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.
Where a request is answered, where a stream originates, and where a viewer receives it are three different places. Placement policy lets you state which capacity your streams may use and in what order, such as your own servers first, and enforces it where media starts.
A live stream is a ring buffer on an edge node. A channel that streams for 90 days straight is still one recording, replayable in chapters, and a plan change halfway through never shortens an archive that is already recording.
FrameWorks now runs an EU and a US region. Viewers and broadcasters are handled entirely in their own region, while analytics and billing converge in one place, so a tenant gets one bill that counts every region exactly once.
No signup form, no credit card, no human: an agent signs in with a wallet, gets a payment request when its balance runs out, pays in USDC, and carries on. How FrameWorks treats agents as first-class users.
A FrameWorks edge can run on a server we have never seen. How it proves who it is without a shared secret, why it never holds our internal certificate authority, and why we run our own mesh instead of Tailscale.
The FrameWorks gitops repo is public: every service, database, and broker placement in plaintext, with only host addresses and credentials encrypted. What we encrypt, what we don’t, and the pre-commit hooks that enforce the boundary.
Clusters can now source live streams from one another. A viewer near a cluster that never received the broadcast is served from a nearby edge after a single server-to-server pull, instead of being sent somewhere worse.
We used a multi-agent review process to audit FrameWorks across routing, ingest, billing, analytics, auth, and more. The useful part was forcing every claim to come with evidence.