Pricing
Room to grow. Clear costs.
You select a base plan, and then you pay for messages, connection minutes, and channel minutes. Celeris offers monthly billing and long-term access.
Estimate your cost
Enter your expected usage to see a cost breakdown.
What could smaller payloads mean for your traffic?
This tool compares the payload sizes that you send. Compact encodings can decrease the bandwidth. The results depend on your data and on your format. The message volume and the connection time are separate costs.
Small payloads add up
Compare your payload volume
Enter the measured sizes for the same data in each format. The defaults use our position update: 48 bytes of JSON and 32 bytes of MessagePack.
Use whole numbers, including zero. Count each recipient as one delivery: one message to 100 clients makes 100 payload deliveries.
- JSON payload volume
- 48 MB
- Binary payload volume
- 32 MB
This binary encoding moves 16 MB less payload data per month.
This result shows the payload volume only. It excludes the protocol overhead, compression, retries, and connection traffic. Lower bandwidth can decrease costs where your infrastructure charges for transferred bytes. This is not a billing estimate or a promise of a lower Celeris bill.
How we measured the example →Questions?
The limits page shows how Celeris applies each limit and how Celeris counts messages. The FAQ page gives answers about billing, the SDKs, and support.
† We measured a p95 32ms round-trip on one AWS EC2 instance of the type c8g.large during a 25-minute sustained test at 96,114 msg/s. The latency includes the k6 test-client overhead. Production latency at a lower sustained throughput is typically lower.