Skip to content

FrameWorks and the Livepeer Studio transition

6 min read
Motion-blurred film photo of a person's legs walking across a zebra crossing, long shadows on the white stripes.

By Marco van Dijk, FrameWorks

Studio is closing. Your streams can stay on Livepeer.

For a long time building on the Livepeer Network meant: building on Studio. They stewarded the Livepeer transcoding stack and turned it into a complete, hosted media pipeline with everything a developer needed to build video applications.

However, with the dawn of a new and improved Livepeer protocol comes new capabilities for the network. From open models and built-in media tools, to a ‘Livepeer Agent’ that turns a single prompt into a finished, edited video.

This new direction put Livepeer Studio on the backburner, and now that entity is winding down. Fortunately, there’s a new home for anyone that has been building on Studio.

You might already know the engine; Studio's live streaming ran through our open source media server software: MistServer. It’s the workhorse handling tasks like ingest, transmuxing, and delivery. Our team has been building MistServer since 2009, and FrameWorks is the video cloud built around it, leveraging the Livepeer network of GPUs to handle heavy tasks like transcoding.

Built from the ground up, aiming to fulfill a more ambitious roadmap: more features, lower latency, more protocols, and a new and improved Livepeer Transcoding pipeline.

Studio was a solid video API. FrameWorks aims to be the whole video cloud: everything between the camera and the viewer's screen, in one place, run by the people who understand video like no other.

Building further on Studio’s pioneering work

What carries over from Studio, and what is new
What carries over from Studio, and what is new

Everything you used on Studio carries over: RTMP and WebRTC ingest, HLS and WebRTC playback, recordings, clips, VOD, multistreaming, webhooks and signed playback. On top of that:

  • More ways in. SRT, Enhanced RTMP with HEVC and AV1, and pulling streams straight from IP cameras, SRT, RIST or HLS sources.
  • More ways out. SRT, LL-HLS, DASH, and (animated) thumbnails for every stream, clip or recording.
  • A studio in your browser. StreamCrafter mixes cameras, screens and overlays before you go live.
  • Your own hardware. Run FrameWorks edge nodes on your own machines and they serve your viewers first. Or self-host the whole platform; the code is public domain and the architecture is documented.
  • Everything in one place. Configuration, viewer analytics and quality of experience, infrastructure health, incidents and support tickets, all in one dashboard & API.
  • Built for agents. An MCP server, wallet sign-in and pay-per-use USDC, so an AI agent can set up a stream and pay for it on its own, or help you migrate off of Studio.
  • Hands-on support. Talk to the engineers who built the media server over a video call, a shared Slack, or any other channel you prefer. Sometimes, video problems start before the stream reaches us or after it leaves, and our engineers love helping out with those issues too.

Live in New York, watched in Berlin

In order to provide a great quality of service on a global scale, one of the biggest improvements over Studio is our Edge Runner architecture, orchestrated by custom built load balancer software.

A broadcaster in New York goes live from OBS. The stream lands on one of our US edges, which hands the source to nearby Livepeer orchestrators and gets back a full ladder, from 1440p down to 360p. Viewers in the US watch straight from that edge.

Then someone in Berlin opens the stream. We route them to a healthy edge in Europe, which pulls the finished renditions across the Atlantic. As more viewers in Europe trickle in, they can instantly playback on a warm node close by.

Nothing is transcoded twice, and our load balancers open up peer-to-peer ‘federation’ channels to sync up, optimize stream boot times, and keep on working even if there’s an outage in our control plane.

One stream, transcoded once by Livepeer orchestrators, served from edges in the US and Europe
One stream, transcoded once by Livepeer orchestrators, served from edges in the US and Europe

The Livepeer network side is fully handled by our platform. It finds eligible orchestrators, picks the best ones, pays them, keeps track of how they perform and swaps in a replacement when one falls behind.

Every plan in the FrameWorks video cloud includes transcoding on Livepeer, so streams that land on FrameWorks become work for the network. As new capabilities come online on Livepeer, they’ll be exposed as well so that people building on FrameWorks can make full use of the Livepeer compute network.

The only video cloud that offers price reduction options

Say you run a channel 24/7 with about 150 people watching at any moment. That is roughly 6.5 million delivered minutes a month. Fully hosted on FrameWorks, that comes to about €3,200 a month on our Production plan at the base price (bulk volume discounts are applicable).

Even though this is a competitive rate compared to other video clouds, these costs can be too much to bear for individuals or businesses who are starting out or don’t have monetization for their content.

Now put a FrameWorks edge runner on a Mac Mini at your studio, on a decent fibre line. Your viewers are served from your own box first, and the minutes it delivers cost nothing. You would be on the €79 Supporter plan, saving about €3,100 a month, close to €38,000 a year.

Fully hosted vs. serving viewers from your own edge runner first
Fully hosted vs. serving viewers from your own edge runner first

The box does need the bandwidth: serving 150 viewers at HD qualities can easily saturate a gigabit uplink. If a big show outgrows it, or attracts viewers from faraway regions, these spill over onto our edges at the normal rate, ensuring quality of service for anyone watching your content.

Moving over

Moving from Studio to FrameWorks in three steps
Moving from Studio to FrameWorks in three steps

Even though we took great care to ensure the API feels familiar to people coming from Studio, moving over to FrameWorks means replacing their player and backend SDK’s with ours.

You’ll need to re-create any streams, authentication, webhooks, or other features you’re using on Studio. Your streamers and viewers will barely notice; they’re still speaking the same standardized protocols.

The migration guide can be a good starting point, and our client portal offers a more interactive experience to discover FrameWorks’ capabilities & go live on the free plan, no credit card needed.

Let's talk

An even better way to get started is through a (digital) face-to-face meeting. Get in touch and we'll set up a video call to go over your setup, or come say hi on Discord, either in the FrameWorks or Livepeer server. Our video engineers are always ready to help you solve media-related issues, regardless of what video provider you’re using.