Product · SaaS analytics
lapwy
Analytics for SaaS, AI first. Built for your agent as much as for you.
The problem
I built lapwy for myself, because the analytics I used didn't help me make decisions. Google Analytics is convoluted. Even setting it up so it doesn't track people is a job, and the admin panel is all over the place.
Then there's Plausible, which is really good and which I mostly like. But it's too simple for decisions: it shows traffic, you can filter a bit, and that's it. And a lot of that traffic now is bots driving real browsers, so the numbers stop making sense. You see plenty of visitors, then you see they don't convert or do anything. So what's the point of counting them?
What it does
Traffic, kept simple
If you only care about traffic, there's a Plausible-like panel: visitors, sources, pages, devices, countries. Nothing more than you need.
Campaigns side by side
Every way you bring people in — search, AI assistants, tagged ads, emails, newsletters — with what that traffic actually does: signups, payments, revenue. Tick two and compare them.
From conversions backwards
The view I missed most. Start from the people who converted and look back: which countries, which sources, which funnel got them there.
Health, like a product SLO
Not full monitoring, just what matters to visitors: does the page open fast, is it up to Google's standards, does the layout shift. With recommendations, and alerts when something regresses.
Retention without forcing cookies
Cookieless by default, so no cookie banner. When you need real retention, switch a site to a first-party cookie, or to cookie only after consent.
Releases
Tag each deploy and see how it compares with the one before: visitors, conversions, revenue per visitor, errors. So you know when a change made things worse.
Humans, not bots
I don't care how many bots visit my pages. I care about the humans who are at least a bit interested. So every site gets its own rule for an active visitor: opened several pages, stayed for some time, hit a marker you chose. Bots rarely get that far, so switching the reports to active visitors cuts most of the noise.
On top of that, lapwy collects the signals to tell a likely bot from a person and filters them out of every number. It needs more data before it's sharp, and the rule is to avoid false positives: better a bot slips through than a real person goes missing.
Built for your agent
This is the other big reason I built it. lapwy has an MCP server, so the agent I work with knows the numbers too. After a release I can ask "what changed, should we do something?" and it reads the same reports I see in the dashboard. It already runs on my own sites, and it helps me notice things I'd otherwise miss.
Screenshots
Where it runs
Websites through one script tag or the React, Next.js and Vue packages, and native apps through React Native for iOS and Android. It already tracks this site, SpotKat, myStofa and UnslopAI. Access is by request for now.
Count the people. Skip the bots.
Try lapwy