Showcase

What FrameWorks does today, and what comes next

A plain view of what you can use now, what is being built next, and what is further out. Statuses come from the same feature registry as the docs and the roadmap.

Shipping today · Beta

StreamCrafter browser studio

Go live from a browser tab with no encoder to install. Mix cameras, screens, and media files into scenes and switch between them on air.

Several cameras, screen shares, and video or audio files in one mix

Scenes with stacked layers, logo and text overlays, and picture-in-picture or split layouts

Cut, fade, or slide transitions between scenes

The same studio as npm packages for React, Svelte, and Web Components

The SDK will change substantially as cloud production arrives, so expect breaking changes between releases.

your browser tabcamerascreen sharemedia fileStreamCrafterscenes and layerslogo and text overlayscutfadeslideWHIPFrameWorksWHIP ingestviewers andmultistreamyour browser tabcamerascreenmedia fileStreamCrafterscenes and layerslogo and text overlayscutfadeslideWHIPFrameWorksWHIP ingestviewers and multistream
Sources are mixed into scenes inside the browser tab and published to FrameWorks over WHIP. There is no encoder to install.
Up nextStreamCrafter cloud productionThe server side of StreamCrafter. Sources are mixed on processing nodes into one program stream, so a show keeps running without a browser tab.

Shipping today

Available on the hosted platform and in the self-hosted release. A badge or note marks work that is in beta or still expanding.

Shipping

Live video delivery

Ingest, protocol conversion, low-latency delivery, recording, and playback, on our own media server and delivery network.

Quick start
  • Push over RTMP, E-RTMP, SRT, or WHIP from any encoder or browser
  • Deliver over HLS, LL-HLS, DASH, WebRTC (WHEP), and progressive MP4
  • The same stream converts between protocols without a separate transcode step
Shipping

Multistreaming

Push one live stream to YouTube, Twitch, Kick, or any RTMP or SRT destination while it runs.

  • Pushes start when the stream goes live and stop when it ends
  • Turn destinations on or off without deleting them
  • Each destination gets the original video when it fits, with no re-encoding
  • Status and failure reasons per destination

Each destination shows its status and failure reason. Live bitrate and bytes sent per destination are not shown yet.

Multistreaming guide
your encoderMistServerorigin nodeTwitchYouTubeKickFacebookXcustom RTMP / SRTno relay in betweenpushed from hereyour encoderMistServerorigin nodeTwitchYouTubeKickFacebookXcustom RTMP / SRTstart and stop with the stream
One ingest, every destination, pushed straight from the origin. Targets start and stop with the stream.
Shipping

Players and embeds

Player SDKs for React, Svelte, Web Components, and plain JavaScript, with protocol selection and playback access control.

Playback guide
  • Picks the best protocol for each viewer, or the one you require
  • Public, signed JWT, or webhook playback policies with allowed embed origins
  • Startup and buffering telemetry from every viewer, built in
Shipping

Recording, clips, and VOD

Record live streams around the clock, cut clips from any point, and serve uploads as on-demand assets.

Recordings guide
  • 24/7 DVR with live rewind and chapters you can replay by time range
  • Clips stored as their own assets, or cut on the fly as a download
  • VOD upload and import from a URL, with retention you set per asset
Shipping

Viewer routing

Each viewer is sent to the best edge by location, load, and node health, across every cluster the stream can use.

How routing works
  • Routing decisions are visible per viewer in analytics
  • Edges you run and FrameWorks regions serve the same audience
Shipping

Analytics and viewer QoE

See why each viewer connected to the edge they did, and what their playback was like.

  • Stream health, audience geography, and routing decisions in real time
  • Startup time, rebuffering, and frame drops per view from the FrameWorks player
  • VOD retention and watch density per asset

Viewer QoE comes from the FrameWorks player. QoE from third-party players and per-view tracing are not there yet.

See analytics
viewerroutinglocation, load, healthFrameWorks edgeyour edgeunhealthy edgewhy this edgestartup, rebufferinganalyticsviewerroutinglocation, load, healthFrameWorks edgeyour edgeunhealthy edgestartup, rebuffering, routeanalytics
Each viewer is sent to a healthy edge by location and load. The routing decision and the player's playback report land in the same analytics.
Shipping

Livepeer transcoding

Live adaptive bitrate renditions through the Livepeer network or local processing, with usage reported per stream.

Renditions follow your plan's processing policy, and a stream can turn its live ladder off. Choosing the ladder per stream is not there yet.

Encoder setup
  • Renditions follow your plan's processing policy
  • Streams that need no ladder can turn it off
  • Processing minutes and orchestrator results in the usage analytics
Shipping

Pull inputs

Bring in IP cameras and upstream feeds without an encoder. FrameWorks pulls the source only while someone is watching.

Not shown yet are the upstream connection attempts, retries, and drops after a source resolves.

Pull streams guide
  • RTSP cameras, SRT and RIST feeds, HLS origins, MPEG-TS, and MistServer sources
  • Each source check is logged on the stream, so a bad address shows up at once
Shipping

SCTE-35 cue markers

Ad and splice cues pass through the media engine on MPEG-TS input and output. Platform controls for cues are expanding.

The media engine carries cues through MPEG-TS today. Inserting and inspecting cues through the API, agents, and dashboard is not there yet.

  • Cues in your MPEG-TS input are carried through to HTTP TS and TS-over-SRT outputs
Shipping

Your own edges

Run media edges on your own hardware and attach them to FrameWorks, or self-host the entire stack as your own platform.

  • Your edges serve your viewers next to FrameWorks regions
  • FrameWorks keeps running routing, storage, billing, and the control plane
  • Full self-hosting is deployed and upgraded with the frameworks CLI
