Realtime settings and limits
Decide who may connect to realtime, cap clients, events per second and message size per project, and know the organization-wide limits of your plan.
Realtime › Settings controls who may connect and how much one connection may send. What a connection may join or publish on is decided per channel by your rules.
| Setting | What it does |
|---|---|
| Allow public access | Off: only signed-in users can connect; connections that use only a project key are refused. |
| Max concurrent clients | Per project, on top of your plan’s limit for the organization. 0 uses the plan limit. |
| Max events per second | Messages one connection may send each second. Extra messages are rejected with rate_limited. |
| Max message size | In KB. Larger messages are rejected with payload_too_large. |
Who may join or publish on a channel is decided by your rules (realtime:subscribe, realtime:publish) — see Security, policies and audit.
Plan limits
Messages are a monthly allowance: Free stops at it, paid plans are billed beyond.
| Free | Pro | Ultra | Team | Enterprise | |
|---|---|---|---|---|---|
| Monthly realtime messages | 2,000,000 | 5,000,000 | 15,000,000 | 75,000,000 | 300,000,000 |
| Concurrent realtime connections | 100 | 500 | 1,500 | 5,000 | 20,000 |
| Realtime channels | 20 | 500 | 5,000 | 20,000 | 100,000 |
| Realtime connections per signed-in user | 20 | 50 | 100 | 200 | 500 |
| Largest realtime message | 0 MB | 0 MB | 0 MB | 0 MB | 0 MB |
| Recent realtime messages kept per channel for replay | 1,000 | 1,000 | 1,000 | 1,000 | 1,000 |
Something unclear or missing on this page?Tell us