# Soketify pricing

Six plans from $0/month to $299/month. No per-message fees, no connection overage fees, no surprise bills.

Canonical page: https://soketify.com/pricing · Last reviewed: 2026-08-21

## Pricing

Every plan is a flat monthly fee. There is no per-message charge, no
per-connection overage charge, and no separate charge for large event payloads.

| Plan | Price (USD/month) | Concurrent connections | Messages / month | Apps | Max event payload |
| --- | --- | --- | --- | --- | --- |
| Free | $0 | 200 | 6,000,000 | 3 | 100 KB |
| Indie | $9 | 500 | 50,000,000 | 5 | 256 KB |
| Startup | $19 | 2,000 | 150,000,000 | 10 | 512 KB |
| Scale | $59 | 6,000 | 400,000,000 | 15 | 1 MB |
| Scale-1 | $149 | 10,000 | 1,000,000,000 | 25 | 2 MB |
| Scale-2 | $299 | 20,000 | 1,800,000,000 | 50 | 4 MB |

Plans can be changed at any time and take effect immediately. The Free plan
needs no credit card.

### Cost against Pusher at comparable usage

| Usage | Pusher (estimated) | Soketify | Difference |
| --- | --- | --- | --- |
| 200 concurrent connections, 6M messages/month | $0/mo | $0/mo | Both free |
| 500 concurrent connections, 30M messages/month | $49/mo | $9/mo | About 82% less |
| 1,000 concurrent connections, 100M messages/month | $299/mo | $19/mo | About 94% less |
| 2,000 concurrent connections, 400M messages/month | $599/mo | $59/mo | About 90% less |
| 10,000 concurrent connections, 1B+ messages/month | Sales call required | $149/mo | Pusher requires a sales call; Soketify stays list-priced |

Pusher figures are estimates from published Pusher Channels pricing as of 2026
and can change. Soketify figures are list prices. Pusher's default maximum event
size is 10 KB, above which it requires a paid add-on, and it does not deliver
events larger than 256 KB at any price; Soketify includes 100 KB on
Free and up to 4 MB on the top plan at no extra charge.

## Routing, regions, reliability

- One endpoint for WebSocket traffic (ws.soketify.com) and one for the REST API
  (api.soketify.com). Clients are routed to the nearest healthy node
  automatically.
- Regions serving traffic today: US East, US West, EU Central.
- All clients of one app can exchange messages regardless of the region they
  connected from.
- Uptime target on paid plans is 99.99%. The Free plan carries no SLA and runs
  on the same infrastructure. Live and historical status: https://status.soketify.com.
- All traffic is encrypted in transit (WSS and HTTPS). For payloads the platform
  itself cannot read, use the protocol's encrypted channels.

## Secrets and limits

- An app can hold several secrets active at once, each labelled, so rotation is
  deploy-the-new-one, then revoke-the-old-one, with no downtime and no failed
  authorizations during the overlap.
- Plan limits cover concurrent connections, messages per month, number of apps,
  and maximum event payload size.
- Crossing a limit sends a notification at 80% and at 100% and starts a grace
  period. Connections are not cut, messages are not dropped, and no overage is
  invoiced.

## Frequently asked questions

### How does Soketify pricing work?

Soketify charges a flat monthly fee per plan, from $0 on Free to $299 per month on Scale-2. Each plan sets a ceiling on concurrent connections, messages per month, number of apps, and maximum event payload size. There is no per-message billing and no overage charge.

### What are the event payload size limits?

The maximum event payload runs from 100 KB on Free, to 256 KB on Indie, 512 KB on Startup, 1 MB on Scale, 2 MB on Scale-1, and 4 MB on Scale-2. Limits are enforced per app before fan-out. Pusher's comparable default is 10 KB, with a hard cap of 256 KB even with its paid add-on.

### What happens if I exceed my plan limits?

Soketify notifies you at 80% and 100% of your limits and your service keeps running. Connections are not hard-stopped and messages are not dropped, and you get a grace period to upgrade or optimize instead of an overage bill.

### How do I rotate API secrets?

Each app can hold several secrets active at the same time, each with its own label. You create a new secret, deploy it to your servers while the old one is still valid, then revoke the old one once nothing signs with it. Because both secrets verify during the overlap, rotation causes no downtime and no failed authorizations.