Free
1M requests / month100 req/s sustained
The whole request path, minus the API and AI gateways.
- DNS with DNSSEC
- TLS + automatic certificates
- L4 admission + DDoS controls
- WAF and bot management
- CDN cache
- No AI gateway
- No overage — hard quota
Plans
Pick the package, not the pieces
A package is a set of rules: which layers are enabled, what the quotas are, and what the sustained rate limit is. Those rules are compiled into your configuration and enforced at the edge — a layer your plan does not include is simply not in your request chain.
Pro
50M requests / month2,000 req/s sustained
Adds the API gateway and the AI gateway.
- Everything in Free
- API gateway — keys, JWT, OIDC, scopes, quotas
- API shield — OpenAPI contract enforcement
- AI gateway — guards, metering, budgets
- Overage billing rather than a hard stop
- 5M AI tokens / month
- Overage allowed
Business
500M requests / month20,000 req/s sustained
The same capabilities at ten times the volume.
- Everything in Pro
- Custom WAF rules
- Higher quotas across every layer
- 100M AI tokens / month
- Overage allowed
Enterprise
Custom request volume200,000 req/s sustained
Every layer, with the limits set to your traffic.
- Every layer enabled
- Negotiated quotas and rate limits
- Custom overage terms
- Custom AI token budget
- Overage allowed
Pricing
Package prices are quoted rather than listed here. Quotas, rate limits and the enabled layers above are the whole of what a package changes — everything else about the platform is identical on every plan.
How limits behave
What happens at the edge of a plan
Rate limit
The sustained figure is a token bucket, not a fixed window: a burst above it is absorbed from the bucket rather than refused, and a request that exceeds it gets a 429. That is why a spike at the top of the minute does not get double-counted the way a fixed window would.
Monthly quota
Counted from the same per-layer events that feed your analytics, per node and reconciled centrally. Over quota, a plan with overage keeps serving and bills the excess; a plan without one stops.
Enabled layers
Not a feature flag checked per request — the layer is left out of the compiled chain entirely, so it costs nothing to be on a plan without it.
Changing plan
A change recompiles your configuration and rolls out like any other. Sites beyond a smaller plan’s allowance are disabled rather than deleted, and a later upgrade re-enables exactly those.