Analytics and monitoring decision
Matomo Cloud
Keep paying only if you need Matomo Cloud's managed hosting, SLAs, or priority support; otherwise self-hosting the official open-source Matomo repo is a practical one-day setup for a capable engineer and avoids recurring SaaS fees.
Visit website↗$29/mo
$348/yr
Read off the official pricing page.
$20one-off6 h to build
$0/mo4 h/mo upkeep
On cash alone, building overtakes the subscription at 1 seat.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Matomo Cloud alternatives, with the arithmetic →
What a replacement has to do
- Collect pageviews and events via a JavaScript tracking snippet, ingest and validate events on a server endpoint, store and aggregate events for reporting, render dashboards/reports and provide raw-export APIs, implement privacy features (IP anonymization, cookieless tracking).
What it still won’t have
- Managed hosting, scaling, and automated backups from Matomo Cloud
- SLAs, priority support, and dedicated Customer Success
- Bundled enterprise onboarding and migration services
What remains hard
- Compliance and regulation
Certified ISO 27001:2022
- Brand trust
Trusted by 1 million organisations worldwide
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted Matomo deployment using the official PHP app from https://github.com/matomo-org/matomo. Stack: Docker Compose running PHP-FPM/NGINX, MariaDB/Postgres (as supported), Redis (optional), and a cron scheduler. In scope: clone the repo, create Docker Compose files, configure database and environment variables, run DB migrations, expose the tracking JS, verify event collection from a sample site, set up archiving cron jobs, enable IP anonymization and data retention, configure daily backups to S3, and add a basic dashboard smoke-test. Out of scope: reimplementing Matomo features or building a new analytics engine. Include idempotent setup scripts, health checks, error handling, and automated tests for tracking ingestion, DB migrations, and backup restore.
How we checked
How the score was reached
- Self-host verdict base92
- An open-source build was found+5
- 6 cited sources+3
- Price verified on pricing page+3
- 2/2 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score99
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 6
Every page the run actually retrieved.
- official productMatomo homepage
- official pricingMatomo support plans
- official docsMatomo product features
- open sourceusefathom/fathom
- open sourcepirsch-analytics/pirsch
- official pricingMatomo Cloud pricing
Integrity checks
What held up, and what did not.
