Spatial scenes, WebTransport, and huddle media stay here. Stream, game, IoT, and fleet write D1 and fan out on the room. We do not sell healthcare, we do not include a BAA, and joinVoiceStage is signaling, not an SFU.
A lab can be real enough to prototype against. It is not a license to put it in a customer path. The schema, the media path, and the browser support can move. Pin the SDK, read the limit, and keep a fallback.
Worker rooms are different: chat core, stream, game, IoT, and fleet run on the Worker and D1 today. They share the room and the transcript. Labs sit beside them, clearly labelled.
A room can carry a scene graph and AR overlay state. It stays a lab until a design partner takes it to production.
Open the lab pageWebTransport negotiation with an explicit WebSocket fallback. It does not replace the room socket today.
Open the lab pagejoinVoiceStage is signaling, not an SFU we sell. Live audio is LiveKit when configured; recorded clips land as room messages.
Voice AI surfaceMap scenes and place data are useful for prototypes. They are not a routing engine, a tile bundle, or a geocoder.
Read the platform note| Room | Status | What it is |
|---|---|---|
| Spatial / Twin | Labs | Digital-twin scenes and AR overlays on a room. |
| AI Transport | Labs | WebTransport negotiation with a WebSocket fallback. |
Statuses: Core = Ships on every plan · Worker = Runs on the Worker and D1 · Module = Attach when you need it · Labs = Prototype; no GA promise
Stream, game, IoT, and fleet write D1 and fan out on the room. The deep links open the console page; everything else on this page stays labs.
Start with a room that is not a lab.
Chat core is the baseline. Add a Worker surface when the flow needs it. Keep the prototype on the side until it earns a customer.