Comparison

BuddyStat vs Umami

Both are open source and cookieless, and both now have session replay and Web Vitals. BuddyStat adds error tracking, five-layer bot detection, and a read-write MCP server; Umami adds heatmaps and a free cloud tier.

7-day free trial. Cancel anytime.

Why consider BuddyStat over Umami?

Umami has grown well past pageview counts. Version 3.1.0 added session replays and Core Web Vitals, and 3.2.0 added click and scroll heatmaps. It also has funnels, journeys, retention, revenue, and attribution reports, so the two products now cover a lot of the same ground.

The differences that remain are specific. BuddyStat tracks JavaScript errors; Umami doesn't. BuddyStat filters bots through five detection layers and keeps what it blocked in a Bots report. Its MCP server has 44 tools and can create goals, save funnels, and manage sites, while Umami's MCP server is read-only. And on BuddyStat Cloud, Google Search Console clicks and impressions sit in the main dashboard.

Price and setup differ too. On Umami Cloud, replays and heatmaps start with the $200/mo Business plan, while BuddyStat Pro includes session replay from $39/mo. Umami is cheaper per event and has a free Hobby tier. Self-hosted, Umami is a Node.js app and one PostgreSQL database; BuddyStat is a Docker Compose stack built around ClickHouse, a columnar database designed for large event tables.

Comparison

Which is right for you?

Choose BuddyStat if...

  • You want JavaScript error tracking next to your traffic and sessions
  • You want session replay without a $200/mo plan (BuddyStat Pro starts at $39/mo)
  • You want bots filtered by five detection layers, with a report of what was blocked
  • You want an MCP server with write access (44 tools, including goals, funnels, and sites)
  • You want Google Search Console data in your analytics dashboard (BuddyStat Cloud)
  • You want to bring your Umami history with you through the built-in importer
  • You self-host at high volume and want your events in ClickHouse

Choose Umami if...

  • You want a free cloud tier (Hobby covers 100K events a month on one website)
  • You need click and scroll heatmaps
  • You want revenue and attribution reports built in
  • You prefer the MIT license to AGPL-3.0
  • You want the smallest tracking script (about 2.4KB compressed)
  • You'd rather self-host a Node.js app and one PostgreSQL database
  • You track millions of events a month and want the lowest price per event

Feature by feature

Why choose BuddyStat over Umami?

CapabilityBuddyStatUmami
Analytics Features
Real-time analytics
Custom events
With attributes
With properties
Funnels
User journeys
Retention
Conversion goals
Saved segments
UTM tracking
Revenue and attribution reports
Public dashboards
Advanced Features
Session replay
Pro plan, from $39/mo
Business plan, $200/mo
Click and scroll heatmaps
Business plan, $200/mo
Web Vitals monitoring
Error tracking
User profiles
Autocapture (clicks, forms, copy)
Bot filtering
5 layers + Bots report
Excludes bots by default
MCP server for AI assistants
Read and write, 44 tools
Read-only
Google Search Console data
Yes (Cloud)
Privacy & Open Source
Cookie-free tracking
No personal data collection
Visitor ID salt rotation
Daily (opt-in)
Monthly (default)
Open-source license
AGPL-3.0
MIT
Self-hostable
Technical & Pricing
Script size (compressed)
~11KB
~2.4KB
Self-hosted database
ClickHouse + Postgres
PostgreSQL
Ad-blocker bypass via proxy
API access
Cloud starting price
$19/mo
Free (Hobby)

Pricing

Pricing comparison

Events-based pricing

BuddyStat

$19/mo

  • 7-day free trial, card required at signup
  • Standard: 100k events, up to 5 sites and 3 team members
  • Pro ($39/mo) adds session replay (10,000 a month) and unlimited sites and members
  • Error tracking, funnels, journeys, and Web Vitals on both plans

Free tier + usage-based cloud

Umami

Free

  • Hobby: $0 for 100K events a month on 1 website
  • Pro: $20/mo for 1M events, with API and MCP access
  • Replays and heatmaps need Business at $200/mo
  • 14-day trial on paid plans; self-hosting is free (MIT)

Umami vs BuddyStat, in depth

Two open-source tools with a lot of overlap

Until Umami 3.1, the split between these two was easy to describe: both had traffic stats and reports, and BuddyStat added session replay and Web Vitals. That's no longer accurate. Umami 3.1.0 (April 2026) added session replays and Core Web Vitals (LCP, INP, CLS, FCP, and TTFB), and 3.2.0 added click and scroll heatmaps. Its docs also cover funnels, journeys, retention, goals, segments, cohorts, revenue, attribution, boards, and teams.
BuddyStat covers most of that list too, with session replay, funnels, user journeys, retention, Web Vitals, and user profiles. Both tools are cookieless and free to self-host. What separates them now is a shorter list of specific features, plus price, license, and how much infrastructure you want to run.

Where BuddyStat goes further

Error tracking is the clearest gap. BuddyStat captures uncaught JavaScript errors and unhandled promise rejections from your own domain, groups them in an Errors report, and shows each one in the session timeline next to the pages and events around it. Umami has no error tracking. BuddyStat's replays don't record console output, so errors show up in the Errors report and the session timeline rather than inside the replay.
Bot filtering is the second. Umami excludes bots by default. BuddyStat runs each tracking request through five detection layers (user-agent patterns, header checks, browser signals, ASN data, and rate anomalies), keeps what it blocked in a separate Bots report, and doesn't bill you for bot traffic.
Both ship an MCP server for AI assistants, and Umami's is read-only. BuddyStat's MCP server has 44 tools, including ones that create goals, save funnels, manage sites and team members, and run read-only SQL. On BuddyStat Cloud, Google Search Console clicks, impressions, and keywords also appear in the main dashboard.

