What it looks like
The dashboard, on real traffic
The same engine, seen from the front. These are live views from a Measr dashboard: KPI cards, trend charts, and per-dimension breakdowns, all read back from the customer's own database.
Measr is our own product: a self-hosted, privacy-first analytics toolkit, and we run it on this very site. A tracking SDK captures behavior in the browser, writes it to a database the customer owns, and a dashboard reads the KPIs back. This is the system, end to end.
Published June 2026 by Balázs Turán, Creative Data Engineers.
Teams want to know what happens on their site without handing visitor behavior to a third party. So we built one and run it ourselves: an analytics toolkit where the data sits in the customer's own database, with no cookie and nothing personal collected.
The rule we set ourselves: the visitor's browser only sends, the database only stores and guards, and a person reads the result after signing in. That split is what makes it private by design. The SDK can never read data back out, and the dashboard only ever sees the sites its owner is allowed to see.
Three stages run in order: capture behavior in the visitor's browser, store it in the customer's own Supabase, then see it in a signed-in dashboard. No cookies, and the data never leaves the customer's project.
Hover or focus any box for a plain-language explanation.
Measr is a product you can run yourself, on your own database. See the product page →
The same engine, seen from the front. These are live views from a Measr dashboard: KPI cards, trend charts, and per-dimension breakdowns, all read back from the customer's own database.
An anonymous, write-only key plus row-level security makes a client-side SDK safe. The SDK can write events and nothing else. RLS blocks reads at the database, so even with the key in the page, no one can pull data back out.
Aggregate on the server so the dashboard stays fast. The KPIs are computed by functions inside the database, not in the browser. The dashboard asks for totals and breakdowns, not raw rows, so it stays quick even as the event log grows.
Self-hosted means the customer owns the data. Events land in the customer's own Supabase project. We never hold a copy, and the customer can read, export or delete it whenever they want.
Yes. The data lives in the customer's own Supabase project, never ours. You own the database, the tables and every row in them.
No. Measr sets no cookie and uses no third-party tracker. The session is kept in the browser's local storage for 30 minutes, and nothing identifies a visitor personally.
No. The SDK posts events with an anonymous key that can only write. Reads are blocked at the database, so the SDK can never pull data back out. The dashboard can only read once a person is signed in.
Yes. We can wire Measr into your site and your own Supabase, and walk your team through the dashboard. Measr is EUR 19 per month or EUR 190 per year. Book a call and we will scope it.
Measr gives you the numbers that matter without handing visitor behavior to a third party. No cookies, no tracker, and the data stays in your project. It is EUR 19 per month or EUR 190 per year.
We also teach operators to build systems like this, hands-on. Balázs runs the build sessions at Agent-J+.