Deployment models

Self-managed (BYOC): the data plane runs in your cloud account under your KMS key, and raw telemetry never leaves your boundary. You own the security perimeter and retention; m-cdn operates the control plane and sees only summaries.

m-cdn Cloud: m-cdn runs the full stack as a managed service, so there's nothing for you to provision. Faster to start; the trade is that the telemetry boundary sits with m-cdn rather than inside your account.

The routing engine and product experience are identical across both — the choice is purely about where the data lives and who operates the infrastructure. Enterprises with strict data-residency or procurement requirements typically take self-managed BYOC; teams that want to move fast and don't need raw data in-house typically start on m-cdn Cloud and can migrate later.

Either way, m-cdn never proxies your video and (under v2.0) stays out of the critical path — the CDNs serve pre-published manifests, so the stream survives an m-cdn outage regardless of deployment model.