When one live stream goes to several destinations, each restream now gets the original video if the destination accepts it and a compatible rendition if it does not, without encoding again what already fits.
We compared every Livepeer Studio webhook event, payload field, and playback-policy option against FrameWorks and closed the gaps that would force a Studio integration to change its logic, from playback gates that rejected a 204 to importing VOD assets from a URL.
FrameWorks now publishes SDKs for TypeScript, Go, and Python. All three are generated from the same GraphQL operations, share one version, and pass the same conformance fixtures, so a backend gets the same behavior in any of them.
FrameWorks now publishes a versioned catalog of account events, delivers it live over a GraphQL subscription, and sends it to your HTTPS endpoints as Standard Webhooks-signed requests you can verify with existing libraries.
Platform alerts now become incidents: one record per failure with a timeline, acknowledgement, assignment and live updates, visible to the tenant who owns the cluster and reachable through the dashboard, GraphQL and MCP.
FrameWorks 0.3.0 adds platform admin, analytics, playback that survives control-plane blips, media placement policies, safer agent workflows, and the real-time foundation for chat and conferencing.
Skipper answers streaming questions from curated docs, runs diagnostics against your live streams, and acts through the same MCP gateway your own agents use. Every part of an answer says how sure it is.
Why we’re writing about video infrastructure in public, and what to expect from this blog.