Launched this week
Statable Analytics
Web analytics built for you and your AI agents
755 followers
Web analytics built for you and your AI agents
755 followers
Statable is web analytics built for humans and AI agents. Use the simple dashboard yourself, or connect Claude, ChatGPT, Cursor, Codex, and other agents through MCP to read reports, analyze traffic, and configure tracking, goals, and funnels. No cookies, no analytics consent banner in most cases, and your data stays hosted in the EU.
Statable Analytics
Hey Product Hunt. Yevhen here.
I have built and grown websites for over 20 years, living inside analytics every day. GA4 kept growing, with more reports and more setup, most of which I never opened. :) At some point I found myself taking a Google Analytics course, and that is when it clicked: I am not the audience for this product. So I started building my own.
Building it myself meant I set the requirements, and from the start those were: collect as little as possible, no fingerprinting, and a product shaped around European regulation. Statable is cookieless, EU-hosted (NL) and needs no consent banner for analytics.
Then AI got good enough to take over my routine work, but agents had no way into analytics. That is what the MCP server fixed. Now the numbers live where I already work: I ask Claude what moved last week and get an answer from my own data, and when I need a funnel for the signup flow I describe it in a sentence instead of clicking through a builder.
Connecting is one OAuth sign-in, and you choose whether an assistant can configure anything or only read.
Free forever on .edu and GitHub or GitLab Pages.
Would you use this? If not, what stops you? I am here all day.
@yevhen_skrypets No cookies and EU hosting sounds useful. Does this work well for larger websites with lots of traffic?
Statable Analytics
@heyrohitk Yes. Every pageview is counted, no sampling, even on the busiest days, which is one of the things that pushed me off GA4. Plans go up to 10M pageviews a month, and above that we set it up with you directly. The script is about 2 KB, so it doesn't weigh on page speed either.
Roughly what volume are you looking at?
@yevhen_skrypets Roughly 1-2M/ month. wanted to see how it performs at that scale.
Statable Analytics
@heyrohitk That's well within range. The easiest way to see it is on your own traffic: the 30-day trial has no cap, so at 1-2M you'd get a full month of real numbers, no card needed. Plenty of people run it next to their current tool for that month and compare.
Macaly
analytics that agents can actualy read is smart 👀 no cookie banner is a nice bonus. who's using it most so far?
Statable Analytics
@petrkovacik Thanks Petr! Early on it's mostly small teams and solo builders moving off GA4, plus a fair share of WordPress sites through the plugin. The MCP side pulls in developers who already live in Claude or Cursor and would rather ask than open a dashboard.
What are you building at Macaly, would it fit there?
Lancepilot
Statable Analytics
@odeth_negapatan1 Thanks Odeth! Subdomains are separate sites by default, so blog.example.com and app.example.com each get their own dashboard. If you'd rather see them as one, use the same snippet on both and add them to the hostname allowlist, then the Hosts report still splits traffic per subdomain.
Are yours separate products or parts of one?
Does it still capture enough detail for meaningful conversion analysis without cookies?
Statable Analytics
@amybradley For conversions that happen within a visit, yes: goals, custom events with properties, funnels, and the source, UTM or referrer the person came from.
Where it's weaker is a journey spread over several days. The visitor ID is a hash that rotates every 24 hours, so someone who reads on Monday and signs up on Thursday counts as two visitors, and the signup gets credited to Thursday's source. That's the trade we made for no cookies and no banner.
How long is the path to a conversion on your site?
How it handles sites with several domains or subdomains. Can one account keep those properties organized separately?
Statable Analytics
@manonbriffaut Both ways, your call. By default each domain or subdomain is its own site with its own dashboard, all under one account.
If you'd rather see them together, put the same snippet on all of them, say example.com, blog.example.com and app.example.com, and list those hostnames in the site's allowlist. Anything else sending that snippet, like staging or a copied site, gets dropped. The Hosts report then splits the combined traffic by hostname, so you can still see each one on its own.
What's the setup on your side, separate products or one product across subdomains?
hi, i saw that u have a free options for .edu sites. i run a 100% free learning website, but its domain is .org not .edu. would the free access still apply? thanks