Plans and usage
What each plan includes and how to read your usage.
This page lists what each plan includes and what happens when a limit is reached.
Plans
Plans and their prices are being finalized. To change your organization's plan, write to [email protected].
| Free | Pro | Team | |
|---|---|---|---|
| Events per minute | 1,000 | 10,000 | 50,000 |
| Events per month | 5 million | 100 million | 500 million |
| Projects | 1 | 10 | 50 |
| API keys per project | 3 | 10 | 25 |
| Members | 1 | 5 | 25 |
| Channels per project | 2 | 10 | 25 |
| Channel types | Email, webhook | Email, webhook | |
| Shortest digest interval | 24 hours | 1 hour | 1 hour |
| Retention | 7 days | 30 days | 90 days |
| INFO summary window | 60 minutes | 15 minutes | 5 minutes |
| AI-written tickets and summaries per day | 20 | 500 | 2,500 |
Going over a count limit (projects, keys, members, channels) returns plan-limit-reached; going over the event rate or the monthly quota returns rate-limited. A user can create one organization on the free plan (free-org-limit).
Usage
Usage in the organization shows the plan, the events received this month (UTC) against the monthly quota, the projects and members in use against their limits, and the API keys allowed per project.
Daily AI budget
Each plan includes a number of AI-written tickets and INFO summaries per day (UTC). medium and low tickets and INFO summaries can use at most 70 % of it, so critical and high tickets always keep a reserve.
When the budget runs out, tickets and summaries are still written and delivered, built from the same facts (severity, service, occurrences, stack trace, surrounding log lines) but without the AI-written title, summary, probable cause and suggested fix. The budget resets at midnight UTC.
Retention
Error samples, tickets and INFO summaries are kept for the plan's retention period and then deleted. Error groups and their counts stay.