Umami covers goals, funnels, journeys and revenue. What does Prelumen Analytics do differently?

Umami measures revenue by having you send the properties revenue and currency along with the tracked event. Prelumen Analytics instead connects your payment provider and puts revenue on top of traffic by source, page and campaign in realtime — and, after opt-in per website, per visitor as well. On top of that come funnels with per-step drop-off, custom events as conversion signals, and aggregated form friction over explicit form and field aliases, without field values and without any entered text.

How do the two products differ in their privacy setup?

Both measure without cookies. Umami identifies visitors through a hash of IP address, user agent and website ID with a rotating salt and, according to its own documentation, does not store the IP; Do-Not-Track is switched on through a tracker attribute. Prelumen Analytics processes and hosts in the EU and respects DNT and GPC signals by default, with nothing to configure for it; the person-level view stays opt-in per website. Both descriptions cover out-of-the-box product behavior; for your specific setup, the implementation decides.

Umami is MIT-licensed. What does that mean for the decision?

MIT is a permissive license: the code may be adapted, embedded and redistributed, including in closed products. If that is exactly what you need, Umami is the right call: the code sits with you, along with operations, updates and the database. Prelumen Analytics goes the other way: no source code to adapt, no installation on your side — but equally, nobody on your team looks after the database, updates and backups.

How do AI agents access the data?

Umami provides a REST API across all application functions, in Umami Cloud from the Pro plan; Umami does not offer an MCP server of its own, and the MCP servers you can find are third-party community projects. Prelumen Analytics ships a native MCP server across traffic, check, compliance, carbon and issue data on selected plans, plus a REST API. That way your agents query not only traffic but also open findings and proof.

What happens after a finding in Prelumen Analytics?

Checks for quality, security, accessibility, privacy, SEO/GEO, content and carbon run as subscriptions on fixed intervals. Every finding becomes an issue: prioritizable, with an executive summary for decision-makers and developer guidance for implementation; anything severe or urgent goes out as an incident alert without delay. Umami documents no check or issue layer for this — analysis there runs in dashboards and boards you build yourself, and follow-through in your own process.

Umami Alternative

You adapt Umami yourself. Prelumen checks your website for you.

Cookie-free realtime analytics from the EU, from €0. Revenue comes from your connected payment provider, checks run on a fixed schedule, every finding becomes an issue — no database or update cycle on your side.

Start where you can stay.

Analytics history rarely moves cleanly between products. Start free with the system that already has the next layer built in: revenue attribution and funnels as well as audits, issues and verifiable proof when you need them.

Free isn’t a trial mode. It’s the product, in small.

Start for free Plans and Pricing

Choose by fit

Both are privacy-first: they measure cookie-free and pass no data to ad networks. The decision comes down to licensing and data ownership — and to whether checks, issue follow-through and agent access should sit in the same product.

Prelumen Analytics is a fit when

Revenue should come from your connected payment provider and sit on top of traffic by source, page and campaign in realtime.
Accessibility, security, privacy, SEO/GEO, content and carbon should run as recurring checks alongside your growth metrics.
Every finding should become a prioritizable issue with an incident alert instead of a report someone has to carry forward.
Your own AI agents should query traffic, check and issue data through a native MCP server.

Umami Analytics is a fit when

A permissive MIT license is a given: the analytics code should be adaptable, embeddable and redistributable without copyleft obligations.
Analytics raw data should live in a PostgreSQL database your team provisions itself and queries directly via SQL alongside your own domain data.
Analytics should ship as a component inside your own product or under your own brand, with the license as a purchase criterion.

Capability comparison

Traffic, campaigns, funnels, journeys and revenue are covered by both products. The rows show where licensing, data ownership and the layers after analysis diverge.

