Account
Plan Limits Explained
What counts toward your limits, what happens when you reach them, and how to avoid surprises.
Each plan has four limits: sources, destinations, events per month, and retention. What counts toward each one, and what actually happens when you hit them, isn't always obvious from the plan page alone.
Sources
A source is one inbound webhook feed with a unique ingest URL. The limit is on the number of active sources in your workspace.
Only active sources count toward the source limit.
Destinations
A destination is a URL that receives forwarded events. The limit applies to the total number of active destinations across all sources in your workspace.
One source with three destinations attached counts as three destinations. Disabled destinations count toward the limit.
Events per month
Accepted non-duplicate events count toward monthly usage, including events with failed verification. Requests rejected before storage do not count. Ingest accepts supported HTTP methods, not just POST.
The count resets at the start of each UTC calendar month. You can check current usage in Settings → Usage.
What doesn't count:
- Replay requests (replaying an existing event doesn't create a new event count)
- Delivery attempts and retries (the event is counted once on ingest, not per retry)
What happens when you reach the event limit
When you reach 80% of your monthly event limit, you receive an email notification and an in-app alert.
When the limit is reached, ingest returns HTTP 403 before storing the event. The rejected payload cannot be inspected or replayed from Watchtower. Upgrade or wait for the UTC calendar-month reset, then request a provider resend if needed. Provider retry behavior varies: GitHub does not automatically redeliver failed requests.
Existing stored deliveries continue under their retry policy. Hitting quota does not create a stored queue of newly rejected events.
Retention
Retention is how long event data is kept after receipt. At the end of the retention window, events are permanently deleted and can't be replayed.
| Plan | Retention |
|---|---|
| Scout | 1 day |
| Guard | 7 days |
| Sentinel | 30 days |
| Bastion | 90 days |
Retention applies from the time the event was received, not from when it was last accessed.
Checking your usage
Go to Settings → Usage in your workspace to see:
- Events used this UTC calendar month
- Sources in use
- Destinations in use
- Days until the monthly counter resets
Upgrading before you hit a limit
Upgrade any time from Settings → Billing. The new limits take effect immediately. You don't need to wait for the next billing cycle. After an upgrade raises your allowance, new ingest requests can be accepted again. Previously rejected requests require a provider resend.
Need more help?
Check the FAQ for quick answers, or email hello@webhookwatchtower.co.uk . Include your event ID or workspace name to get a faster answer.