Why I Built Metrone

I didn't set out to build an analytics company. I was building Sentrix — an AI-powered digital presence management platform — and I needed analytics. Simple analytics. How many people visit the sites we manage? Which pages perform? Are the AI features we're integrating actually being used?

So I went looking for a tool. The requirements were straightforward:

• Privacy-first. No cookies, no IP storage. Our clients are in healthcare, finance, and regulated industries. We can't explain away a tracking cookie.
• AI-aware. We're building voice agents and chatbots into client sites. We need to measure call duration, intent resolution, and provider performance — not just page views.
• First-party. The script needs to load from the client's own domain. Ad blockers are real, and our clients deserve accurate data.
• Fast. Edge processing. No 24-hour delays. No sampling.

What I found

Google Analytics? Privacy nightmare. Also, Google uses your data to sell ads. That's not a conspiracy theory — it's their business model.

Plausible and Fathom? Great privacy story. Genuinely good products. But no AI tracking. No voice agent analytics. No chatbot metrics. I'd need to bolt on a second tool, write custom integrations, and maintain two dashboards. For every client.

Mixpanel, Amplitude, PostHog? Powerful, but designed for product analytics with user identification. They're trying to know who each user is. That's the opposite of what we need. Also, most of them are heavy — 50KB+ scripts, cookies, and consent flows.

Nothing hit all four requirements. Every tool made me choose: privacy or features. Simplicity or AI awareness. First-party loading or easy setup.

So I built it

Metrone started as an internal tool at Sentrix. A lightweight ingestion pipeline that processes events at the edge, resolves geo data from the network (not from IP lookups), and stores everything without a single cookie or raw IP address.

Then I added the AI event schema. A unified data model where a voice call from Twilio sits next to a page view from a marketing site, and a chatbot session from an AI assistant lives in the same table as a conversion event. Same pipeline, same dashboard, same privacy guarantees.

The more I built, the more I realized this wasn't just a Sentrix problem. Every team shipping AI features faces the same gap. Every privacy-conscious company struggles with the same tradeoffs.

The principle

Metrone is built on one belief: you should be able to understand how your product is used without knowing who is using it.

That's not a marketing tagline. It's a technical constraint we designed around. Every decision — from the data model to the session handling to the pricing — follows from it.

We don't have a free tier because free analytics platforms monetize user data. We charge a fair price and keep your data yours. We don't fingerprint browsers because we don't need to. We don't store IP addresses because once you hash them with a rotating salt, you can't reconstruct them — and that's the point.

What's next

Metrone is now in public beta. It's the tool I wished existed when I started building Sentrix. If you're shipping a product with AI features and you care about privacy, I built this for you.

— Pahridin Q.
Founder, Metrone · Building Sentrix