umami-software/umami

Umami is a credible self-hosted analytics option if you want traffic, campaign and conversion numbers without shipping user data to an ad-funded third party. Its setup is well documented and the UI is approachable; the harder question is how much customization and scale you need.

The problem

A site owner wants to know which pages, campaigns and conversion paths bring results without handing visitor records to a third party or configuring a cookie banner for basic traffic counts. Traditional hosted analytics often means adding a script that phones home, and the data ends up in someone else's dashboard. Umami replaces that with a first-party tracking script and a dashboard you run yourself, backed by PostgreSQL. After installation you get pageviews, campaigns, audience segments, cohort analysis and revenue reporting in one interface, based on the project's own description.

What's different

The distinguishing choice is self-hosting as a first-class path: the README documents running from source with Node.js 18.18+ and PostgreSQL, plus an official Docker image and compose file that bundle the database. That matters because the alternative to a hosted analytics vendor is often a vague promise about privacy; here the data store is a database you control. Umami also documents an MCP endpoint, disabled by default and enabled with an environment variable, so an AI client can query analytics with a separately generated API key.

The trade-off is operational weight. You are responsible for the database, the reverse proxy or port configuration, and the update cycle: source installs require pulling, reinstalling dependencies and rebuilding, while Docker updates require pulling new images and recreating containers. First-time builds create the tables and an admin login with a default password, so account hardening belongs on the initial setup checklist. The README shows the deployment mechanics but not benchmarks for high-traffic sites, so volume planning needs your own testing.

Who should try it

A developer or small team running a content site, documentation portal or product landing page is a good fit: they can deploy a container, add the tracking script, and get campaign and conversion reporting without a separate consent flow for basic counts. A technically comfortable individual with a single personal site can also use it, though the database and update chores may outweigh the value compared with a lighter hosted option.

A poor fit is someone who wants zero maintenance or only needs a raw event pipeline at very large scale. The PostgreSQL dependency and rebuild-based updates add ongoing work, and a commenter on Hacker News on 2025-02-17 described having to modify Umami heavily for a game companion app because of missing features and performance issues, which suggests custom, high-volume use cases deserve early load testing. The Docker compose path is the gentler entry point; source installation is more involved.

Requirements and limitations

You need Node.js 18.18+ and PostgreSQL v12.14+ for a source install, or Docker for the packaged path, plus a reverse proxy or adjusted port to serve it publicly. Two-factor authentication cannot be enabled until a separate 64-character encryption key is configured, so security hardening is a deliberate step rather than a default. The documented private MCP endpoint means API keys are another credential to manage.

Upkeep is the bigger long-term cost. Source-based deployments must be rebuilt after each pull, and database schema changes arrive through the build step, so updates are not a single click. The README does not lay out a backup or migration plan; you should decide how the PostgreSQL data is backed up before relying on it for records you care about. For evaluation, the hosted demo and the getting started guide are the practical starting points.

HotRepo's take

HotRepo's dated observations show 39,649 stars and a +43 daily gain on 2026-10-24, then 39,654 stars and +45 on 2026-10-25, with two daily-board appearances. That sample is too short to judge momentum, and the repository has existed since 2020. The Hacker News thread from 2025-02-13 drew 348 points and 168 comments, which signals discussion volume rather than a verdict.

Adoption judgement: worth trying for a small self-hosted site where database ownership is the point. Before committing, verify the PostgreSQL version and update path in the project instructions against your hosting setup.