Production-ready
Suitable for controlled production when configured and validated according to the deployment guidance.
The participant fabric, honestly labeled.
Every capability is separated into production-ready, demo-ready, foundation, or roadmap work—with evidence and current limits beside it.
surfacestatusevidenceBrowser roomproductionSDK + testsMediasoup SFUproductionengine + guidanceRobot bridgedemo-readysim + field validationMedia graphfoundationbounded runtime
Production-ready = configured pathDemo-ready = evaluate closelyFoundation = bounded surfaceRoadmap = no runtime claimLimits named in matrix
Readiness language for shared decisions.
Commercial, product, and engineering stakeholders can use the same labels without treating demo-ready surfaces as commitments or foundations as finished products.
Demo-ready
Working software for demos, pilots, or controlled evaluation, with known hardening or operational integration gaps.
Foundation
Useful APIs, packages, tests, or partial integrations exist, but the complete production path is not yet finished.
Roadmap
Architecture or product direction exists, but customers should not depend on the capability as currently available.
Production communication, control, and operations.
| Capability | Status | Evidence | Current limit |
|---|---|---|---|
| WebSocket/WSS signaling | Production-ready | Server, SDK, integration tests, TLS/proxy guidance | Requires production auth, TLS, rate limits, and proxy timeout configuration |
| Room presence and lifecycle | Production-ready | Room registry, liveness, reconnect, demos, tests | Multi-node durability requires a production shared adapter |
| Browser mesh | Production-ready | Browser SDK and two-browser examples | Suitable for small rooms; use an SFU as room fan-out grows |
| Mediasoup-backed SFU | Production-ready | Default SFU engine, control lifecycle, demos, tests | Validate target codecs, browsers, NAT/TURN, and capacity |
| Integrated first-party SFU/media plane | Demo-ready | Native UDP, ICE-lite, DTLS/SRTP, RTP routing, pacing, two-client smoke harness | Cross-browser, separate-host, and operational hardening continues |
| TURN/STUN | Production-ready | First-party relay, dynamic credentials, metering, relay tests | Size relay ports, bandwidth, quotas, firewall, TCP, and TURNS per deployment |
| Chat, typed signals, awareness | Production-ready | Protocol, client, server, storage adapters, late-join snapshots | Configure durable storage when restart persistence is required |
| Typed data channels and files | Production-ready | Schema validation, chunking, compression, tests | Application policies must set size, type, and retention limits |
| Production auth | Production-ready | JWT key rings, JWKS, OIDC, OAuth introspection, RBAC | Issuer, audience, scopes, rotation, and dev-auth rejection are deployment responsibilities |
| Admission and token revocation | Demo-ready | Waiting-room tickets, moderator decisions, abuse controls, revocation store | Multi-node rooms require shared ticket and revocation state |
| OpenTelemetry and usage export | Production-ready | OTLP, Prometheus, tenant-labeled usage records, reference rollup consumer | Customers operate durable collectors, retention, pricing, invoicing, and dispute workflows |
| Admin API | Production-ready | Room, participant, policy, audit, token, and health endpoints | Requires exact origins, CSRF controls, and strong bearer tokens |
| Admin console and global monitoring UI | Demo-ready | Operator console plus signaling, SFU, TURN, worker, regional-capacity, JSON/SSE/HTML monitoring | History is in-memory; bring an identity layer and durable telemetry for broad production use |
| License operations | Production-ready | Signed runtime validation, role/capacity gates, redacted admin status, air-gap entitlement | Operators own protected distribution, status artifacts, renewal timing, and rotation |
| WHIP/WHEP HTTP gateway | Demo-ready | HTTP session lifecycle, SDP negotiation, trickle ICE, TURN Link headers, producer/consumer wiring | Production-scale ingest/egress hardening and broader validation remain ongoing |
Expansion paths with explicit maturity.
| Capability | Status | What exists now | Current limit |
|---|---|---|---|
| React / Next / Vue / Nuxt / Svelte / Solid / Angular | Shipped | Documented framework packages over the shared browser room session | Follow framework-specific client-only and SSR rules |
| SvelteKit / Remix | Pattern | Minimal examples composed from shipped Svelte or React room packages | No dedicated adapter package; use the documented client-only pattern |
| Qwik / Astro / Lit | Foundation | Bindings and controller packages with examples or guidance | First-class integration and validation continue |
| Node / Go / Python / .NET service clients | Production-ready | Tested signaling, data, chat, and worker paths; optional Node/Python media | No general native-capture claim; provider and media wiring remain application-owned |
| Rust / C++ service clients | Foundation | Protocol, signaling, worker, and partial external-media paths | Use verified media FFI or an external WebRTC/media stack |
| Swift / Kotlin / React Native / Flutter | Foundation | Signaling, SFU control, generated types, and partial libwebrtc or WHIP/WHEP paths | Media maturity and target-platform validation vary substantially |
| MQTT / serial / BLE / USB bridges | Production-ready | Native sidecars, shared gateway package, examples, simulators | Browser device adapters and broad real-hardware test matrices remain planned |
| ROS2 robotics | Demo-ready | Bridge paths, teleoperation, simulation, fleet rooms, camera workflow | Broader hardware profiles and production field validation are ongoing |
| AI/service workers | Production-ready adapter pattern | Typed room clients, provider adapters, lifecycle, usage, and monitoring hooks | Production model-provider selection and credentials remain application responsibility |
| Local TTS and presence surfaces | Foundation | Piper-WASM, Web Audio track output, native speech provider, personas, lexicon | Broader browser UX and direct room examples are still maturing |
| Shared realtime objects | Shipped package | Transport-neutral per-key LWW objects, SharedSignal adapter, and tests | No BrowserRoom convenience API, authoritative server snapshots, persistence, or collaborative-text CRDT |
| Realtime media surfaces | Shipped package | Canvas, interactions, shared-object adapters, room publishing, semantic recording/replay, headless commands | A dedicated PMG graph-node adapter remains roadmap work |
| Programmable Media Graph | Foundation / bounded slices | Frame bus, scene runtime, batch/live grid, speaker, PiP, custom layouts; live composition on mediasoup and integrated engines | Batch is first-party-only. Broadcast control and composited-feed APIs ship, but stock end-to-end consumer validation, semantic replay, and broad deployment remain open |
| Metering reference consumer and dashboard | Demo-ready | Validated ingestion, deduplication, tenant/region rollups, 60-metric inventory, illustrative rate card | In-memory reference only; not a billing SDK, invoice, quota, or durable ledger |
| Diagnostic evaluation tools | Demo-ready | Connectivity check, local support-bundle evaluator, and declarative RTC Test Lab | Evaluation and support tools do not replace production monitoring or capacity validation |
| Recording | Foundation | Controller, workers, WebM muxer, track synchronization, mesh and SFU ingest adapters, synthetic artifact demo | Complete live-room worker orchestration and durable artifact operations are not broad production-ready |
| E2EE | Foundation | Capability, key-manager, transform, and opacity work | Production key distribution and complete browser/SFU validation remain |
| Server voice agent | Roadmap | Architecture plus separate worker, VAD, and TTS building blocks | No server-side conversational voice-agent runtime exists yet |
| Media DSP engine | Roadmap | Product and architecture direction | Do not treat as a currently available runtime |
Status is not a certification. Production suitability still depends on target browsers, networks, codecs, identity systems, data policy, scale profile, and operational acceptance tests.