Betterlytics is a privacy-first, cookieless web analytics platform, licensed AGPL-3.0 and built with Rust, ClickHouse, and Next.js, aimed at teams that want real-time traffic and product insight without consent banners or third-party data sharing.

What it is

Betterlytics is an open-source, self-hostable web and product analytics platform. The ingestion and query layer runs on Rust and ClickHouse for speed, the dashboard is built with Next.js, React, and TypeScript, and PostgreSQL and Docker appear in the project's own badge set. It sits in the web analytics ecosystem as a drop-in alternative to conventional cookie-based trackers: a script tag of under 2KB replaces the heavier third-party snippet, and the deployment model lets an organisation keep event data on infrastructure it controls rather than in a vendor's account.

The concrete problem it solves is the consent-and-compliance tax that classic analytics imposes. Cookie-based tools force a consent banner, a cookie policy, and a data-processing relationship with a third party, and they typically aggregate and share that data outside the site owner's control. Betterlytics removes the cookie from the measurement path entirely and is described as GDPR, CCPA, and PECR ready out of the box, with data anonymization and an EU hosting option. The result is that analytics keeps working for visitors who decline or never see a banner, and the site owner does not have to negotiate a third-party data-sharing agreement to get page view, traffic source, or conversion numbers.

Key capabilities

• Core analytics: page views, visitors, bounce rate, traffic sources, geographic insights, device analytics, real-time data, and custom events.
• Advanced analytics: session replay, user journeys, funnels, time period comparisons, annotations, and outbound link tracking.
• Performance monitoring via Core Web Vitals — LCP, INP, CLS, and TTFB — plus uptime monitoring and SSL certificate monitoring.
• Public status pages with custom domain support, served from the same platform as the analytics.
• Privacy and compliance controls: cookieless tracking, GDPR/CCPA/PECR readiness, EU hosting, and data anonymization.
• Access and security: role-based access control, two-factor authentication, and OAuth sign-in through Google and GitHub.
• Developer experience: a simple script tag, framework SDKs for React and Next.js, and a self-hosting option.

Who uses it and how

• Privacy-focused product and marketing teams that need funnel and traffic-source reporting but cannot justify a consent banner for measurement alone.
• Engineering teams that need Core Web Vitals, uptime, and SSL certificate monitoring in the same dashboard as their traffic data, rather than running a separate status page product.
• Organisations with EU data-residency requirements that want EU hosting or a fully self-hosted deployment they operate themselves.
• Larger teams or agencies that need role-based access control, two-factor authentication, and Google or GitHub OAuth to give multiple people access without sharing a single login.
• React and Next.js projects that prefer a framework SDK over a hand-written snippet, alongside the plain script tag route.

Getting started

Use the hosted service at betterlytics.io, or self-host it — the README documents a self-hosting option and the project ships Docker and PostgreSQL/ClickHouse components, with installation detail in the documentation at betterlytics.io/docs. A live demo is available at betterlytics.io/demo.

How it compares

The facts provided name no other analytics products, commercial or open source, so no like-for-like comparison can be drawn here. Betterlytics stands alone in this registry on the evidence available.

When to use it — and when not to

A self-hoster must operate the full stack, which the project's own materials indicate includes a Rust service, ClickHouse, PostgreSQL, and Docker — that is real infrastructure to run, back up, and upgrade, so teams without that capacity should take the hosted option or choose a lighter tool. The project carries 55 open issues against 175 stars and 21 forks, and the provided README excerpt is truncated partway through its feature table with no release history given, so anyone evaluating it for production should check current issue activity and release cadence first. Teams that need deep marketing attribution, ad-network integrations, or long-retention raw event export beyond what the listed features cover should confirm fit before committing.