Pay for delivered bytes
Egress is metered per gigabyte leaving the edge. Requests, TLS, purges and the control API are included at every tier.
Starter
Side projects and staging origins.
- 100 GB egress included
- 2 zones
- Automatic TLS
- Community support
Growth
Production sites with real traffic.
- 2 TB egress included
- 25 zones
- Origin shielding + edge rules
- Prometheus metrics export
Scale
High volume and committed use.
- Unlimited zones
- Dedicated shield capacity
- Custom cache tiering
- Priority incident routing
What counts as billable egress
| Traffic | Billed | Note |
|---|---|---|
| Cache hits served to visitors | yes | Metered per GB at the edge |
| Origin fetches (edge to origin) | no | Not charged on our side |
| Purge and control API calls | no | Rate limited, never metered |
| TLS handshakes and redirects | no | Included at all tiers |
Prices exclude VAT where applicable. Included allowances reset monthly and do not roll over.
Questions people actually ask
Is there a request charge?
No. Requests, including cache misses and revalidations, are not billed separately - only bytes delivered from the edge.
Can I cap spend?
Yes. Set a monthly ceiling per account; once reached, zones fall back to origin-direct rather than accruing further charges.
Do you charge for certificates?
No. Issuance and renewal are automatic and included, including for hostnames added later.
What happens on overage?
Traffic keeps flowing and the excess is billed at the tier rate. Nothing is throttled or cut off mid-month.