Bring your own edge
HostedHybridSelf-hostedEdge nodesControl planeProcessingStorageyour edgeshosted burstControl planeProcessingStorageEdge nodesControl planeProcessingyour S3FrameWorks runs ityou run itexternal, yoursHostedEdge nodesControl planeProcessingStorageHybridyour edgeshosted burstControl planeProcessingStorageSelf-hostedEdge nodesControl planeProcessingyour S3FrameWorks runs ityou run itexternal, yours
Same control plane and dashboards in every row. Move between rows without rebuilding your setup.
Shipping

Network explorer

A public map of the network your streams run on, from FrameWorks infrastructure to the Livepeer orchestrators that transcode them.

Open the network map
  • FrameWorks infrastructure topology on a map
  • Livepeer orchestrator prices and measured transcoding performance by region
  • The same Livepeer data as a public API
Shipping

Incidents and alerts

Platform alerts become incidents you can acknowledge, assign, annotate, and resolve. Coverage is still expanding.

Alert coverage is still expanding, with edge reachability, certificate, DNS, capacity, and per-stream causes to come.

Incidents guide
  • Tenants see incidents for the clusters they own
  • Realtime updates in the dashboard and through the API and agents
  • Skipper can investigate an incident for you
Shipping

Agent access

AI agents operate streams, recordings, billing, and infrastructure through the MCP server, with the same controls as the dashboard.

  • Confirmation gates on sensitive and billable actions
  • Diagnostics tools for buffering, packet loss, and routing
Agent docs
your agentany MCP clientMCPMCP servertools, resourcessensitive actionsask firststreamsrecordingsbillinginfrastructureyour agentany MCP clientMCPMCP servertools and resourcessensitive actions ask firststreamsrecordingsbillinginfrastructure
Agents use the same tools and permissions as the dashboard. Sensitive and billable actions ask for confirmation first.
Shipping

Skipper

A platform agent in the dashboard that answers questions about your streams and investigates incidents with you.

Agents can ask Skipper questions over MCP. Managing Skipper conversations through agents is not there yet.

Skipper docs
Shipping

Backend SDKs

TypeScript, Go, and Python SDKs generated from the public API, with typed methods for every operation. Still expanding.

The TypeScript, Go, and Python SDKs cover the whole public API and are still expanding. Typed custom selections exist only in TypeScript, and other languages have no SDK yet.

SDK reference
  • Retries, pagination, and typed errors
  • Multipart VOD upload, playback JWT signing, and webhook verification helpers

Up next

Next on the roadmap, in no fixed order and with no dates. Each entry links to its roadmap section.

Up next

StreamCrafter cloud production

The server side of StreamCrafter. Sources are mixed on processing nodes into one program stream, so a show keeps running without a browser tab.

  • Logos, lower thirds, picture-in-picture, and live switching on the server
  • Backup inputs that take over when a primary source drops
  • Server-side ad insertion (SSAI) on SCTE-35 cues
Roadmap entry
Up next

Teams and roles

Several people on one account with roles for owners, operators, developers, and finance, so producers and engineers work together.

Roadmap entry
Up next

DRM content protection

FairPlay, Widevine, and PlayReady, built into MistServer and the player SDKs.

Roadmap entry
Up next

Live AI processing

Small AI models run inside the media engine on the edge node, next to the live stream. Object detection, segmentation, and transcription are in testing; heavy models go to dedicated compute on the Livepeer network.

Roadmap entry
Up next

Device discovery

An on-site FrameWorks Edge finds IP cameras, PTZ cameras, NDI sources, USB capture, and HDMI inputs, and turns each into a managed stream.

Roadmap entry
Up next

Password and geo rules

Password protection and country rules as switches on a stream, on every plan, with no webhook endpoint to run.

Roadmap entry
Up next

Scheduled programming

Recordings that start and stop on a calendar, and linear channels played out from your VOD library.

Roadmap entry
Up next

Guests and remote contribution

Invite a guest or commentator into a show from StreamCrafter, mixed in the browser or on the server. It follows teams and cloud production.

Roadmap entry
Up next

Rooms and chat

Viewer chat first, then channel points, leaderboards, and moderation views, all synced to the stream timeline.

Roadmap entry
Up next

Live commerce

Shopping and auctions on a live stream, with auction closes that stay fair for viewers at different delays behind live.

Roadmap entry

Further out

Planned work that follows the items above.

Further out

Managed DNS, proxying, and storage

The DNS, proxying, and object storage FrameWorks runs for its media service, offered as products of their own.

Roadmap entry
Further out

Stream-level balances

Balances that fund a single stream, for pay-per-view, tips, and sponsored streams, plus promo codes and referral rewards.

Roadmap entry
Further out

More SDK languages

SDKs for PHP, Ruby, Elixir, Java, and C#, generated from the same operations as today's SDKs.

Roadmap entry
Further out

Mobile apps and help center

Native mobile apps for your streams, incidents, and account, and a help center inside the dashboard.

Roadmap entry
Get started

Launch FrameWorks your way

The same media engine and APIs in every option. Move between them without rebuilding.

Hosted

Sign up and stream on FrameWorks infrastructure. The Free plan needs no card.

In your browser

Play an HLS, DASH, WHEP or MistServer stream, or go live with StreamCrafter.

Your own edge

Attach edge nodes you run to the hosted platform with the frameworks CLI.

Self-hosted

Run the whole platform on your own hardware, deployed and upgraded by the CLI.

Talk to the engineers

Tell us what you are building

You work directly with the people who have built MistServer for more than 15 years. That experience covers your whole pipeline, not just our part of it: encoders and contribution before FrameWorks, players and delivery after it. Ask about trial usage, custom pricing, or a shared channel.