A new video cloud built on 15+ years of media engineering
FrameWorks turns MistServer's proven media engine into a complete hosted, hybrid, and self-hosted platform for live video.
Why we built FrameWorks
FrameWorks exists because live video should not require surrendering the media path to a chain of managed services.
Our team has spent more than 15 years developing MistServer, the media engine at the heart of FrameWorks. It handles ingest, protocol translation, low-latency delivery, recording, and playback without forcing every workflow through a proprietary video service.
FrameWorks adds the cloud platform around that proven engine: tenancy, routing, authorization, analytics, billing, automation, and developer APIs.
Use it as a hosted video cloud, connect your own edges, or run the complete stack yourself. The operating model changes; the product you build against does not.
Core Pillars
Media-Native Core
MistServer carries the live media itself, with broad protocol support and more than 15 years of development behind it.
One Operational System
Ingest, routing, playback, recording, analytics, access, and billing share one tenant-aware platform.
Open to People and Agents
Operate through the dashboard, CLI, SDKs, GraphQL, or MCP. Human operators and autonomous tooling use the same platform capabilities.
Not another API over someone else's video cloud
FrameWorks uses external infrastructure where it makes sense, but the video product itself is not a resale of hyperscaler media services. You get cloud convenience without making a hyperscaler's product or pricing model the foundation of yours.
MistServer is not an interchangeable upstream vendor. It is developed by the same team building FrameWorks and forms the core of the live media path.
Hosted FrameWorks workloads run on infrastructure we operate, including bare metal. We control how streams are placed, routed, delivered, and observed.
Use FrameWorks edges for SLA-backed capacity, Livepeer for low-cost capacity that is quick to scale, or your own edge with no FrameWorks processing charge.
The video layer, control plane, analytics, and operational model can run in your footprint. Storage and DNS remain external integrations today.
Coming Soon
A drop-in app that auto-discovers IP cameras, VISCA PTZ controls, NDI sources, USB webcams, and HDMI inputs.
Combine multiple input streams into one composite output with picture-in-picture, overlays, and mixing.
AI-native live video: transcribe, analyze, automate, and transform streams in real time.
FairPlay, Widevine, and PlayReady protection for premium and licensed content, built natively into MistServer.
What runs the video cloud
At the core is MistServer, developed by our team for more than 15 years. FrameWorks adds the distributed control plane, routing, analytics, billing, and automation. Processing can run on our edges, on Livepeer, or on your own edge.
- MistServer - media server
- Livepeer Network - decentralized transcoding + AI
- WebRTC, RTMP/E-RTMP, SRT, HLS, DASH - streaming protocols
- Go - service runtime
- Apache Kafka - event streaming
- YugabyteDB - distributed SQL
- ClickHouse - analytics store
- gRPC - service RPC
- GraphQL - API gateway schema
- WireGuard - mesh networking
- ACME / Let's Encrypt - TLS certificates
- HashiCorp Vault - secrets
- Redis - caching
- MaxMind GeoIP - geo lookup
- Docker - containers
- Nginx - reverse proxy
- WebSockets - real-time transport
- Prometheus - metrics
- Grafana - dashboards
- Loki - logs
- VictoriaMetrics - metrics storage
- Metabase - BI
- SvelteKit - web app
- React - SDKs
- Astro - docs framework
- Starlight - docs theme
- Stripe - payments provider
- Mollie - payments provider
- x402 - crypto payments + auth
- Chatwoot - support inbox
- Listmonk - newsletter
Our journey
How we got here and where we're headed.
Our team develops MistServer, the media engine that now sits at the heart of FrameWorks.
- Low-latency ingest, delivery, recording, and playback.
- Broad protocol support across broadcast, contribution, and web workflows.
- Production use by streaming operators around the world.
FrameWorks brings a multi-tenant control plane, routing, analytics, billing, and automation to the proven MistServer media layer.
- IBC showcase highlights CDN + hosted processing pipelines with telemetry.
- Sales-engineering loop; from demo interest into structured pilots.
- Partner roadmap aligned with MistServer + Livepeer field feedback captured during the conference.
Core platform is live with limited capacity and a semi-autonomous Media plane
- Operators onboard quickly through the CLI.
- Advanced features start to roll out to round out platform featureset
- Code hardening, unit testing, UX polish, and documentation depth.
Grow the core team, expand infrastructure regions, and deepen enterprise integrations.
- Expand SRE and solutions engineering headcount to support multi-region customer rollouts.
- Broaden advanced-processing orchestration and AI automation capabilities.
- Acquire ASN and expand the network across various data centers.
Deliver a federated CDN and marketplace so operators can exchange bandwidth & compute.
- Ensure the network is open & accessible, and lessen our role as the central gatekeeper.
- Expose FrameWorks policy engine so operators trade bandwidth and processing workloads securely.
- Maintain public-domain licensing so any team can extend, self-host, and interoperate without friction.
Built by the MistServer team. Backed by Livepeer.
A proven media engine, an open cloud platform, and additional processing capacity when workloads need it.
The same team building FrameWorks has developed MistServer for more than 15 years. It is the media engine at the core of FrameWorks, not a third-party service hidden behind our API.
Livepeer provides decentralized processing capacity and ecosystem backing, helping FrameWorks offer accessible transcoding, burst capacity, and a generous free tier.
Three ways to deploy
Hosted, hybrid, or self-hosted. Video infrastructure that fits how you work.