WebSocket limits
Per-plan WebSocket caps: concurrent connections, subscriptions per connection, and total subscriptions per plan from STARTER to PROFESSIONAL.
// updated 2026-06-04
All WebSocket limits by plan.
What are the WebSocket connection and subscription limits?
| Limit | STARTER | FOCUS | BUILD | GROW | PROFESSIONAL | Dedicated |
|---|---|---|---|---|---|---|
| Concurrent WS connections | 10 | 20 | 30 | 40 | 70 | unlimited |
| Subscriptions per connection | 100 | 100 | 100 | 500 | 1,000 | unlimited |
| Total subscriptions per plan | 1,000 | 5,000 | 5,000 | 10,000 | 25,000 | unlimited |
| Idle timeout | 10 min | 10 min | 10 min | 10 min | 10 min | 10 min |
| Required ping interval | ≤60 sec | ≤60 sec | ≤60 sec | ≤60 sec | ≤60 sec | ≤60 sec |
NOTE
Total subs is a hard cap, not connections × subs/conn. See How pricing works.
STARTER: the WebSocket-first plan
STARTER ($40/mo) is the WebSocket-friendly entry plan - no gRPC, lower RPS - with 10 concurrent WS connections at the lowest price. STARTER users typically run browser clients or lightweight listeners. WS connection caps then scale up with each tier (FOCUS 20, BUILD 30, GROW 40, PROFESSIONAL 70).
RPS counts subscribe and unsubscribe
Incoming subscribe / unsubscribe commands count against your RPS limit, the same as RPC requests. This is a deliberate anti-abuse measure.
What happens when you hit a limit
- Connection limit exceeded - new connection rejected.
- Subscription limit exceeded - subscribe call returns an error, existing subscriptions keep working.
- RPS exceeded -
429. Calculated over a 10-second sliding window.