An AI Agent Walks Into a Streaming Platform
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.
Blog
Trusting an Edge Node on Hardware We Don't Own
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.
Our Production Topology Is Public on Purpose
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.
Federation: Serving a Stream From a Cluster That Doesn't Have It
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.
Skipper: An AI Video Consultant With Real Diagnostics
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.