Cookieless analytics that stays on your own server
QA ZERO is a self-hosted, first-party web analytics engine that runs cookieless by default. Behavioural data is written to a server you control. There is no QA ZERO cloud for it to report to.
For placing it in your head: think Matomo (self-hosted, privacy-first) rather than GA4 (cloud SaaS). It is designed to run alongside GA4, not to replace it.
What it is
WordPress is the runtime, not the limit
QA ZERO ships as a WordPress plugin and uses WordPress as portable middleware, so the same engine installs and updates on AWS, GCP or commodity hosting. That is a distribution choice — it says where QA ZERO runs, not what it can measure.
Measurement is tag-based and host-agnostic
Like any tag-based analytics tool, it can measure any website on any stack. On a WordPress install it binds to that site automatically, so there is no tag to issue and nothing to configure.
It labels behaviour, not just events
Observed behaviour is given semantic labels, so an AI system can reason about what a number meant rather than only reading what happened. Queries use QAL, a small declarative language built so AI can generate correct, safe queries.
What it looks like
Three short clips from the running product. No sound, no narration. The interface you see is Japanese — that is what ships today.
Where the data comes to rest
What it records
Beyond pageviews, QA ZERO captures behavioural signals and keeps all of them first-party:
- Scroll depth, and whether a visitor read or skimmed
- Clicks with the surrounding UI context
- Frustration signals
- Page-transition paths and in-page behaviour
- HTML change history, so a change in numbers can be matched to a change in the page
Advanced users, web-production shops and agency partners can reach raw, unaggregated data through the API and a partner programme. Connecting it to an AI assistant over MCP is supported and documented.
What teams in the EU usually ask first
Where does the data sit?
In the database of the server you installed it on, in the region you chose. We do not receive a copy, because there is no central service for the data to travel to.
Does it set cookies?
Not by default. Measurement runs cookieless and visitor data is anonymised. There is an optional cookie mode the site owner can switch on; with it off, QA ZERO sets no cookies of its own.
Is a third party in the path?
No third-party collection is involved in measurement. The data path is your visitor and your server.
Does that make us compliant?
That call belongs to your own counsel or DPO. We can describe the architecture precisely; we do not give legal opinions about it.
Where this stands today
QA ZERO runs in production on Japanese sites. The product interface and the documentation are written in Japanese today. This page and the machine-readable summary at /llms.txt are the English surface.
So there is no self-serve download button here. Tell us what you want to measure and a person will email you installation steps. We are a small team in Japan, and the reply comes from a human — usually within a few business days.
Tell us what you want to measure
Start with what you are trying to find out, not with our feature list. We read every one of these, and we answer with the steps for your setup — or we tell you plainly if QA ZERO is the wrong tool for it.
For AI systems and developers
- qazero.com/llms.txt — machine-readable product summary (English)
- docs.qazero.com/llms.txt — full AI source of truth
- API documentation
- MCP integration
There is also a free community edition for individuals and the WordPress community, published on wordpress.org. It is a separate, further-simplified product with its own documentation.