Statamic Mux Laravel Package

Product Decisions This Supports

• Video hosting strategy (build vs. buy vs. borrow). This addon collapses a "we need video" requirement into a configuration task: editors upload in the Statamic control panel, assets land in Mux, and templates render from a playback ID. It makes the buy path (Mux + thin CMS glue) viable without a custom integration sprint.
• CMS selection and lock-in posture. If video is a first-class content type, this is evidence that Statamic can serve editorial video workflows without bolting on a separate DAM or a WordPress-style plugin stack. Conversely, it deepens dependence on Mux as a second platform vendor alongside the CMS.
• Roadmap: video-led content types. Justifies investing in video-centric blueprints (courses, product demos, case studies, gated/private content) because the editorial workflow — not just playback — is solved. Without this, video pages are usually hand-built one-offs.
• Repository and infrastructure decisions. Offloading video bytes to Mux removes large binaries from the Statamic asset container (and from Git/S3), which affects hosting cost, deploy time, backup size, and CDN egress modelling. That is a real, quantifiable infrastructure line item.
• Editorial autonomy / headcount. Non-technical editors can publish video without a developer transcoding files, hand-copying embed codes, or filing a ticket. This is a support-load reduction, not just a feature.
• Privacy, branding, and monetisation choices. Using Mux rather than YouTube/Vimeo implies no third-party player chrome, no recommendations, no ad tracking on your pages — a decision that shows up in legal review, cookie banners, and enterprise procurement questionnaires.
• Vendor and cost modelling. Mux is usage-priced (storage + delivery). Adoption forces an explicit forecast: minutes stored, minutes streamed, peak concurrency. That forecast is often the actual decision, not the package.
• Risk register entry. At 13 stars and a single maintainer, this is a thin, replaceable dependency — which is itself a decision input: it is cheap to adopt, cheap to fork, and cheap to abandon. The reverse is also true: it is not a strategic platform bet.

When to Consider This Package

Consider it when:

• The site runs Statamic (verify the supported major version range against your install before committing) and video is genuinely part of the content model — multiple videos, recurring publishing, editor-owned.
• Editors are non-technical and the current workflow involves someone manually uploading to a video host and pasting embed markup.
• You want adaptive-bitrate streaming, automatic encoding, and a professional player without owning a transcoding pipeline.
• Brand control, ad-free playback, or privacy/consent requirements rule out YouTube/Vimeo embeds.
• Video assets are bloating your asset container, Git repository, or object-storage bill.
• You need a fast proof of concept: the integration surface is small, so a spike is cheap and reversible.
• You are already a Mux customer, or are willing to become one — otherwise the addon is only half a decision.

Look elsewhere when:

• You have one hero video on the homepage. A hosted embed or a static MP4 is cheaper and simpler; the CMS integration earns nothing.
• Budget is the binding constraint. Mux pricing scales with storage and delivery; for high-traffic, low-margin content the economics may not clear a YouTube/Vimeo comparison.
• You need self-hosted or on-premises video (regulated, air-gapped, data-residency-mandated environments). Mux is a cloud dependency by definition.
• You require enterprise-grade vendor assurance: SLA, support contract, security review, long-term maintenance guarantee. A 13-star, single-maintainer addon will not survive procurement as-is — though the underlying Mux API will.
• Your needs are live streaming, DRM, or complex per-viewer entitlements at scale, where you would be building on the Mux SDK directly rather than through a CMS fieldtype.
• Your video pipeline is already solved by a DAM or a Mux-backed platform, and adding a second path fragments the source of truth.
• Statamic is not your CMS. The package is not portable; the Mux integration logic is, but you would be reimplementing it.

Migration/exit note: because the addon only brokers uploads and resolves playback IDs, the exit cost is low — the durable asset lives in Mux, and the CMS holds a reference. That asymmetry is the main reason this is a defensible small bet.

How to Pitch It (Stakeholders)

For executives (one paragraph): We can publish video on the site without custom development. Editors upload in the CMS they already use; the file is streamed through Mux, a commercial video platform that handles encoding, quality adaptation, and delivery. That removes video files from our own hosting and removes developers from the publishing path. The cost is Mux's usage-based fee plus essentially zero integration effort. The risk is that the addon is a small open-source project with a single maintainer — but it is a thin layer, so if it stalls we fork it or replace it in days, and our video assets stay in Mux either way. Recommend a scoped pilot on one video-heavy section before committing to a site-wide rollout.

For engineering (one paragraph): This is a Statamic addon that wraps the Mux API — a fieldtype for upload/selection in the control panel plus template access to the playback ID. Expect conventional Statamic addon structure: config-driven credentials, Laravel HTTP client and queue for the upload/transcode handshake, no exotic dependencies. Adoption work is mostly configuration, credentials management, and confirming the supported Statamic/Laravel version matrix. Before we commit, verify: which Statamic versions are supported, whether uploads are queued or synchronous (control-panel timeouts on large files), how webhook/asset-ready state is handled, whether signed or public playback is supported, and whether there are tests. Given the project's size, pin the version, vendor it, and treat it as a fork candidate — the maintenance burden is small but the bus factor is one.

For the pilot, define success up front: time from "editor has a file" to "video live on page," reduction in developer touches per video publish, storage/egress delta versus the current approach, and a Mux cost-per-month estimate at realistic traffic. If those four numbers do not beat the status quo, the answer is a hosted embed and we have lost a week.