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.
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.
Report
Does it still capture enough detail for meaningful conversion analysis without cookies?
@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?
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.
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?