Migrate to FrameWorks

Moving to FrameWorks from another platform? This section is the home of our migration program: dedicated guides for the platforms we see most often, a generic guide for the ones we haven’t written up yet, and a standing offer to help you 1:1 if your case doesn’t fit a template.

Why teams move

One branded URL across every operator you use. Paid tenants get {tenant}.cdn.frameworks.network plus per-service aliases (edge-ingest.{tenant}.cdn.frameworks.network, foghorn.{tenant}.cdn.frameworks.network, …) that geo-balance across every cluster you subscribe to — your own self-hosted nodes, FrameWorks platform clusters, and any third-party marketplace clusters. One URL, one cert, one operational view. No competitor spans operator trust boundaries this way.
Always-on DVR without arbitrary rollover. Run long-lived live channels, keep one continuous archive, and replay historical windows through finalized chapter artifacts.
API and agent parity. The dashboard, GraphQL API, and MCP tools expose the same platform controls, so human operators and autonomous agents can use the same workflows.
Hybrid edge options. Use managed regions, your own edge clusters, or both, while keeping routing, analytics, and playback access control in one control plane.
Deep routing and QoE visibility. Debug viewer routing, buffering, quality tiers, geography, stream health, and node performance without treating delivery as a black box.

Available guides

Livepeer Studio Available now — REST → GraphQL, player swap, multistream, and playback access-control differences.

MistServer Available now — stay on raw MistServer, add FrameWorks edge capacity, or move to managed SaaS.

Bunny Stream Available now — VOD/CDN swap, plus first-class live ingest you don't get from Bunny Stream today.

Mux Available now — REST → GraphQL, signed playback (RS256 → ES256), simulcast, and where Mux Data fits in the migration.

Any video API Available now — universal checklist for platforms without a dedicated guide.

Planned migration guides

Dedicated guides we intend to publish next. If you’re coming from one of these today, the Any video API checklist plus support outreach is the fastest path.

Wowza (Streaming Cloud + Streaming Engine)
Cloudflare Stream
AWS IVS
Vimeo
api.video
Ant Media

Don’t see your platform?

Open a forum post, drop into Discord, file an in-app ticket from /support, or ask Skipper directly. Include the source platform, the APIs you use today, and the migration deadline so support can point you at the closest existing guide or scope the missing platform-specific steps.

Migration assistance

We don’t ship one-shot importers yet. What we do offer:

Concierge migration for paid tiers and self-hosted operators with non-trivial libraries: we’ll help pull your VOD assets, rewrite your integration, and validate side-by-side. Reach out before you start so we can scope it.
Skipper, on demand: the AI consultant can answer API and troubleshooting questions from the docs and protocol references.
Direct human help via in-app ticketing, Discord, and the forum.

Not available yet: Studio asset importer, OpenAPI → GraphQL codegen pointers, and an encoder-config converter.

What every migration looks like

Regardless of where you’re coming from, the moves are the same:

Create a FrameWorks account and a first stream. Wallet sign-in works if you’d rather skip email.
Repoint your encoder. RTMP, RTMPS, E-RTMP, WHIP, or SRT — the URL changes; the protocols stay.
Swap the player. @livepeer-frameworks/player-* ships React, Svelte, Web Components, and a vanilla core.
Rewire your API integration. Most platforms are REST; FrameWorks is GraphQL-first. See Any video API for the universals.
Review playback access policies. Public playback IDs are straightforward; JWT/webhook gating needs a separate plan.
Re-attach multistream targets. Push targets are scoped per-stream on FrameWorks (and on most platforms).
Validate side-by-side. Run your old and new streams in parallel before you cut over.

Concepts worth knowing before you start

A few things differ from most peers, so we surface them once here instead of repeating them in every guide:

GraphQL-first API. REST is used for auth, webhook ingress, and playback URLs only. The application surface is GraphQL — query, mutation, and subscription. Codegen against the public schema is the recommended path; Houdini, urql, and Apollo all work.
Subscriptions instead of outbound webhooks. Real-time events flow over GraphQL subscriptions today. Outbound HTTP callbacks are on the roadmap, but subscriptions are the supported event surface for current migrations.
Wallet auth + x402 for agents. Autonomous callers don’t need an account. Sign with an EVM wallet (EIP-191) or attach a gasless USDC payment (EIP-3009) and go. See Agent Access.
Sovereign and hybrid hosting. You can run the video and control-plane stack on your own hardware, or mix BYO edge nodes with our managed control plane. S3-compatible storage and managed DNS are external integrations today; native storage and DNS are on the roadmap.
Skipper. The in-product AI consultant runs diagnostics (rebuffering, packet loss, routing), explains the API, and is reachable from the dashboard, the docs (⌘J), or via MCP. Treat it as a first-line support channel.

Get help

Channel	Best for	Where
Skipper (AI consultant)	Quick troubleshooting, API discovery, diagnostics, after-hours, non-human callers	Dashboard `/skipper` · `⌘J` in docs · MCP at `/mcp`
In-app ticketing	Account-specific issues, billing, anything tied to your tenant data, library-migration help	Dashboard `/support`
Forum	Long-form Q&A, recipes, searchable community knowledge	forum.frameworks.network
Discord	Real-time chat, casual questions	Join
GitHub	Bugs, feature requests, deeper technical threads	Livepeer-FrameWorks/monorepo