Usage and retention limits
Monthly capture quotas, retained content and delivery windows are separate limits.
Monthly capture usage
These values describe configured backend limits, not a price quote or purchase offer. Billing UI figures are informational; the server determines admission. Other storage and delivery budgets still apply.
| Configured backend plan | Captures per month | Sources | Members | API keys |
|---|---|---|---|---|
| Free | 5,000 | 3 | 3 | 3 |
| Pro | 100,000 | 10 | 3 | 5 |
| Team | 1,000,000 | 50 | 10 | 20 |
| Enterprise | No fixed plan cap | No fixed plan cap | No fixed plan cap | No fixed plan cap |
Body and retained-content limits
- Maximum incoming body: 1 MiB; larger bodies are rejected with 413.
- Accepted async captures retain encrypted content for 30 days from original receipt, regardless of the plan’s legacy metadata-retention labels.
- Reading, automatic retries and manual replay do not extend expiry. Historical purged content has no backfill.
- Retained storage budget: 1 GiB globally, 256 MiB per organization, 100,000 rows globally and 25,000 per organization. Exhaustion rejects the entire capture with 503.
- Replay allows up to six delivery attempts in a 15-minute window clipped by content expiry. New replay is unavailable in the final ten seconds.
Billing and deployment
The dashboard shows configured plan, usage and downloadable activity reports. Self-service checkout, invoices, trials and automatic overage billing are not implemented. No automatic 80% email is promised; configured alert rules are a separate feature.
Infrastructure traffic policies are managed by the deployment operator. This page does not prescribe or certify request-per-second limits.