Pricing
Priced on traffic measured, not on people identified.
Every plan is aggregate-only and enforces the same twelve invariants. What changes between them is volume, the dimensions your jurisdiction profile permits, and how much evidence your reviewers need in the box.
Standard
For a single product with straightforward jurisdiction requirements.
Tailored
Single product · standard traffic profile
- Operational lane and aggregate dashboard
- 1, 7 and 14-day deduplication windows
- Bot classification and abuse-rate summary
- Country, device, OS and page-group dimensions
- Modelled monthly uniques with 90% intervals
- Standard suppression threshold
Most common
Regulated
For teams whose reviewers need the evidence, not just the dashboard.
Tailored
Regulated product · enhanced evidence
- Everything in Standard
- Jurisdiction profiles, including conservative EU defaults
- 30-day windows subject to approval reference
- Regional, ISP and connection-type dimensions where permitted
- Evidence pack: invariant results and destruction logs
- Signed, hash-chained deletion records
- Configurable suppression threshold
Enterprise
Multi-brand estates, unusual jurisdictions, or private deployment.
Talk to us
Multi-brand · private or managed deployment
- Everything in Regulated
- Multiple tenants with isolated keys and row policies
- Custom jurisdiction profiles and approval workflows
- Private edge deployment in your own Cloudflare account
- Named reviewer support through your DPIA
- Contractual invariant commitments
Pilot and production terms are confirmed after a traffic, jurisdiction and evidence review. We do not publish placeholder prices as if they were agreed commercials.
Questions
The ones that come up first.
- Why is pricing based on requests rather than visitors?
- Because there are no visitor records to count. The system holds aggregate sketches, not people. Billing on measured requests is the only unit that reflects what the platform actually does, and it means our commercial interest never depends on identifying anyone.
- Does this replace our existing analytics?
- No. It sits alongside it. Your consented analytics keeps doing what it does; INSIGHTS measures the operational shape of the traffic that consented analytics is not permitted to see, and reports it separately and honestly as measured or modelled.
- Do we still need a consent banner?
- Your obligations are yours to determine with your own advisers, and nothing here is legal advice. What we can say precisely is what the operational lane does: no client-side storage, no fingerprinting inputs, no persistence of IP or user-agent, and no capability to recognise a returning person. The evidence pack is built to support that assessment rather than to substitute for it.
- What happens to the data if we leave?
- The aggregate sketches are deleted on the schedule in your contract, and the deletion is evidenced by a signed, hash-chained record you can verify independently. There is no raw visitor data to return or destroy, because none was ever kept.
- Can we self-host or run it in our own cloud?
- The edge collector can run in your own Cloudflare account on the Enterprise plan. Full private deployment of the aggregation and modelling tiers is available for regulated estates. Talk to us about the shape of it.