Roadmap
The Platform capabilities page is the source of truth for what you can use today. This roadmap is intentionally narrower: it shows the product areas we are expanding next and the customer outcome each one is meant to unlock.
Expanding Now
Section titled “Expanding Now”Self-host, Hybrid, and Federated Delivery
Section titled “Self-host, Hybrid, and Federated Delivery”We are continuing to harden the self-host path: bring your own MistServer nodes and let FrameWorks handle DNS, TLS, geo-balanced routing, cluster federation, tenant subdomains, analytics, playback access control, and the rest of the operations layer around them. The same plane supports teams running fully self-hosted clusters, teams that mix their own infrastructure with managed FrameWorks regions, and teams that want to list spare capacity to others.
Outcome: stand up a production-grade MistServer cluster without gluing together ten separate services for DNS, certificates, routing, observability, billing, and access control.
Pull-Input Streams
Section titled “Pull-Input Streams”Pull streams are available through the dashboard, API, and agents. The remaining work is deeper operational visibility for upstream connection attempts, retries, private-source edge cases, and self-hosted deployment diagnostics.
Outcome: bring RTSP cameras, SRT/RIST feeds, HLS origins, MPEG-TS sources, and Mist/DTSC sources into FrameWorks with clearer failure states.
Gateway-Backed Transcoding
Section titled “Gateway-Backed Transcoding”Livepeer Gateway integration is active. We are expanding native controls, plan-aware defaults, and dashboard/API workflows for adaptive renditions.
Outcome: enable ABR when source bitrate or viewer networks make a single rendition impractical.
FairPlay, Widevine, and PlayReady support is in development. Until DRM lands, premium playback workflows that require it should stay on their existing provider.
Outcome: protect premium playback workflows without moving video delivery out of the FrameWorks control plane.
Public Cluster Marketplace
Section titled “Public Cluster Marketplace”Marketplace primitives — listing, invites, subscription requests, approvals, preferred-cluster routing, pricing models, and metered/custom rating — ship today. The remaining work is the public operating model: operator vetting, published commercial terms, support boundaries, and a production onboarding workflow for third-party capacity.
Outcome: turn the existing marketplace plumbing into a vetted public program so tenants can buy capacity from third-party operators with a known support and trust contract.
Agent and Automation Workflows
Section titled “Agent and Automation Workflows”We are expanding agent-facing workflows around operational diagnostics, billing preflight, and safe platform changes through MCP and GraphQL.
Outcome: let agents operate FrameWorks with the same controls humans use, while preserving confirmation gates for sensitive or billable actions.
Scheduled Recordings
Section titled “Scheduled Recordings”Calendar-driven DVR captures for places of worship, periodic events, classes, scheduled programming, and any workflow where a stream goes live on a known schedule. Recording starts and stops automatically against a stream that may already be live 24/7, and the operator does not need to be at the desk when the window opens.
Outcome: a weekly service, lecture, or event records itself on its own schedule, with the resulting DVR/clip/VOD assets dropping into the library without manual intervention.
Scheduled VOD Streams
Section titled “Scheduled VOD Streams”Linear live channels assembled from existing VOD assets are planned on top of the managed-stream foundation. The scheduler should select finalized VOD artifacts, verify or pre-hydrate frozen assets before their playout window, and materialize a rolling live stream without bypassing artifact ownership, retention, or billing semantics.
Outcome: turn a VOD catalog into a programmed live channel for demo loops, event replays, education, worship, or TV-style schedules while keeping the source assets in the normal library lifecycle.
Team Accounts and Permissions
Section titled “Team Accounts and Permissions”Multi-user accounts, role-based permissions, and audit visibility are planned for tenants that need shared operations.
Outcome: separate owners, operators, developers, and finance workflows without sharing a single account credential.
Event Webhooks
Section titled “Event Webhooks”Outbound webhooks are planned for platform events such as stream lifecycle changes, asset readiness, billing events, and operational alerts.
Outcome: connect FrameWorks events to your own systems without polling.
View-Level QoE Analytics
Section titled “View-Level QoE Analytics”Stream and routing analytics already exist, and first-party view-level QoE now ships for the FrameWorks player — rebuffering, frame drops, startup time-to-first-frame, and per-asset VOD retention/watch-density. What’s still ahead is the breadth: QoE capture from third-party / non-FrameWorks players and deeper per-view tracing.
Outcome: answer which viewers buffered, why they buffered, and which route or rendition they used — across any player, not just the FrameWorks one.
Device Discovery and Contribution Inputs
Section titled “Device Discovery and Contribution Inputs”The media engine already has experimental local discovery and local-source creation paths. The FrameWorks work is productizing that capability around an Edge node: packaging it into the edge runtime, exposing it through the API and dashboard, and making it usable from the Tray app and CLI.
Outcome: let an on-prem FrameWorks Edge discover cameras, PTZ devices, NDI sources, USB capture, and HDMI contribution paths, then ingest them into managed FrameWorks streams or self-hosted clusters without hand-built local glue.
Processing and Composition
Section titled “Processing and Composition”Server-side processing remains a longer-term platform theme. The intent is to keep media work inside the media engine: a MistServer-native blitter for logos, watermarks, and lower-third overlays; MistServer’s Composer reused for server-side ad insertion (SSAI) and raw-pixel composition; transcription, object detection, picture-in-picture, and automated clipping layered on top.
Outcome: move more production work into the same control plane that already handles ingest, delivery, assets, and analytics.
Managed DNS, Proxying, and Storage Services
Section titled “Managed DNS, Proxying, and Storage Services”Managed DNS, generic CDN/proxying, and standalone object/block storage are backlog items adjacent to video delivery. FrameWorks already runs DNS automation, service proxying, and media storage internally for operated deployments; the roadmap work is turning the right parts into customer-facing products with domains, origins, Ceph-backed storage resources, self-hosted/Anycast DNS paths, policies, billing, and support boundaries.
Outcome: cover more of the infrastructure teams already wire around their video workloads without pretending internal operator plumbing is a self-serve product.
Mobile Apps and Help Center
Section titled “Mobile Apps and Help Center”Native mobile apps and an integrated help center are planned, but they come after the core platform surfaces are complete.
Outcome: make FrameWorks easier to operate from more places without splitting the product experience.