GeckoStats vs Umami
Umami is the most generous product in this comparison: MIT licensed, self-hostable for nothing, and free in the cloud up to 100,000 events. The case for paying us is narrow and specific.
Seven days free, no card. Checked against their own pages in November 2026.
Which one should you actually use?
Umami and GeckoStats are both cookieless, both need no consent banner, and both have funnels and revenue in the product rather than as an add-on.
Umami is MIT licensed and free to self-host, free in the cloud to 100,000 events, and cheaper per event above that than we are.
GeckoStats takes the payment from the provider's own webhook rather than from an event you send, opens it into the visitor who made it, and gives your AI agent 26 tools to ask with.
| GeckoStats | Umami | |
|---|---|---|
| Revenue | ||
| Revenue attribution | From the provider’s webhook The payment arrives from your payment provider carrying the visitor id, so the amount is theirs rather than your front end’s, a refund takes the sale back off the chart, and every source, campaign, page and query is ranked by the money instead of the traffic. | Revenue tracking Listed on Pro and above, from events you send. It is not taken from a payment provider’s webhook and not joined back to the visit. |
| Every visitor’s journey | Open any payment A session-by-session trail for one anonymous visitor, from an identity that rotates daily: the source that first brought them, every page and click, the days between visits, and the payment at the end. | Sessions Session detail is visible; a profile opened from a payment is not on the pricing page. |
| Funnels and goals | On every plan Button clicks and signups as goals, then step-by-step drop-off between them, with the revenue that came out of the last step. | Yes Funnel analysis on Pro and above. |
| Subscriptions and MRR | Yes MRR, churn and lifetime value broken down by source: which channel brings customers who stay, rather than which brings the most first payments. | Not listed Not on their pricing or documentation pages when we checked. |
| Visitors | ||
| Campaigns, with revenue | Yes A tagged link per tweet, article or newsletter issue. It appears by name with the visitors and the money it brought, including people who came back and bought a fortnight later. | Yes UTM campaigns with visitors against them. |
| Live view | A globe, and a feed Everyone on the site right now on a rotating globe, with pages, goals and payments landing in a feed beside it. | Realtime A live view of current visitors. |
| Returning visitors | Yes New against returning for the period, week-by-week retention, and what the people who came back were worth. | Yes Retention reporting on Pro and above. |
| Content and search | ||
| Search Console, with revenue | Built in Connect it once and every query, page and country you rank for arrives with the money its page earned beside it, so the list is ordered by what it is worth rather than by clicks. | Not listed Not on their pricing or documentation pages when we checked. |
| AI crawlers and AI referrals | Both halves Which assistants read your pages, named, and what each one sent back: the visitors arriving from ChatGPT, Claude, Perplexity and Gemini, with their revenue and conversion rate against everyone else’s. | Not listed Not on their pricing or documentation pages when we checked. |
| Core Web Vitals | From real visits LCP and INP measured on your actual visitors, shown beside the revenue of the page, so a slow page that earns is the one you fix first. | Not listed Not on their pricing or documentation pages when we checked. |
| For developers | ||
| Release markers | Yes One curl at the end of your deploy puts a marker on the chart, so a drop can be read against what you shipped rather than guessed at. | Not listed Not on their pricing or documentation pages when we checked. |
| MCP server for AI agents | 26 tools Your agent calls the same queries the dashboard runs, with a key issued per website and revocable. Twenty-four of the twenty-six only read; the two that write create a funnel and re-run attribution. | No No MCP server; API access on Pro and above. |
| REST API and server events | On every plan Read every figure the dashboard shows, and post payments, goals, deploys and crawler hits from your own backend with the same key. | Pro and above API access from the Pro tier. |
| Alerts | Yes Tracking stopped, revenue down, organic clicks down, a page deindexed, a query dropped five places. Emailed when it happens rather than found a week later. | Not listed Not on their pricing or documentation pages when we checked. |
| Privacy | ||
| Cookies and consent banner | None by default A visitor is a salted hash that rotates daily and the IP is never stored, so there is nothing on the device to consent to anywhere in the EU. Global Privacy Control and Do Not Track are honoured in the script and again in the collector. | None No cookies and no consent banner needed, the same position as ours. |
| Open source | No A hosted product. The tracker is the only part that runs on your side, and there is no self-hosted edition. | MIT The most permissive licence in this comparison: self-host, fork and modify with essentially no obligations. |
| Where it runs | Cloudflare A United States company, on its global network. Data at rest is encrypted; no IP addresses are stored at all. | Yours, or their cloud Self-hosted wherever you put it, or Umami Cloud. |
| Data retention | As long as the site exists No ceiling and no tier. Deleting a website deletes its events, visitors and payments in the same minute, and deleting the account does that for every website it owns. | Not listed Not on their pricing or documentation pages when we checked. |
| Price | ||
| Entry price, and the meter | From $9 a month Counted in events, which is pageviews plus anything you tag yourself: 25,000 for $9, 100,000 for $19 on Starter. Seven days free, no card, every feature on. | Free, then $20 a month Counted in events, like ours. Hobby is free to 100,000 a month, Pro is $20 for a million, Business $200 for ten million. Cheaper per event than us above 100,000. |
| Websites and seats | 1 on Starter, 30 on Growth Seats match the websites: just you on Starter, up to thirty on Growth. | Not tiered by site The limit is events rather than websites. |
| Free tier | Seven-day trial No card, and every feature is on during it. | Free forever Self-hosted free, and Umami Cloud Hobby free to 100,000 events a month. |
Where something is marked “not listed”, it means we could not find it on their pages, not that it does not exist. Umami’s figures were read off their own pricing and documentation pages in November 2026. Found something out of date? Tell us and we will correct it.
The screens you would be moving to
Not a description of them. The same tiles the front page shows, and the same live demo behind them.
Every customer’s full journey
Who paid, where they came from, how long it took. Open anyone and read every page and click from first visit to payment.
Chrome- 7:31 PM/pricing
- 7:33 PMcheckout_click on /pricing
- 7:35 PMPaid $49
- 9:02 AM/blog/ship-faster
X / Twittercampaign: launch-tweet2m 40s- 2:14 PM/
- 2:15 PM/pricing
Traffic and revenue in one view
Blue shows visitors and orange shows revenue. See how they move together, then drill into the channels and sources behind each spike.
Point your AI agent at it
An MCP server with 26 tools over your own numbers, so you ask in plain English instead of reading a dashboard. Twenty-four of them only read, the key is issued per website, and you can revoke it whenever you like.
Claude Code~/sites/nimbusWhat actually differs
01Revenue attribution
Umami lists revenue tracking on Pro and above, from events you send. Ours comes from the payment provider's own webhook, so the amount is the provider's, a refund reverses the sale, and the payment opens into the visitor who made it.
02Every visitor's journey
A session-by-session trail for one anonymous visitor, from an identity that rotates daily: first source, pages, clicks and the day they paid. Umami shows sessions; a per-payment profile is not on its pricing page.
03Owning it, which theirs lets you do
Umami is MIT and self-hostable for free, which is the most permissive position on this page. We have no self-hosted product at all. If running the database yourself is the requirement, that decides it and nothing below changes it.
04Price, and the meter
Both count events. Umami Cloud is free to 100,000 a month and $20 for a million; we are $19 at 100,000 and $69 at a million. Theirs is the cheaper shelf for raw volume.
Moving across from Umami
If you are self-hosting Umami, keep it. Add our tag for a fortnight, connect your payment provider, and see whether the money column changes a decision you would otherwise have made on traffic. If it does not, you have an answer and you have lost nothing.
What it costs
Priced by events a month, with everything on both plans except the number of sites and seats.
Starter
For one site and one person.
Billed monthly · up to 100K events
7 days free trial
- Realtime dashboard
- Live Globe
- User Profiles
- Funnels
- Revenue tracking
- Core Web Vitals
- and 9 more, on every plan
Growth
RecommendedFor several sites and the people who work on them.
Billed monthly · up to 100K events
7 days free trial
- Realtime dashboard
- Live Globe
- User Profiles
- Funnels
- Revenue tracking
- Core Web Vitals
- and 9 more, on every plan
Every plan starts with 7 days free. No commitment, cancel anytime. Prices exclude VAT, which may apply at checkout.
GeckoStats and Umami: the questions people ask
Umami is free and open source. Why pay for this?
For one reason: we join the payment provider’s webhook to the visit, so a sale carries the source, the campaign, the page and the search query that produced it, and the payment opens into the person who made it. If that is not a question you need answered, Umami is the better deal and it is not close.
Is GeckoStats open source?
No. It is a hosted product, and the only part that runs on your side is the tracker script. If self-hosting is a requirement, Umami is the right answer on this page.
Umami has revenue tracking on Pro. Is it the same?
It is revenue you send as an event. Ours comes from the provider over a webhook, so the amount is the provider’s, a refund takes the sale back off the chart, and the payment is joined to a visitor rather than to a number.
Can I run both?
Yes. Neither sets a cookie, and two tags are a couple of kilobytes.
Comparisons with the other five
vs Plausible
Both are cookieless, both fit in a page of numbers rather than a reporting suite.
vs Fathom
Fathom charges one price for everything it has and keeps your data forever.
vs Google Analytics
GA4 is free, and that is a real argument.
vs DataFast
This is the closest comparison on the site.
vs Simple Analytics
Simple Analytics is the most privacy-forward product in this comparison and it has a free plan that is not a trial.
See which traffic pays, this week.
Add the script, connect your payment provider, and the next sale arrives knowing where it came from.
7 days free · no commitment · cancel anytime