Focus area	Prelumen Analytics	Umami Analytics
Operating model	Human and agentic operations layer: analytics, revenue attribution, diagnostics and issue workflow in one product	Privacy-first analytics platform for traffic, campaigns, behavior, conversions and revenue, self-hosted or in the cloud
Revenue and conversion	Revenue by source, page and campaign in realtime once your payment provider is connected; funnels, custom events, form friction	Goals, funnels, journey, retention, attribution and revenue in the dashboard; revenue values are sent along as revenue and currency properties on your own event
Privacy baseline	Cookie-free default, EU processing and hosting, DNT/GPC respected by default	Cookie-free measurement via a hash of IP address, user agent and website ID with a rotating salt; Do-Not-Track is enabled through the tracker attribute data-do-not-track
Diagnostics scope	Built-in checks for quality, security, accessibility, privacy, SEO/GEO, content and carbon, as subscriptions on fixed intervals	Web analytics including Core Web Vitals, plus session replay and heatmaps through an additional recorder script
Action after insight	Every finding becomes an issue with incident alerts: weighted by page hits from the last 30 days and resolved or ignored across every affected URL in one step	Reporting in dashboards and boards you build yourself; follow-through runs in your own process
AI agent access	Native MCP server across traffic, check, compliance, carbon and issue data, on selected plans	Agent access through the REST API; Umami does not offer an MCP server of its own
API surface	REST API + MCP on selected plans	REST API across all application functions; in Umami Cloud from the Pro plan, the Streaming API from the Business plan
Daily simplicity	Add the tracker and realtime numbers are there with no further configuration; checks and issues live in their own areas	Installed with a single tracker script, analyzed in clearly scoped reports
Hosting model	Managed EU platform with reduced customer-side code and infrastructure surface	Self-hosted service on your own PostgreSQL database from v12.14 with Node.js from 18.18, or Umami Cloud with a selectable data region in the US or the EU
License and code model	Managed product: no source code, update or database lifecycle on your side	MIT-licensed source code: adaptable, embeddable and redistributable, with operations, updates and the database on your side
Best-fit profile	Teams running traffic, revenue and website quality in one managed system and working findings off there too	Teams that adapt the analytics code themselves under a permissive license and keep raw data in their own database

Decision guide

Umami measures traffic, campaigns, funnels and revenue itself. What remains is an operating question: who holds the database and the updates, and where the follow-up work after measurement happens.

Choose Prelumen

when revenue from your connected payment provider, recurring checks, issue follow-through and agent access should sit in one managed EU system.

Choose Umami

when a permissive MIT license and analytics raw data in your own PostgreSQL database are firm requirements.

Clarify the license question first

when cookie-free analytics is settled but whether code and database have to stay in house is still open.

Frequently Asked Questions

Umami covers goals, funnels, journeys and revenue. What does Prelumen Analytics do differently?: Umami measures revenue by having you send the properties revenue and currency along with the tracked event. Prelumen Analytics instead connects your payment provider and puts revenue on top of traffic by source, page and campaign in realtime — and, after opt-in per website, per visitor as well. On top of that come funnels with per-step drop-off, custom events as conversion signals, and aggregated form friction over explicit form and field aliases, without field values and without any entered text.
How do the two products differ in their privacy setup?: Both measure without cookies. Umami identifies visitors through a hash of IP address, user agent and website ID with a rotating salt and, according to its own documentation, does not store the IP; Do-Not-Track is switched on through a tracker attribute. Prelumen Analytics processes and hosts in the EU and respects DNT and GPC signals by default, with nothing to configure for it; the person-level view stays opt-in per website. Both descriptions cover out-of-the-box product behavior; for your specific setup, the implementation decides.
Umami is MIT-licensed. What does that mean for the decision?: MIT is a permissive license: the code may be adapted, embedded and redistributed, including in closed products. If that is exactly what you need, Umami is the right call: the code sits with you, along with operations, updates and the database. Prelumen Analytics goes the other way: no source code to adapt, no installation on your side — but equally, nobody on your team looks after the database, updates and backups.
How do AI agents access the data?: Umami provides a REST API across all application functions, in Umami Cloud from the Pro plan; Umami does not offer an MCP server of its own, and the MCP servers you can find are third-party community projects. Prelumen Analytics ships a native MCP server across traffic, check, compliance, carbon and issue data on selected plans, plus a REST API. That way your agents query not only traffic but also open findings and proof.
What happens after a finding in Prelumen Analytics?: Checks for quality, security, accessibility, privacy, SEO/GEO, content and carbon run as subscriptions on fixed intervals. Every finding becomes an issue: prioritizable, with an executive summary for decision-makers and developer guidance for implementation; anything severe or urgent goes out as an incident alert without delay. Umami documents no check or issue layer for this — analysis there runs in dashboards and boards you build yourself, and follow-through in your own process.

Checks and Audits

Checks that lead to action.

Compliance and Accessibility

Compliance starts with checks, not claims.

To Compliance and Accessibility

Privacy Analytics

Privacy-first analytics without flying blind.

To Privacy Analytics

Cookie-free analytics that brings operations and proof along.

Use Prelumen Analytics when nobody on your side should be maintaining an analytics database and measurement, checks and proof still need to live in one place.