Open Source Fathom Analytics Alternatives

Umami is a privacy-first analytics platform that puts traffic, campaigns, behavior, conversions and revenue in one place. It sets no cookies and does not follow people around the web, so a team gets the numbers it needs without building a profile of every visitor who lands on the site.

The application runs on Node.js version 18.18 or later and stores everything in PostgreSQL version 12.14 or newer. A single DATABASE_URL entry in an env file is enough to start, and the build step creates the tables on first install along with an initial admin login you should change straight away.

A handful of choices shape how an installation behaves.

• Self-hosted or cloud: run the platform on your own server or use the hosted service, with the same product either way.
• Docker deployment: an official image and a compose file bring up Umami together with a PostgreSQL database in one command.
• Two-factor authentication: a 64-character hex encryption key switches it on, and it stays unavailable until that key exists.
• Configurable API base: the API_URL setting points internal interface calls at a relative path or an absolute host proxied through the local route.
• Plain upgrades: pull the repository, install dependencies and rebuild, or pull the new Docker image and recreate the containers.

Umami suits site owners who want to answer questions about visits and revenue while keeping the raw data on infrastructure they control. The requirements stay modest, a Node server and a Postgres instance, which makes it a reasonable fit for a small virtual machine.

Plausible counts visits without counting people. It stores no personal data and no IP addresses, and it sets no cookies or persistent identifiers, which keeps it compliant with GDPR, CCPA and PECR and removes the consent banner that a conventional analytics script drags along with it.

Everything lands on a single page rather than a tree of menus and custom reports, and the tracking script is small enough not to slow a site down. The backend is Elixir and Phoenix, general data sits in PostgreSQL and analytics data in ClickHouse, with a React and Tailwind frontend.

What arrives beyond the visitor count is worth listing.

• Goals and funnels: track conversions, revenue attribution and funnels through custom events and dimensions, with codeless tracking for outbound clicks, downloads, form completions and 404 pages.
• Modern routing: single page apps work out of the box, including pushState and hash based routing.
• Reports and sharing: weekly or monthly email or Slack reports, traffic spike and drop alerts, role based team access, and dashboards shared publicly or by link.
• Search insights: the Google Search Console integration brings keyword data into the same dashboard.
• Data out: an events API sends data in, while a stats API and CSV export take it back out.

Self-hosting means Plausible Community Edition, a free long term release published twice a year. It omits the premium funnels, ecommerce revenue goals, SSO and sites API, and its bot filtering is basic rather than advanced. In exchange you get the raw ClickHouse data and full control over where the server sits.

Positioned as the modern replacement for Google Analytics, Rybbit is an open source analytics platform that takes a couple of minutes to set up. It answers the questions a product team asks without the cookie banner and consent plumbing that the usual tools drag along.

Tracking works without cookies, so visitors are counted in a privacy-friendly way, and the dashboards cover both sides of measurement: the traffic report a marketing team reads and the behavioral detail a product team needs.

The reporting goes well past a count of pageviews.

• Core web metrics: sessions, unique users, pageviews, bounce rate and session duration, updated in real time.
• Session replays: recordings of individual sessions sitting next to the aggregate numbers.
• Product analysis: goals, retention, user journeys and funnels, each with a dashboard of its own.
• Filtering: more than fifteen dimensions to slice by, plus custom events carrying JSON properties.
• Location detail: country, then region, then city, with map visualisations built on the same data.

There are two ways to run it, a hosted service or self-hosting on your own VPS following the deployment documentation, and both support organizations and an unlimited number of sites. A public demo runs on a real production site for anyone who wants to click around first, and the code is licensed under AGPL version 3.

Openpanel puts the depth of Mixpanel next to the simplicity of Plausible, an open source web and product analytics platform for teams who want funnels and user profiles without settling for Google Analytics to get them cheaply.

Events land in ClickHouse while Postgres holds the account data, with a Next.js dashboard, a Fastify event API, and Redis, BullMQ and GroupMQ behind the queues. Tracking is cookieless by default and GDPR compliant, and the SDKs cover web, Swift, Kotlin and React Native as well as server-side collection.

The feature set reaches well past counting pageviews.

• Funnels and cohorts: analyze how users move through a flow and group them by behavior.
• User profiles: keep session history per person rather than aggregates alone.
• Session replay: records and replays sessions with privacy controls and no monthly session cap.
• A/B testing: runs variant tests with detailed breakdowns in the same product.
• Revenue tracking: follows purchases, subscriptions and lifetime value beside product events.
• MCP server: exposes 38 hosted tools so Claude, Cursor or any MCP client can answer questions about your users.

Dashboards update live and can be assembled from custom charts, with event and funnel based notifications when something moves, and Google Search Console among the integrations that enrich the data. Self-hosting is documented and deliberately kept simple, while local development needs Docker, Node and pnpm.

The very first version of Fathom Analytics stayed open source after the product became a paid hosted service. Fathom Lite is that code, a simple website analytics dashboard you install on a server of your own, downloaded millions of times.

