Rate Limits and Operational Limits
Status: PUBLIC_CONTRACT_DRAFT. This page describes the planned rate limit model. Plan-based limits are documented intent. No SLA guarantee. It is not a production-live availability claim.
Audience
Customer / developer planning integration capacity.
Plans and Quotas
| Tier | Webhooks / Month | Max Payload | Max Endpoints | Max Destinations |
|---|---|---|---|---|
| Free Forever | 25,000 | 256 KB | 3 | 3 |
| Pro — Early Bird | 500,000 | 1 MB | 50 | 25 |
| Business (Coming Soon) | Custom | Custom | Custom | Custom |
| Enterprise (Contact Us) | Custom | Custom | Custom | Custom |
Rate-limited requests receive a 429 Too Many Requests response with a Retry-After header.
Delivery Operational Limits
| Parameter | Default | Configurable |
|---|---|---|
| Retry attempts | 5 | Yes |
| Retry backoff | Exponential (1s → 60s) | Yes |
| DLQ retention | 7 days | Yes |
| Delivery timeout | 30s | Yes |
| Max fan-out destinations | 10 | Yes |
Versioning
See API Versioning and Compatibility.
How Webhooks Are Counted
- A webhook is counted when Zen Mesh receives an inbound webhook request at an endpoint.
- Provider retries count as additional inbound webhooks.
- Zen Mesh internal delivery retries do not count as additional webhooks.
- Filtered or dropped requests may count against abuse and rate limits even if they are not delivered downstream.
Non-Claims
- These limits apply per deployment and tenant configuration
- Limits may be adjusted during maintenance windows
- No SLA or uptime guarantee is made for any rate limit threshold
- Production deployments may have different limits than sandbox/staging