Lumenlytic vs Umami

Umami is the closest like-for-like comparison in the privacy-first category, because it uses the same meter as Lumenlytic: events, not pageviews. That makes the price comparison unusually honest — both tools count pageviews and custom events in the same bucket, so you can compare like with like instead of translating between units and guessing how many pageviews a custom event is worth. If you have ever tried to compare an event-billed tool with a pageview-billed one, you will appreciate how much noise this removes. The two products are genuinely competing for the same buyer, which is why the details below matter more than they would in a lopsided comparison. When two tools measure the same thing the same way, the decision comes down to price, control and the handful of features that differ.

Umami is open source and can be self-hosted for free, which appeals strongly to teams who want full control or who already run their own infrastructure. Its managed plans are simple: Hobby is $0 for 100k events, one site and six months of retention; Pro is $20 for 1M events, 20 sites and two years; Business is $200 for 10M events, unlimited sites and five years. Overage on paid plans is billed per event, so a viral post can add a line to your bill rather than pausing collection. Self-hosting is the real differentiator: if you have a server and the appetite to run it, the software itself costs nothing and your data never leaves your infrastructure. For a team with existing DevOps capacity, that combination of zero licence cost and full control is genuinely compelling.

Lumenlytic is managed only, but it is cheaper at the entry and mid range: the free plan covers 200k events with one site, and Solo is $15/mo for 1.5M events and five sites. It also captures Core Web Vitals out of the box and has no per-event overage on paid plans, using a fair-use model instead. The trade is that Lumenlytic offers 20 sites on Studio at $39 rather than 20 sites on a $20 plan, and it does not offer self-hosting at all. So if your priority is the lowest possible bill for a single site, Lumenlytic wins; if your priority is twenty sites for twenty dollars, Umami's packaging is stronger. Read the free tier carefully too, because the difference between 100k and 200k events is meaningful for a site with steady traffic.

The decision usually comes down to control versus convenience. If self-hosting or open-source licensing is a requirement, Umami is the clear choice and a genuinely excellent one. If you want a managed product that is cheaper at the low-mid end, captures web vitals and never surprises you with an overage line, Lumenlytic is the better fit. Both are strong products; the difference is packaging and control, not capability at the basics. You can also run them side by side for a week, since both install with one script tag, and compare the numbers against your own traffic before committing to either. That parallel test is cheap and removes most of the guesswork from the decision.

Total cost of ownership is where the two products diverge most. Umami's self-hosted option is free software but costs a server, database, upgrades and the attention of whoever runs it; its managed paid plans add per-event overage above the allowance. Lumenlytic is managed only, but the price is flat, there is no overage, and there is nothing to operate. For a team with spare engineering capacity, self-hosting can be effectively free at the margin. For a team without it, the same option is a liability. Be honest about which team you are: the cheapest option on paper can be the most expensive if it quietly consumes an afternoon every month.

If you are deciding today, pick Umami when open source or self-hosting is a hard requirement, or when you need five-year retention on a large plan. Pick Lumenlytic when you want a managed service, a larger free tier and no overage surprises. Both bill events, so the price comparison is unusually fair, and both install with a single tag. Running them side by side for a week is a cheap way to confirm the numbers and the workflow before you commit. The decision is mostly about control and price, and a short trial will make the trade-offs concrete.

Support and reliability differ in kind here. Umami's self-hosted path puts reliability squarely on your team, which is fine if you already run services and have on-call habits, and risky if analytics is an afterthought. Its managed service is a smaller operation than the larger vendors, so the track record is shorter. Lumenlytic is managed only, which removes operational risk but also removes your ability to fix things yourself. Neither model is better in the abstract; the right one depends on whether you would rather own the uptime or pay someone to. Ask about export, backups and what happens during an outage before you commit.

Set a trigger to revisit. If traffic grows past the free tier, if overage starts to matter, or if you decide self-hosting was more maintenance than it was worth, re-run the comparison rather than tolerating a poor fit. Because both are event-billed and install with one tag, moving is comparatively clean and your price expectations carry over. The risk is choosing an operational model that matches your ideals rather than your actual habits. Be honest about whether you will really maintain a server, and let that answer decide more than the sticker price does.