Analytics 1 min read

Umami vs Matomo: analytics deployment and data controls

Compare documented self-hosting requirements, measurement scope and data questions.

Deployment and measurement

Umami and Matomo both describe self-hosted analytics and hosted options. Umami’s source installation documentation lists Node.js and PostgreSQL. Matomo’s self-hosted project lists PHP and MySQL or MariaDB and describes adding a JavaScript tag to each site. Check the version and operational resources your team can maintain.

The projects list campaign and conversion-related analytics, but their event definitions and hosted plan entitlements are not established as equivalent by these sources. Define the same pages, events and reporting periods before comparing results. Neither product was installed or tested in this review.

Data, privacy and price

Umami describes a no-cookie approach; Matomo describes keeping self-hosted data in your own database. Neither statement alone establishes compliance or a particular data residency for a hosted plan. Check actual collection, consent, retention, exports, processor terms and plugin behavior for your deployment and jurisdiction.

Umami’s code repository is MIT licensed; Matomo identifies GPL v3 or later. Code licences do not determine hosted subscription terms. Compare current usage limits, required paid plugins, support, infrastructure, backups and total cost from the actual offer; these sources do not establish comparable cloud pricing.

Rollout

Before adding any tag, review access controls and test the measurement setup with permission. Umami’s documented source build creates an initial login, so secure administrative credentials before exposing a self-hosted installation. No analytics data was collected for this comparison.

Sources

Umami: umami-readme · Evidence: documentation · Not checked

Matomo: matomo-readme · Evidence: documentation · Not checked

Next step

Tools in this guide

All analytics tools
All guides