Pricing
Room to grow. Clear costs.
Choose a base plan, then pay for messages, connection minutes, and channel minutes. Explore monthly billing or long-term access.
Estimate your cost
Enter your expected usage to see a cost breakdown.
What could smaller payloads mean for your traffic?
Compare the actual payload sizes you send. Compact encodings can reduce bandwidth; the difference depends on your data and chosen format. Message volume and connection time remain separate considerations.
Small payloads add up
Compare your payload volume
Enter 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 a delivery: one event sent to 100 clients is 100 payload deliveries.
- JSON payload volume
- 48 MB
- Binary payload volume
- 32 MB
16 MB less payload data per month with this binary encoding.
Payload volume only; excludes protocol overhead, compression, retries, and connection traffic. Lower bandwidth can reduce costs where your infrastructure charges by transferred bytes. This is not a billing estimate or a promise of a lower Celeris bill.
How we measured the example →Pricing FAQ
† p95 32ms round-trip measured on a single AWS c8g.large EC2 instance during a 25-minute sustained test at 96,114 msg/s. Latency includes k6 test-client overhead. Production latency at lower sustained throughput will typically be lower.