Plans and limits
What the Free and Pro plans include, how the monthly event allowance works, and what happens when it runs out.
Plans#
| Free | Pro | |
|---|---|---|
| Price | $0 | $50 a month |
| History shown | Last 7 days | Last 30 days |
| Events per month | 200,000 | 10,000,000 |
| Issues, alerts, webhooks, MCP server | Yes | Yes |
| Assistant and weekly digest | No | Yes |
Plans belong to the organization and cover all of its applications and environments. Raccoon keeps 30 days of events on both plans, so upgrading to Pro shows the rest of the month right away.
Upgrade#
An owner upgrades under Settings → Billing. Payment goes through Stripe Checkout, and Manage billing opens Stripe's portal for invoices, payment methods and canceling. After canceling, Pro stays on until the end of the paid period. Other members can see the plan but can't change it.
History on Free#
On Free, the period picker locks 14 and 30 days, and pages show the last 7 days at most. A link to a request, job or issue occurrence older than that opens an upgrade page instead. The MCP server has the same limit.
The event allowance#
Every record counts as one event: a request, a query, a job attempt, a log entry, a page view, an exception. A request that runs 20 queries and writes 3 log entries counts as at least 24 events. The count starts again on the first day of each month (UTC).
Settings → Usage shows the month's count against the allowance, events per day, and events per environment and type, for the last 12 months.
As the allowance runs out:
- At 80%, owners get an email, and every dashboard page shows a banner.
- At 100%, owners get a second email. Raccoon stops storing new events until the next month. The batch that crossed the limit is still stored.
Your apps aren't affected. The Nightwatch agent and raccoon-nodejs keep running normally, and Raccoon still answers their requests. The events just aren't stored, and Usage shows them as "Not stored". No issues open and no alerts fire for events that weren't stored.
To use fewer events, lower the Nightwatch package's sample rates, such as NIGHTWATCH_REQUEST_SAMPLE_RATE=0.1. Raccoon stores what arrives and doesn't scale the counts back up, so the dashboard's totals are for the sampled data.