Feasible vs Umami

Start with the two things Umami does better, because they’re not small.

Umami is MIT-licensed. The whole repository, since 2020. Feasible is AGPL-3.0-or-later. MIT is more permissive than AGPL - you can modify Umami, run it as a service for other people and keep your changes to yourself, and our license says you can’t. If license permissiveness is what you’re optimizing for, this comparison is already over and Umami won it.

Umami has a free tier. Hobby is $0, one website, 100,000 events a month, six months of retention. We have no free plan - a 30-day trial with no card, and then $9.99. For a personal blog, free beats $99 and we’re not going to pretend otherwise.

Now the rest.

The price

From Umami’s pricing page, read September 3, 2026.

Umami has no annual billing. Their FAQ: “Billing occurs on a monthly basis and you can cancel at any time.” So Pro is $240 a year against our $99, and Business is $2,400.

Umami is the closest thing to us on price in this whole comparison - 2.4 times, not 14 or 20. That’s worth saying plainly instead of burying it.

What counts as an event

Here’s the difference that moves money, and it’s in Umami’s own words:

“Usage is measured by counting pageviews to a website plus any custom events or custom event properties stored. Each website pageview counts as one event. If you save event properties, each data property stored counts as one event.”

Read that last sentence again, because it’s the thing nobody checks before they sign up.

Say you fire a purchase event with five properties on it - plan, currency, amount, coupon, referrer. That’s six events against your limit. One for the event, five for the properties.

Work it through on a real shop. 700,000 pageviews a month. 20,000 purchases, each carrying those five properties. 30,000 signups carrying two.

Add a sixth property to your purchase event and Umami’s number is 930,000. Ours doesn’t move. Add a seventh and ours still doesn’t move, on identical traffic.

We count pageviews and custom events - the same two rows they do. The third row is the whole difference. Properties are free here, however many you attach, and so are the engagement pings behind scroll depth and time on page. Describing your business properly in your analytics shouldn’t cost more, and here it doesn’t.

Side by side

Self-hosting

Umami self-hosts on Node.js 18.18 or newer plus PostgreSQL 12.14 or newer. Two containers. Of everyone in this comparison, Umami is the one whose self-hosting story we respect most - it’s light, it’s documented, and it works.

Feasible is one Go binary and one SQLite file. No Node, no Postgres, no container required. 1 core, 512 MB of RAM. One process instead of two isn’t a revolution, and we’re not going to dress it up as one.

The difference that does matter is what’s in the build. From Umami’s own FAQ:

“Cloud also includes additional features like email reports and the streaming API that are not available in the self-hosted version.”

Feasible’s self-hosted build is the build we host. Every feature, every release, no license key, no cut-down edition, and no directory in the repo you’re not allowed to compile. Set FEASIBLE_APP_HOSTED=false and everything works - funnels, custom properties, the API, webhooks, MCP, raw export, teams. See open source web analytics for what that does and doesn’t promise.

Knowing when data goes missing

Every analytics tool drops traffic - bots, scrapers, datacenter addresses, browsers too old to trust, requests from hostnames that aren’t yours. Correct behavior. The question is whether you find out.

Feasible has a health screen per site: the last 24 hours of accepted and dropped events, each drop labeled with a reason - bot, datacenter_ip, referrer_spam, outdated_browser, automation, hostname_not_allowed, shield_ip, rate_limited and more.

It reports which client address it resolved for your last request and from which header, and warns you when your reverse proxy isn’t forwarding visitor addresses

• the failure that collapses every visitor into one and puts your whole audience in your datacenter’s city. There’s a button that sends a real test event through the public URL, so it exercises the proxy and the headers as a browser would.

We think that’s the most useful thing in the product, and it’s the one place where “we never fail silently” is a feature you can point at rather than a slogan.

The script

Measured September 3, 2026 with gzip -9: Umami 2,307 bytes, Feasible 3,377. Theirs is smaller. Both are small enough that it isn’t the reason to choose either one - the number that matters in this category is Google’s 148,451.

Where Umami wins

The MIT license, plainly. A free tier we don’t have. Session replay and heatmaps on their Business plan, neither of which we offer at any price. A smaller script. A much bigger GitHub community and more years in the wild.

Where Feasible wins

You want annual billing and $99 instead of $240. You want more than two years of history. You have more than ten people or more than twenty sites. You attach properties to your events and would rather that didn’t inflate your bill. Or you want the self-hosted build to be identical to the hosted one, with nothing held back.

More: the whole price ladder, or what’s in Feasible including what isn’t.