The maintainers are clear about its status. No new features are being added to Lite, though they commit to maintaining it long term and fixing bugs as they surface. Anyone comparing it against today's hosted product should expect an older interface and a narrower feature set.

The README spells out plainly what the self-hosted version lacks.

• Cookies: Lite uses cookies, while the hosted product tracks without them.
• Dashboard: the current view with live visitors, filters and detail panels is not part of Lite.
• API: programmatic access to your data belongs to the hosted plans only.
• Events: custom events, ecommerce tracking and campaign parameters are absent.
• Operations: scaling, backups and a global CDN become your responsibility rather than someone else's.

Installing it needs Go and npm for a development build, or the prebuilt Docker image for a faster start, after which an account is registered from the command line and the dashboard answers on port 8080. Tracking begins by creating a site and pasting the snippet into your pages, and a content security policy needs the instance host allowed for scripts and images. Lite suits anyone who wants basic, self-owned traffic numbers and can live with a codebase in maintenance rather than development.

Open Web Analytics is a tracking server you install yourself, offered as an alternative to commercial tools such as Google Analytics. The bargain is explicit. You run the server and the database, and in exchange the data collected about the people using your sites never leaves your hands.

The repository installs the OWA server together with a first party JavaScript tracker to drop into your pages. PHP applications can report through the OWA PHP SDK instead, and WordPress sites have a dedicated plugin. Building from a clone needs Composer for PHP dependencies and Node with npm for the frontend, since the vendor directory and the built public assets, tracker included, are deliberately not committed to git.

Reporting covers considerably more than page counts.

• Tracking: visitors, pageviews, ecommerce transactions and any action you configure.
• Multiple sites: an unlimited number of websites from one OWA server.
• Heatmaps: see where visitors clicked on a page.
• Domstream recordings: replay a session as it played out in the browser.
• Geolocation: place visitors by where they connected from.
• REST API: administer the installation and pull data out programmatically.

Every report can be viewed and customized, the reporting interface supports multiple users, and custom modules extend the framework where the defaults stop. Read the technical requirements first, since this is a PHP application with a database behind it rather than a hosted snippet, and the upgrading notes list which interfaces are deprecated for anyone maintaining a third-party module or theme. It is GPL version 2 or later.

Litlyx is web analytics that skips cookies entirely and gets out of the way during setup. One deferred script tag carrying a workspace id is the whole installation, after which page visits, real-time users and unique visitors start recording.

Beyond the script tag there is an npm package, litlyx-js, that works with modern JavaScript and TypeScript frameworks. Import the client, initialize it with a workspace id, and automatic tracking begins. WordPress sites inject the same script through a third-party plugin.

What sits past the pageview counter is deliberately small.

• Custom events: any named event can be fired from code, with optional metadata such as product name, price and currency.
• HTTP ingestion: events post straight to the broker endpoint, so a single curl call is enough to test a project.
• Cookie-free by design: no cookies are set, which removes the consent banner question before it is asked.
• Self-hosted dashboard: Docker images are published and the dashboard comes up on port 3000 through Docker Compose.
• Host redirection: the script tag takes host, port and secure attributes so data forwards to your instance instead of the hosted one.

Litlyx is Apache 2.0 licensed. The project positions itself against Google Analytics 4, PostHog and Mixpanel, and self-hosting unlocks the full platform for free, with paid lifetime plans available for teams scaling to more client seats. A public roadmap and a Discord channel cover what is being built next.

Databuddy is an analytics and data management platform for web applications, covering real-time dashboards, user behavior tracking and data visualization. It is built with Next.js, React and TypeScript in a Turborepo monorepo, and the README is unusually candid about which features ship today and which are still marked as coming.

It runs on Bun with Postgres, ClickHouse and Redis underneath, split into separate services for the API, event ingestion, an investigation worker and short links. Backend images are published to GHCR, so a self-hosted deployment is a compose file rather than a build project.

The analytics surface covers the usual questions.

• Real-time dashboard: metrics update as events arrive, with user behavior tracking behind them.
• Funnel analysis: multi-step conversion paths, alongside goal tracking and conversion analytics.
• Custom events: application-specific events are tracked beyond what is captured automatically.
• Multi-tenant support: separate tenants are served from one deployment.
• Data protection: GDPR compliance, data encryption and a configurable salt for hashing IP addresses.
• API access: data is reachable programmatically, with export available.

Databuddy is AGPL-3.0 licensed. Self-hosting uses a dedicated compose file, distinct from the development one that only starts the databases. Configure the env file with an image tag, URL-safe database passwords, public URLs, an auth secret, an encryption key, an IP hash salt and an AI gateway key, start the databases, initialize the schemas from a checkout, then bring up the four backend services. Bun 1.3.14 and Node.js 20 are the prerequisites.

