Analytics that needs no cookie banner
Visits and traffic are counted by the server that delivers your site — no script and no cookie ever appear on your pages. You also see the visitors that ad blockers hide from ordinary counters. On for every site, on every plan.
Works on every plan, including Free.
What you see
Views and visitors
By day — for a day, a week, a month or your own range. Two numbers side by side: “likely human” and all requests. Bots don't hide inside the total and don't pass for an audience.
Traffic
Bytes actually served, per site and per account — the same number your plan limit is measured by. No estimates: the edge server counts at the moment it responds.
Top pages and referrers
Which pages people open and where they come from: the referrer's domain and path, with direct visits listed separately.
404 report
Broken URLs that someone actually opens. On a static site such links otherwise go unnoticed for years, and no JavaScript counter sees them: it isn't on the error page.
File downloads
How many times your price list, handbook or photo archive was downloaded. A photographer sees that the client got the photos, an expert sees how many people took the checklist.
Submissions and conversion
Form submissions sit on the same chart, and conversion is counted from human visitors — not from bots, which never submit forms.
Devices
Phones, desktops, tablets — from the user-agent string, without any identifier.
Deploys on the chart
Every deploy is marked on the time axis, so you see what changed after a new version went live.
Two numbers instead of one pretty one
JavaScript counters undercount: ad blockers cut the script, and a visitor from an ad who leaves after five seconds never makes it into the stats. Server-side counting sees everyone — bots included. So we show both numbers: “likely human”, the audience after filtering, and “all requests”, which traffic is counted from, because bots consume real bytes. Nothing is filtered out silently: the reasons are listed separately.
Visitor privacy by design
Where to look
Project page
A bar with this month's traffic against the plan limit, and the sites that use the most — you see an overrun before the email, not after.
Site page
A “last 7 days” line right in the header: views, visitors, traffic and a mini chart — the numbers show up right after publishing.
Analytics tab
Everything else: the chart with deploy markers, top lists, referrers, 404s, downloads, devices, form conversion and CSV export.
For AI agents: the get_site_stats tool on the
MCP server and
GET /api/v1/sites/{id}/stats in the
REST API.
Your agent can tell you how many people visited the site and where they came from.
Analytics — frequently asked questions
Why are the numbers higher than in Yandex Metrica or Google Analytics? +
Those are scripts on the page: ad blockers cut them, and a visitor who leaves within a couple of seconds never sends a hit. The edge server sees every request, so server-side numbers are usually higher, especially for ad traffic. We don't hide this: “all requests” is always shown next to “likely human”.
Do I need a cookie banner because of your analytics? +
No. We set no cookies and add no code to your pages, so our statistics give you no reason to show a banner. If you add a third-party counter yourself, the obligation comes from that counter, not from us.
How do you filter out bots? +
By behavioral signals on the edge server: self-declared crawlers, empty user agents, scanners probing nonexistent paths like /wp-admin. Filtered traffic is not thrown away — it is shown as a separate row, so you can always check how much was cut. Nobody gets this 100% right, which is why there are two numbers, not one.
How accurate are “unique visitors”? +
It is an honest estimate, not an exact count. Uniques are counted with a probabilistic data structure that stores no addresses, and linking a person across days is impossible by design. For a single day the figure is accurate to within a couple of percent; for a month it is the sum of the days.
What happens if I exceed the traffic limit? +
Nothing drastic: at 80% and 100% of the monthly limit you get a warning by email and in the panel. Sites keep working, and we don't switch anything off. Plan limits have plenty of headroom.
What can't server-side analytics do? +
Anything visible only from the browser: time on page, scrolling, clicks, screen resolution, “returning” visitors. We would rather not promise these metrics than quietly set identifiers. Precise behavioral data belongs to scripts, with all the obligations they bring.
Is this processing lawful? +
Yes. While handling a request, the edge server sees the IP address — unavoidable for any server — and processes it on behalf of the site owner. This instruction is set out in the Terms of Service, and the data involved is listed in the Privacy Policy. Only anonymized daily totals are stored.
How much does it cost, and how do I turn it on? +
Nothing, and you don't have to: analytics is on for every site on every plan, including Free. Open the site's Analytics tab — the data is already there. CSV export is one button; AI agents use the get_site_stats tool and REST.
The numbers are already counting
Publish a site and statistics start collecting on their own: no setup, no code, no banner. On every plan.