fivebar vs Umami

Umami has more reports, and costs less up to a few million pageviews. fivebar shows the bots and errors it left out, lets an app act for you, and keeps less about each visitor.

Umami does a great deal: funnels, journeys, revenue, Core Web Vitals, an MCP server, and on its Business plan, heatmaps and session replays. It’s free to run yourself, and free on its own cloud up to 100,000 events a month for one site.

The bots it left out

Umami checks each hit’s user agent against a list of bots and drops what matches, with nothing kept to say it did. fivebar counts everything it leaves out on a Bots page: how many pageviews, which pages, which networks, and why each was taken for a bot, whether it named itself or came from a server. When a visit of your own goes missing, that’s where to look.

Pages that fail

Umami has no report of pages that fail: a 404 is counted as a page like any other, unless you send it as an event of your own. Chrome, Edge and Firefox tell fivebar’s script the status of every page they load, so the Errors page fills itself: which addresses fail, how often, and where their visitors came from. Safari needs one attribute on your error pages’ template. Error pages are never billed.

An app that can act

Both have an MCP server. Umami’s reads, and changes nothing. An app reaches it with an API key in a header, from the Pro plan up.

fivebar’s is added by its address alone, on every plan: the app opens fivebar for you to sign in and choose Allow, and there’s no key to copy. Tick a box as you do, and the app adds goals, site search and excluded traffic, or turns your email reports on, when you ask it to.

Less about each visitor

Umami can record sessions to replay, link a signed-in person’s visits across their devices with distinct IDs, and show each visitor’s activity in a profile. fivebar keeps counts, by site and day: so many pageviews of a page, from a country, in a browser, and never a record of what one visitor did.

Its visitors differ too. Umami counts a visitor once in a calendar month, by a salt that changes each month. fivebar counts a visitor once a day, so its visitors over a month are visitor-days, and come out higher wherever people come back.

Where your stats are kept

Umami Software is a company registered in Delaware, and its cloud keeps an account’s stats in the US or the EU, chosen as it signs up. Most of the companies it uses, Amazon Web Services and Cloudflare among them, are American. Nothing fivebar keeps is at rest outside the EU, or on a US company’s server, and your stats are on its servers in Germany, at Hetzner (Infrastructure). Umami keeps a site’s stats for 6 months on Hobby, 2 years on Pro and 5 on Business; fivebar keeps them until you delete the site.

Prices

Umami is cheaper up to a few million pageviews, and fivebar from 5M up. Umami’s limits are in events, and each property an event stores counts as one more, as does session data. Pro holds 20 sites and Business any number; fivebar holds 1,024.

A month, in US dollars, from fivebar’s prices and Umami’s, which charges $30 a million past Pro’s first and $20 a million past Business’s first ten.

What Umami has that fivebar doesn’t

• Reports: funnels, journeys, retention, attribution, revenue, and segments and cohorts to cut them by.
• Heatmaps and session replays, on Business in its cloud, and when you run it yourself.
• Self-hosting: Umami is open source, under the MIT licence, to run on your own server.
• Boards, dashboards of your own making.
• A free plan, for one site up to 100,000 events a month.

Switching

Add fivebar’s tag beside Umami’s, and run both for a few weeks, so you have both counts for the same days before you take Umami’s out. A button with data-umami-event="Signup" takes data-tally="Signup", and its data-umami-event- attributes become data-tally- ones. Where your pages call umami.track() with an event’s name, call tally() with the same name and data.

Checked on 19 October 2026, on Umami’s own pages and code, each linked where it’s used.