Swetrix reports on your traffic without setting a cookie, asking for consent or tracking anyone across devices, and it anonymizes what it does collect. That makes it a direct replacement for Google Analytics on sites where the compliance paperwork costs more than the numbers are worth.

It also goes past pageviews. Error tracking, performance monitoring, session replays, funnels and custom events sit in the same product, so a small team can retire several subscriptions at once. The project has been open source since 2021, is bootstrapped, and is funded by its subscribers rather than investors.

The dashboard is real time, and the tracking snippet stays small.

• The metrics that matter: top pages, geolocation with a map view, devices, traffic sources and UTM campaigns.
• Custom events and properties: track conversions, sales or any action with your own naming.
• Sessions, flows and funnels: follow journeys through the site and see where people drop out.
• Performance monitoring: real-user timings for TTFB, DNS, TLS and rendering.
• Error tracking: client-side errors captured with detail and rolled into aggregated views.
• Sharing and teams: public or password-protected dashboards, teammates with roles, and organizations for wider access control.
• Data portability: CSV export plus a developer API for everything the dashboard shows.

The Community Edition self-hosts with Docker, connecting the API and UI to MySQL, ClickHouse and Redis. The cloud adds session replays, network intelligence by ISP and connection type, revenue analytics and an AI query interface, hosted in Germany.

Betterlytics measures site traffic without cookies, which takes the consent banner and the third party data sharing out of the picture. It is GDPR, CCPA and PECR ready out of the box, and the data it collects is never handed to anyone else.

The ingestion path is written in Rust and events land in ClickHouse, with a Next.js and React dashboard in front and Postgres holding account data. Sites are instrumented with a script tag under 2KB, or through the React and Next.js SDKs.

Reporting is grouped into several areas of the dashboard.

• Core analytics: page views, visitors, bounce rate, traffic sources, geography, devices, custom events and real time data.
• Deeper analysis: session replay, user journeys, funnels, annotations, outbound link tracking and comparisons across time periods.
• Performance monitoring: Core Web Vitals, uptime and SSL certificate checks, and public status pages on a domain of your own.
• Privacy defaults: cookieless tracking, data anonymization and EU hosting on the managed service.
• Access control: roles, two factor authentication and OAuth sign in with Google or GitHub.

Two ways to run it are documented. The managed cloud is EU hosted, updates itself and has a free tier, while the self-hosted route is a manual Docker installation where the servers, the updates and the data location are yours. The code is AGPL 3.0, with third party components attributed separately.

HitKeep is web analytics that ships as one Go binary with DuckDB and NSQ embedded, so there is no separate database, queue or cache to operate. It also removes the usual split between a free edition and a paid one holding the features teams actually need, since custom tracking domains and team SSO live in the same MIT-licensed codebase.

The browser tracker sets no analytics cookies, respects Do Not Track, and collects aggregate website evidence instead of building a cross-site identity. Pageviews and automatic events such as outbound clicks, file downloads and form submissions start flowing as soon as the script tag is on the page.

Reporting follows acquisition through to the outcome.

• Conversion reporting: pages, custom events, goals, funnels, ecommerce revenue and Web Vitals sit in one place.
• AI as a channel: crawler fetches, AI-referred visits and chatbot outcomes stay distinct from ordinary traffic.
• Ask AI: answers cite the aggregate evidence behind them, and a read-only MCP endpoint gives approved assistants governed access.
• Search Console: clicks, impressions, click-through rate and position land beside the rest of the traffic data.
• Open exports: complete takeout, APIs, webhooks, share links and permissions keep the data useful outside HitKeep.

Install it with Homebrew on Apple silicon macOS or x86_64 Linux, pull an ARM64 binary, or run the published Docker Compose file and create the first account on port 8080. HitKeep is deliberately web-focused, so anyone who needs session replay, mobile SDKs or built-in experimentation should look elsewhere.

Prisme Analytics collects page views and custom events without cookies and stores only anonymized data, which takes most of the compliance work out of measuring a website. Setup is a script tag plus a noscript pixel, and numbers show up in a web analytics dashboard within minutes.

The ingestion server is written in Go and ships as a Docker image, while the dashboards run on Grafana. That choice brings user management, teams, permissions, multiple organizations and custom dashboards along with it, instead of a second set of account features written from scratch.

Several details set it apart from heavier analytics stacks.

• Small payload: the tracking script is around 2 kB, roughly 22 times smaller than Google Analytics, and the pixel for visitors without JavaScript is 35 bytes.
• Bot filtering: scrapers and spam traffic are dropped automatically.
• Campaign tracking: UTM parameters attribute visits to newsletters and campaigns.
• Single page apps: any pushState based router is followed without extra wiring.
• Throughput: the project's own load test ingested more than 50,000 requests a second on one AMD Ryzen 7 machine with the load generators running beside it.
• No paywall: every feature is available in the open source version.

You can follow the self-hosting guide for Docker or sign up for the hosted cloud, and the same feature set applies either way. The code is AGPL-3.0 with MIT exceptions listed in a separate licensing file.