Pricing
A pageview and a custom event count the same. AI messages are never metered — the digest is deterministic anyway, so rationing it would be manufactured scarcity. And the open-source core is free forever, on your own server, with no feature held back.
Going over your limit does not cut you off. Collection continues inside a 20% grace band, with a warning in the dashboard from 80% onward. Analytics you failed to collect never comes back — so we would rather warn you than blind you.
Every analysis feature is in every plan. What changes is volume, retention and team size.
| Free | Starter | Pro | Enterprise | |
|---|---|---|---|---|
| Monthly events | 10K | 100K | 1M | Unlimited |
| Data retention | 180 days | 2 years | 5 years | Unlimited |
| Sites | 1 | 10 | 100 | Unlimited |
| Team members | 1 | 3 | 25 | Unlimited |
| Evidence panel | Included | Included | Included | Included |
| AI messages metered | Never | Never | Never | Never |
| Funnels & retention | Included | Included | Included | Included |
| Web Vitals & errors | Included | Included | Included | Included |
| MCP server | — | Included | Included | Included |
| Slack & email digest | Email only | Included | Included | Included |
| Self-hosting | Always free | Always free | Always free | Always free |
A pageview and a custom event each count as one. Web Vitals and error reports are custom events, so they count too — which is worth knowing before you enable them on a high-traffic site. AI crawler requests are stored but do not count against your quota: you did not ask GPTBot to visit, so you should not pay for it.
From 80% you see a warning in the dashboard. Past 100% data keeps flowing up to 120% of your limit. Above that new events are rejected — and the rejected count is shown to you rather than hidden, because a silent data loss is the worst possible outcome for an analytics tool.
Yes, and it is free forever. The core is Apache-2.0 with no runtime dependencies — one process and an embedded database. The cloud plans exist for people who would rather not run it, not because the self-hosted build is crippled. See self-host vs cloud.
No. We set no cookies and store no identifier in the browser, so there is nothing to consent to under the ePrivacy Directive. Strict mode goes further still — see privacy modes.
Card and the usual local methods through Paddle, who act as merchant of record and handle VAT for us. Annual billing is the price shown; monthly is available at a small premium.
Any time, from the dashboard. Downgrading keeps your data until it passes the retention window of the new plan; nothing is deleted the moment you change.
Yes — get in touch through contact with a link to the project.
One script tag. No card, no cookie banner, no consent flow.
Get started free →