Vitrus analytics

Open-source analytics for every app you ship. One panel you can check.

Cookie-free web and product analytics for websites, iOS and Android apps — traffic, users, retention and

revenue side by side, without storing who your users are. Every number carries the SQL that produced it,

and your AI agent can ask about all of them over MCP. One process, on your own server.

Live demo · Use with ChatGPT / Claude · Website · Cloud · Documentation · Quickstart · Compare · Changelog · Discussions

Quickstart

You need Bun 1.3 or newer. That is the whole list.

bun install -g @vitrus-dev/cli

vitrus init # creates ./vitrus.db and a secret salt vitrus site add "My site" example.com # prints your script tag VITRUS_PASSWORD="a long secret" vitrus start # ingest + dashboard on http://localhost:3000

From source instead: git clone https://github.com/Vitrus-Dev/vitrus && cd vitrus && bun install && bun run build:tracker, then run bun packages/cli/src/cli.ts wherever this says vitrus.

Then one line in your site's :

<script defer data-site="SITE_ID" src="https://YOUR-HOST/v.js"></script>

Mobile apps: Vitrus for Swift (iOS, iPadOS, macOS — Swift Package Manager) and Vitrus for Flutter & Dart. Same panel, user ids hashed on the device, no device identifier.

No Docker Compose file, no database server, no migration step. Rather not run it? [app.vitrus.dev](https://app.vitrus.dev) is the same engine, hosted, with a free plan — and [the live demo](https://vitrus.dev/demo) opens the full hosted dashboard on sample data, no account needed.

Every number opens the query that made it

Click a figure and you get the SQL that ran, its parameters, the window and the result — not a description of the number, the number's origin. It is the same evidence the AI summary is checked against.

That matters more now that models write the reports. When an AI-written sentence contains a number that is not in the evidence, Vitrus drops the sentence before it reaches you:

Visitors are down 18% against the previous period. [e1]

The drop coincides with the last deploy. [e1, e7] ✗ dropped: "The new theme caused a 41.7% fall in conversion." → 41.7 is in no evidence record, and "caused" is a claim nobody can make from this data.

Every app you ship, one panel

Shipping several apps — web and mobile — usually means one admin page per app just to see who signed up. Add one line where your app knows the user is signed in, and Vitrus counts who is new, who came back, who you lost and who started paying, per app and for all of them side by side:

vitrus.identify(user.id)           // required: hashed in the browser, never sent raw

vitrus("signup") // optional vitrus("plan", { plan: "pro" }) // optional: your own plan labels

• Every user, under a made-up name. Open an app and each signed-in user is a row — returning, one-time or signed up only, actions, active days, visits, joined, last active; opened, actions by day and recent visits — shown as "Amber Falcon · 3f9a2c", because no email or name is stored to show.
• Lifecycle per app. New, active, came back, lost, net, quick ratio, one-and-done, current plans, became and stopped paying — each with its query.
• Ask your AI. "Which of my apps lost the most users this week?" — get_portfolio and get_lifecycle over MCP answer with counts and the queries behind them.
• Hashed before it leaves the browser. The script sends sha256(site + "|" + id); the server hashes that again with a secret before storing it. Your users' ids — often emails — never reach the server. No WebCrypto, no id sent.
• Separate per app, by design. The same person in two of your apps is two unrelated hashes; nobody can join them. Portfolio totals say so instead of pretending to deduplicate.
• Personal fields dropped twice. Email, phone, name, address, password, token and similar properties — and any value shaped like an email or phone number — are removed in the browser and again on the server, and the removal is counted.
• No auth provider to connect. Works the same with Supabase, Clerk, Firebase, Better Auth or your own login.

Self-hosted: GET /api/people?site=…, GET /api/lifecycle?site=… and GET /api/portfolio on your server; over MCP, get_lifecycle and get_portfolio. How it is counted →

A whole analytics product

Globe. Sessions at their city, on a canvas drawn from our own geometry — no map provider, no GeoIP database.

Real-time. Who is on the site now, and the latest events, streamed as they arrive.

AI traffic. Visitors ChatGPT and Claude sent you, kept apart from the crawlers that read your pages.

Funnels. Ordered — a step counts only after the one before it, so the conversion is not inflated.

Journeys. The paths people take, as a Sankey you can filter by start and end.

Revenue. Per currency, never converted, attributed to where the visit began.

Web Vitals. LCP, INP, CLS, FCP and TTFB at the percentile you choose, per page.

Retention. Cohorts of identified users — and an honest blank for days that have not happened yet.

Heatmaps. Clicks and scroll depth per device class, drawn over the page from your own recordings — nothing extra collected.

Users. Every signed-in user under a made-up name — returning, one-time, signed up only — with actions by day.

Screenshots: the hosted dashboard on a demo workspace; every figure is sample data — open it yourself . The self-hosted dashboard in this repository is simpler today — see Architecture for exactly which views it renders.

Ask your AI about your analytics

Vitrus speaks MCP. Your assistant reads your analytics — read-only — and every number it gets back comes with the query that produced it, so it can cite instead of assert. Listed in the official MCP Registry as dev.vitrus/analytics.

The plugin's skills, under plugins/vitrus/skills:

• `/vitrus:weekly-report` — last week against the week before, channels, AI assistants, goals; every figure cited.
• `/vitrus:traffic-drop` — finds the day a number broke and the segment it lives in, then checks errors and Web Vitals.
• `/vitrus:measurement-plan` — reads your code and proposes the events, goals, funnels and revenue calls to add.
• `/vitrus:ai-search-audit` — which assistants send people, which pages the AI crawlers read, and where the two disagree.

17 tools, all read-only: query_stats (any metric by any of 20 dimensions or by day, with filters), get_portfolio (all your apps side by side), get_lifecycle, get_realtime, get_ai_traffic, get_revenue, goal_report, analyze_funnel, get_journeys, get_retention, get_web_vitals, get_errors, get_digest and more — docs. Connections are scoped to one workspace and can be disconnected any time under Account → Connected apps.

What it is, in one paragraph

Vitrus tells you how many people visit your website, where they come from, what they do and wh