analyticshq

Privacy-first web analytics is almost ready. Leave your email and we will send the install snippet the moment it opens.

analyticshq vs Plausible

Two privacy-first tools. One keeps your data in your database.

Plausible is a respected, cookieless analytics tool, and on the basics the two are close: no cookies, no consent banner, exact counts. The difference is where your data lives and how far the privacy line is drawn.

Plausible vs analyticshq

Point for point.

Cookies and consent Cookieless, no banner, genuinely privacy-first Cookieless, no banner, the same baseline.
Where your data lives Plausible Cloud hosts it on their EU servers Your own PostgreSQL database, wherever you run it.
Geolocation Resolves to city level Country by default. State, province and city only if you switch them on, per site.
Accuracy Exact, no sampling Exact, no sampling, the same.
Visitor identity 24-hour rotating salt 24-hour rotating, per-site hash, the same.
Ecosystem Standalone SaaS, self-hostable Native to the Stacks toolchain: Postgres, queues, deploy.
Licence Open source (AGPL) Open source, and Postgres-native.

Where analyticshq goes further.

Plausible does plenty analyticshq does not: funnels, Search Console, a Looker connector, spike alerts. If those are what you need, it is an excellent choice. Here is where analyticshq leads instead.

01

Your data, in your own database

Plausible is a great cookieless tool, but on Plausible Cloud your analytics live on their servers. analyticshq writes every event to a PostgreSQL table you own and can query directly. No separate store to trust.

02

You decide how precise

Plausible resolves visitor location to city level, for everyone. analyticshq resolves country by default and lets a site owner opt in to state and province, or city, if they need it: a decision you make per site and one that stays off until you make it. Cities with only a handful of visitors are reported together as Other.

03

Part of your stack, not another service

analyticshq runs inside the Stacks toolchain, on the same Postgres, queue, and deploy you already operate. There is no extra analytics service to run alongside your app.

Country
Country by default, region and city opt-in per site. No coordinates, ever.
Your Postgres
Every event lands in a database you own, not a managed store.
24h
Rotating per-site hash by default: no cross-site identity, and no cross-day identity unless a site opts into 30-day visitor timelines.

Your numbers. Your visitors’ privacy. Your database.