Realtime data and chat
Plan WebSocket or SSE streams for chat, live order status and collaboration. Evaluate connections, message volume and channel authorization together.
How to design the workflow
Mobile connections drop and reconnect. Design event cursors, sequence numbers, reconnect backoff and slow-consumer limits. Private messages must not cross tenant channels.
Cost and service boundaries
Monthly active users do not equal concurrent connections. Load-test message fan-out, egress and memory. Managed realtime clusters and unlimited connection packages are not available.
Pre-launch checklist
Validate these steps in your app and with the providers you choose. Measure concurrent load alongside CPU, memory and storage before selecting a plan.
- Authorize room membership on subscription.
- Recover missed events after reconnection.
- Bound message size and concurrent connections.
Common questions
Is this service available today?
This page describes a service plan and architecture. Managed customer services are not enabled; publication does not activate resources or integrations.
Which plan should I consider?
Consider the resource scope of Pro. This is not a capacity guarantee; validate it against application load and external provider fees.