No Usage Limits

The Better Messages WebSocket service has no caps on concurrent connections, monthly active users, or message volume. Whether your site has 100 or 100,000 active users, the service works the same way — same pricing, same performance, no throttling, no overage charges, no surprise bills.

WebSocket version

Flat-rate pricing is one of the most unusual things about the WebSocket version compared to typical SaaS chat services, which usually charge per-connection or per-message.

What it adds#

No limit on concurrent WebSocket connections
No limit on monthly active users
No limit on message volume
No throttling, no rate limiting on the WebSocket service
Equal infrastructure access for every license holder regardless of site size
Predictable flat-rate pricing — your bill doesn't scale with success

Pricing models compared#

Approach	What's included	Pricing model	Typical cost at 10K MAU
Better Messages WebSocket	Messaging, voice / video calls, group calls, Cloud AI (moderation / translation / transcription), web push, mobile apps	Flat per-site license	License is the only cost
Realtime-as-a-service platforms	WebSocket pub / sub only — calls, AI, push billed separately	Per-connection and / or per-message	Several hundred to thousands per month
Chat-as-a-service platforms	Messaging only — calls, AI, push usually billed separately	Per monthly active user (MAU)	Hundreds to thousands per month
Build your own relay	Whatever you build	Your infrastructure + your team	Hosting + dev time + ongoing maintenance

The comparison isn't apples-to-apples — the WebSocket plan bundles call infrastructure, AI services, and push delivery that other approaches charge for separately. On like-for-like infrastructure (messaging + calls + AI + push), the savings widen significantly.

For sites with growth ambitions, the flat-rate license is economically predictable in a way that per-user or per-connection pricing isn't.

How it works#

The Better Messages cloud relay infrastructure scales automatically. New connections are distributed across the relay fleet. There's no per-tenant cap — your site competes with no one for capacity, and the system grows with aggregate platform traffic.

If your site experiences a sudden traffic surge (viral post, product launch), the WebSocket service absorbs it without rate limits. Messages continue to flow instantly even at peak load.

Frequently asked questions#

Are there ANY soft limits I should know about?#

For pathological cases — a single user sending hundreds of messages per minute (clearly abuse) — there are anti-abuse protections at the application layer. Normal usage doesn't hit them.

What if my site becomes huge — will pricing change?#

The WebSocket-version license pricing is the same regardless of site size. Sites with hundreds of thousands of users pay the same as sites with hundreds.

Does "no limits" include voice/video call participants?#

The voice/video call participant cap is 50 per audio call and 32 per video call by default. This is a per-call media-server limit, not a usage limit. Sites with regular higher-participant needs should discuss the self-hosted plan with support.

Is there a connection time limit?#

No — WebSocket connections stay open as long as the browser is open and connected. The infrastructure handles long-lived connections natively.

What's the SLA?#

99.5%+ uptime in practice. The infrastructure runs across multiple regions with automatic failover. See Servers location for the topology.