By workload
Bidirectional.
Sub-millisecond.
WebSocket, Server-Sent Events, and wRPC. Three protocols, one platform, zero configuration overhead.
Explore the details
Make collaboration feel immediate.
Edit the document title and simulate a collaborator's update. Both views share local state, making every reconciliation visible without a network connection.
Shared documentYou + Sam · sample
Confirm production configuration
Sam
Review release notes
Share the launch with the team
Illustrative presence. No other person is connected to this example.
Synchronized view
rev 1Launch checklist
The review is open. Edit the title or simulate an update.
Local example onlyProtocols
The right protocol for every use case.
WebSocket
DirectionBidirectional
Latency<1ms
OverheadMedium
Chat, collaboration, gaming
Full-duplex connections
Auto-reconnection + heartbeat
Per-connection auth
Horizontal scaling across regions
Server-Sent Events
DirectionServer → Client
Latency<5ms
OverheadLow
Live feeds, notifications, dashboards
One-way event streams
Native browser support
No WebSocket overhead
Built-in reconnection
wRPC
DirectionBidirectional
Latency<0.5ms
OverheadMinimal
Inter-component calls, service mesh
WASM-native RPC
Type-safe contracts
Binary serialization
Sub-ms between components
Architecture
Connection to storage in one hop.
ClientBrowser, mobile, IoT device
EdgeTLS termination + routing
HiveWASM runtime + state
SilosPersistent storage
Real-time starts
with one deploy.
WebSocket, SSE, or wRPC. Pick a protocol and ship.