OakData vs Umami
Umami gives you the numbers. OakData gives you the people.
Umami is MIT-licensed, cookieless analytics you can self-host free, with replay and heatmaps arriving in v3. OakData is the managed, person-level version of that whole stack.
Umami has grown from a minimal open-source pageview counter into a genuinely capable suite: funnels, retention, UTM attribution, segments, revenue values on events, and, in the v3 releases, Core Web Vitals, session replay, and heatmaps. It stays cookieless, the tracker is under 2 KB, and the MIT license means you can self-host every bit of it for free. That last part is its trump card, and nothing OakData offers replaces it.
The trade-offs are in identity, depth, and the Cloud pricing ladder. Visitors are anonymous by design, so there are no durable profiles or journeys across visits. There's no error monitoring, revenue is generic event values rather than a billing integration, bot handling is a silent user-agent exclusion, and AI agent access exists only as community projects. And on Umami Cloud, replay and heatmaps start on the $200 a month Business plan, where OakData includes them for everyone.
Side by side
 OakData | Umami | |
|---|---|---|
| Person-level profiles | Yes | No, anonymous by design |
| Session replay | Included, every plan | Self-host, or Cloud Business ($200/month) |
| Heatmaps | Included, every plan | Self-host, or Cloud Business ($200/month) |
| Funnels & retention | Yes | Yes |
| Error monitoring | Yes | No |
| Core Web Vitals | Yes | Yes |
| Stripe revenue & MRR | Built-in, read-only key | Generic revenue values on events |
| Bot filtering | Layered: UA, IP ranges, ASN, headless | Silent UA exclusion |
| AI agent access (MCP) | Yes | Community servers only |
| Cookie-free | Yes | Yes |
| Open source / self-host | No | MIT license, self-host free |
| Script size | Heavier (replay + autocapture included) | Under 2 KB (+ recorder script for replay) |
| Pricing | One plan, all features, usage-based | Self-host free; Cloud $0, $20, $200 tiers |
Based on publicly available information as of July 2026. Features and pricing change, so verify anything decision-critical against Umami's current site.
Choose OakData if…
- You need to recognize people across visits: Umami's sessions are anonymous by design, so journeys and cohorts of real users don't exist.
- You want replay and heatmaps without either running your own Postgres and recorder or paying Cloud's $200 a month Business tier.
- Revenue means your billing reality: OakData reads Stripe MRR and lifetime value per person, not hand-tagged event values.
- You want errors, layered bot filtering, and an official MCP server in the same product.
Choose Umami if…
- Self-hosting on your own infrastructure under an MIT license is the requirement. That's Umami's unbeatable card.
- You want a genuinely free, cookieless counter: 100K events a month on Cloud's Hobby tier, or unlimited if you host it.
- A sub-2 KB script on a content site matters more than person-level depth.
Questions
Self-hosted, yes: MIT-licensed and unlimited, if you run the PostgreSQL database and keep it updated. Umami Cloud is free to 100K events on one website, then $20 a month, with replay and heatmaps arriving only on the $200 Business tier. OakData is a managed product: 14-day trial, then one usage-based price with everything included.
Umami's replay (added in v3.1) is a solid rrweb-based implementation, but it's opt-in per site with a second script, samples around 15% of sessions by default, caps recordings at five minutes, and keeps them 30 days. OakData records sessions as part of the core snippet and attaches them to durable person profiles alongside events, errors, and revenue.
No, deliberately: Umami's docs state users cannot be identified or tracked across websites, and there are no profile pages or identify() flows. That's a principled privacy stance. If you need to know which visitor returned four times before subscribing, that's the layer OakData exists for.
One script swap, and you can run both while comparing. OakData autocaptures from the first pageview, so events you were hand-tagging in Umami (plus replay, errors, and Web Vitals) work without configuration.
More comparisons