Getting started
Core concepts
The vocabulary for the active Woven Host managed path, followed by the capabilities that remain Preview.
Woven Host lifecycle
- Product
- The console resource you create and allocate capacity to. Its product ID is distinct from the Woven protocol namespace and session IDs assigned at provisioning.
- Capacity allocation
- Capacity = tick rate (Hz) × allocated CCU (concurrent users). New sign-ins remain guest with zero capacity until approved. The approved Lite default is 250 capacity units, shared across products; Pro defaults to 2,500 units. Custom approved budgets are preserved.
- Running
- The lifecycle state that confirms the managed runtime is ready for descriptor reveal and client admission. Treat Running as the authoritative readiness signal.
- Connection descriptor
- The sensitive connection material explicitly revealed for a Running product. Use its native or browser endpoint, trust information, Bearer credential, and assigned protocol identifiers as returned rather than deriving replacements from the product ID.
Realtime connection
- Rust client
- The Rust
woven-clientconnects to the descriptor's native QUIC endpoint with TLS verification enabled. - TypeScript client
- The Online browser client carries WVN1 over WebTransport and HTTP/3/QUIC to the same managed runtime through the descriptor's separate
webTransport.urlendpoint. - Bearer authentication
- The client presents the descriptor's Bearer credential during the secure connection. It is runtime admission material, separate from the identity used to sign in to the Woven Host console.
- Managed admission
- The runtime validates the managed credential and admits the connection to the namespace and session assigned by Woven Host. The descriptor supplies those IDs.
- Logical space
- The descriptor returns fixed logical spaces plus complete managed 3D Spatial Subspace definitions. Host allocates numeric IDs from 3, enforces AABB bounds, and permits at most 64 add-only spatial definitions per server generation.
- Channel and Ephemeral events
- The descriptor returns the fixed channel used by the managed session. Its events are Ephemeral: connected recipients receive live traffic, and the event lifetime ends with the runtime state.
Availability
- Lite
- The active entry tier: a 250-unit default capacity budget, managed product lifecycle, descriptor reveal, native Rust QUIC, browser WebTransport, the TypeScript browser client, and managed spatial routing.
- Pro and Dedicated
- Preview tiers offered through private founder access first.
- Persistence
- Ephemeral events are the active managed data model. Persistence beyond Ephemeral remains Preview.
- Inference
- Inference is Preview, with private founder access first.