Limits and quotas
What each plan includes. These numbers come from the same catalog the service enforces, so this page is always current.
| Limit | Applies | Free | Starter | Pro |
|---|---|---|---|---|
| Apps | per organization | 2 | 10 | 25 |
| Concurrent connections | per app | 100 | 500 | 2,000 |
| Publishes per second | per app | 100 | 200 | 500 |
| Client events per second | per connection | 50 | 100 | 200 |
| Read requests per second | per app | 100 | 200 | 500 |
| Messages per day | per organization | 100,000 | 1,000,000 | 5,000,000 |
| Largest event | per event | 10 KB | 10 KB | 10 KB |
| Presence members | per channel | 100 | 100 | 250 |
| Webhook endpoints | per app | 1 | 5 | 20 |
| Team seats | per organization | 1 | 3 | 10 |
| Usage history | 7 days | 30 days | 90 days |
Paid plans are not available to buy yet, and their numbers may change before they are. Need something else? Write to the support address on the site.
What happens at a limit
- Connections: the next client to connect is refused with close code
4100until one disconnects. - Publishes and reads: the request is refused with
code: 429in the response body (HTTP status 200, see the HTTP API). - Client events: a client that sends too many gets
pusher:errorwith code4301; the extra events are dropped. - Event size: a publish bigger than the limit is refused with
code: 413; an oversized client event gets4301. - Apps and seats: creating another app, or inviting another teammate, is blocked until you free one or change plan. Existing apps keep working if a plan shrinks.
What counts as a message
A message is anything the service sends to a connected client. An event published to a channel with 100 subscribers is 100 messages, because each subscriber receives it. Each connection also costs two messages when it is set up: the connection confirmation and the subscription confirmation. Your app's Usage tab shows the same figure, counted in UTC days like the daily quota.
Fixed limits
These are the same on every plan.
- Channel names and event names: 200 characters.
- Channels in one publish request: 100.
- Events in one batch request: 10.
- Presence member info: about 2 KB per member.
When a limit change applies
Connection, publish, read and event-size limits are looked up when a client connects or a request arrives. If you change plan, new connections and new requests use the new limits immediately. Settings a client carries from the moment it connected (client events, the client event rate) change for connections opened afterwards.