Plans and limits
What the Free plan includes, which limits you will actually notice, and what is coming.
ChangeTrace is free to use today. Pro and Agency plans are being built.
Free
| Sites | 1 |
| Team members | 1 |
| History | 7 days |
| Root-cause depth | Basic — the single most likely cause |
| AI investigations | 10 per month |
| Change tracking | Yes |
| Error tracking | Yes |
| Revenue and order monitoring | Yes |
| Uptime monitoring | Yes |
| Incident email alerts | Yes |
| Performance impact | No |
Pro and Agency
Listed as coming soon: more sites, longer history, the full ranked cause list, performance impact, and collaboration features for agencies running many client sites. There is a waiting list on change-trace.com.
There is no upgrade button in the dashboard yet, deliberately — self-serve billing is not live.
The limits you will actually notice
History — 7 days
The one that bites first. Every night, events and metrics older than 7 days are deleted, and dashboard date ranges are capped to match. You cannot compare this month against last.
Note that anomaly detection needs a 7-day baseline, so on Free the detector is working with essentially the whole window it has.
Incidents themselves outlive the raw data — an older incident keeps its title and ranked causes while its underlying timeline ages out.
One site
Registering a second gives: "Site limit reached for the free plan (1). Upgrade to add more sites."
This includes staging. If you want to monitor a staging copy, it costs your one slot.
Basic root-cause depth
You get the single best-scoring cause rather than the full ranked list, and without the supporting error chains. Usually enough — the top candidate is the one you check first anyway — but you lose the ability to look past it when the top candidate is obviously innocent.
One team member
Your member count is displayed but there is no invite screen yet, so this is not a limit you can hit by accident.
Ten AI investigations a month
Per user, on UTC calendar months. Explanations and Ask ChangeTrace questions both draw on it; failed requests are refunded. Need more before Pro exists? Use your own API key — unmetered, billed by your provider.
Changing plan
Not self-serve yet. Use the Need help? widget with the Billing / Plan category.
What no plan changes
These are the same for everyone:
- Uptime monitoring — 5-minute checks, 2 failures to open an incident
- Detection thresholds — 40% and 3σ to open, 70% for critical
- Email alerting — critical only, to organization owners
- What the plugin collects, and what it strips out
- Cron cadences
{ }For developers
organizations.plan is free | pro | agency and is the single source of truth, resolved through
the entitlements service. It is enforced at four points: the site cap on registration (409), the
team-member cap in the Clerk webhook, retention plus the dashboard read clamp (both sides, so
lingering rows still cannot be read), and correlation depth. Premium routes use a feature guard;
today only the performance-impact controller is gated that way. Plans are set manually in SQL —
Stripe is a later phase.