Pricing and self-hosting, honestly

Umami Cloud's Hobby plan is free for 100K events a month on one website, with six months of data retention. Pro is $20/mo for 1M events, 20 websites, and 10 team members, and adds API and MCP access. Session replays and heatmaps start at Business: $200/mo for 10M events, with 5,000 replays included. Paid plans have a 14-day trial.
BuddyStat Cloud starts with a 7-day trial, and the card is collected at signup. Standard is $19/mo for 100k events, 5 sites, and 3 team members, with error tracking, funnels, journeys, retention, and Web Vitals included. Pro is $39/mo at the same volume and adds session replay (10,000 replays a month) plus unlimited sites and members.
Per event, Umami is cheaper: 1M events a month costs $20 on Umami Pro and $69 on BuddyStat Standard. Replays change the math. BuddyStat Pro costs less than Umami Business up to about 2M events a month ($39/mo at 100k, $139/mo at 1M), and Umami Business has the lower list price beyond that. Replay volume differs too: Umami Business includes 5,000 replays a month and charges $0.005 for each extra one, while BuddyStat Pro includes 10,000 replays for every 100k events in your plan. The full breakdown is on the pricing page.
Both self-host for free, and both include session replay when self-hosted. Umami is the lighter lift: a Node.js app and one PostgreSQL database. BuddyStat's self-hosted deployment is a Docker Compose stack with ClickHouse, Postgres, Redis, and a Caddy web server, installed by a setup script on a VPS (the guide recommends at least 2GB of RAM). ClickHouse is a columnar database built for aggregating large event tables, and that's what the extra services buy you.

Switching from Umami to BuddyStat

You don't have to start from zero. BuddyStat's importer reads Umami's CSV export (it also handles Plausible and Simple Analytics), so your historical traffic comes with you. A low-risk path looks like this:
  1. Add the BuddyStat tracking script and leave Umami running. Both are cookieless and the two scripts don't conflict, so running them side by side is safe.
  2. Import your Umami history with the built-in importer (the import guide walks through it). On BuddyStat Cloud, imported events count toward your monthly event limit, and imports reach back 3 years on Standard and 5 on Pro.
  3. Recreate your custom events and goals. Umami's events with properties map onto BuddyStat's custom events with attributes.
  4. Compare the two dashboards for a week or two. Once the numbers line up, remove the Umami script.

When Umami is the better choice

Plenty of sites should pick Umami. If your budget is $0, its Hobby tier covers 100K events a month on one site, while BuddyStat Cloud starts at $19/mo. If you want heatmaps, Umami has click and scroll heatmaps and BuddyStat has none. Umami also has revenue and attribution reports, which BuddyStat doesn't, an MIT license instead of AGPL-3.0, and a smaller tracking script (about 2.4KB compressed against BuddyStat's 11KB). BuddyStat is the better fit when you want error tracking beside your analytics, layered bot filtering with a report of what it blocked, replays without a $200/mo plan, or an MCP server that can make changes. For a wider survey of the options, see our guide to the best web analytics tools.

FAQ

Frequently asked questions

Both are open source and cookieless, and both have funnels, journeys, retention, session replay, and Web Vitals. BuddyStat adds JavaScript error tracking, five-layer bot filtering with a Bots report, an MCP server with write tools, and Google Search Console data on BuddyStat Cloud. Umami has click and scroll heatmaps, revenue and attribution reports, an MIT license, and a free Hobby tier.

Yes. Umami added session replays in v3.1.0 and click and scroll heatmaps in v3.2.0. On Umami Cloud, both need the Business plan ($200/mo, with 5,000 replays included); self-hosted Umami includes them. BuddyStat includes session replay on its Pro plan, from $39/mo with 10,000 replays a month, and on self-hosted installs. BuddyStat doesn't have heatmaps.

Yes, history included. Export your Umami data as CSV and load it with BuddyStat's built-in importer, then add the BuddyStat script and run both tools in parallel until the numbers line up. On BuddyStat Cloud, imported events count toward your monthly event limit.

Umami. It's a Node.js app with one PostgreSQL database. BuddyStat runs as a Docker Compose stack with ClickHouse, Postgres, and Redis, which is more to operate. ClickHouse is a columnar database built for aggregating large event tables, and that's the reason for the extra pieces.

Yes. BuddyStat's tracking script is about 11KB compressed and Umami's is about 2.4KB (measured in September 2026). BuddyStat's also carries error tracking, autocapture, and the browser signals its bot detection uses. Session replay needs a separate recorder in both: BuddyStat fetches its recorder only for sessions sampled for replay, and Umami's replays and heatmaps use a recorder script you add to your pages.

Both are cookieless, don't collect personal data by default, and say you can run them without a cookie banner. Umami rotates its session salt monthly by default. BuddyStat has an opt-in daily salt for user IDs, which stops a visitor from being linked across days. BuddyStat Cloud stores analytics data in the EU; Umami says its cloud servers are in the US and EU.

Switch to analytics that's made for you

Powerful insights without the complexity. Privacy-focused analytics that just works.

7-day free trial. Cancel anytime.