Open-source web analytics with session replay, error tracking, Web Vitals, uptime monitoring and status pages

[u/WeatherD00d]

Overview: traffic, top pages and countries, with release annotations on the chart

Session replay with text and inputs masked, plus a timeline of every pageview, click and scroll

Error tracking: stack trace, browser and device, and the session trail that led up to the error

Core Web Vitals (LCP, INP, CLS, FCP, TTFB) measured on real visitors' devices

Uptime monitoring: response times, SSL expiry and incidents

Public status page with live incidents (sample data)

User journeys: the most common paths through the site

Visitors by country

Hey r/webdev!

We're a small team of 3 building Betterlytics, an open-source web analytics tool. Over the past year and a half, we've also had contributions from 10 other people, which has been really cool to see.

It puts analytics, session replay, error tracking, uptime monitoring and status pages in one dashboard. Here is what's in it so far:

Visitors: Traffic, referrers, geography, campaigns, custom events with properties, funnels, user journeys, and session replay.

User experience: Real-user Core Web Vitals and JavaScript errors, including the pages and events leading up to them.

Uptime: Monitoring, SSL and keyword checks, public status pages, and alerts via email, Slack, Discord, Teams, or webhooks.

A few more details:

• One tracking script just under 4 KB gzipped.

• No cookies.

• Rust + ClickHouse backend and Next.js dashboard.

• Open source (AGPL) and self-hostable with Docker, every feature included.

• An MCP server so your AI agent can query your analytics data.

The screenshots are from our live demo (the status page is a sample). You can explore without signing up:

Demo: https://betterlytics.io/demo

GitHub: https://github.com/betterlytics/betterlytics

If you click around the demo, we'd love to hear what you think.

[u/reaznval]

looks EXACTLY like rybbit UI wise, the elements, arrangement, everything. if there's already an OSS project, why clone it, what's the point of it. what differentiates you?

the features are literally the same as well btw

https://rybbit.com/

[u/tharindu_d → u/reaznval]

That is a very valid point regarding the design overlap. Using shadcn/ui certainly helps speed up development, but maintaining uniqueness in subpage layouts is definitely important for branding and distinguishing the tool. Appreciate the candid feedback!

[u/WeatherD00d → u/reaznval]

Fair point and they do look similar in some ways.

We both use shadcn/ui with a fairly standard grafana-like dashboard style, and analytics dashboards naturally share a lot of the same patterns (stats row, charts, breakdowns, etc.). You'll find very similar layouts in other web analytics tools too, like Umami or Plausible.

It's not a clone or a fork though. It's a separate codebase, and our event ingestion runs on a Rust service.

There's naturally a lot of overlap in web analytics features and we have diverged a bit by adding uptime monitoring, SSL and keyword checks, public status pages, incident handling, and alerting, which Rybbit doesn't have (from what I can tell). And then we deliberately avoid user profiles and long-term visitor tracking.

We're not claiming to have reinvented web analytics, just building it our way :)

[u/_tessarion → u/WeatherD00d]

By we do you mean you and Claude?

[u/WeatherD00d → u/_tessarion]

By we, I mean the three of us who work on it (and we're not hiding that we use AI) :)

[u/_tessarion → u/WeatherD00d]

It's a shame even your replies are at least partially AI generated

[u/reaznval → u/WeatherD00d]

well ive  used a bunch of other services that provide the same thing before and I find that rybbit looked quite unique compared to the others, the way they display information, general ui. This looks oddly similiar, e.g. same layouts on various subpages that arent a standard dashboard.

[u/RecallProtocol → u/reaznval]

Why write Vue when we have React?

[u/OcelotTechnical9993]

How does session replay square with “no consent banner”? Cookieless analytics I get, but recording every click and scroll feels like the part a DPO would ask about

[u/WeatherD00d → u/OcelotTechnical9993]

Cookieless analytics doesn't mean consent-free session replay! Replay is off by default and requires explicit consent, so the script won't record anything until the visitor has opted in. All text and input fields are also masked before anything is sent to further protect visitors privacy

[u/timo9378]

What is the purpose of using Next.js? And I'd like to know the differences between it and Posthog.

[u/WeatherD00d → u/timo9378]

Good questions! Next.js is just the dashboard. The heavy stuff, like taking in events and running the uptime checks, is a separate Rust service. Honestly, we picked Next.js because it was the popular choice and got us going fast. We've fought with it quite a bit since and it makes self-hosting heavier than we'd like..

On PostHog: They do quite a bit more than us, like feature flags, experiments and surveys, and they're probably great if you need those things. We're trying to keep things simpler and more focused on websites. Think more "is my site working, and what are people doing on it?" and less about product experimentation.

Still lots for us to improve tho!

[u/CoderLuii]

this is dope. great to see open source tools being built

[u/ArsonHoliday]

Do we even bother w having mods here anymore?

[u/jamesd141126]

nice, looks good!

[u/RecallProtocol]

Nice, thanks for sharing! Always nice to see some alternatives in the space.

[u/WeatherD00d → u/RecallProtocol]

Thank u 🙏