Should you build your own Matomo Cloud?
Run first-party web analytics with goals, campaigns, and user-owned data
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Matomo Cloud, run first-party web analytics with goals, campaigns, and user-owned data. The hard boundary is mature analytics depth, privacy controls, hosted operations, and premium plugins, plus data pipeline reliability and analytical depth.
ENOriginal research content in English. Original prompt preserved in English.
Build a personal replacement for Matomo Cloud in an empty repository.
Use Next.js 15, TypeScript, ClickHouse, PostgreSQL, and Docker Compose; do not offer alternative stacks.
The core loop is: collect privacy-conscious first-party web analytics events with goals and campaigns, answer a small set of product questions, and retain raw data under the owner's control.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Ship a lightweight browser SDK for page views and explicit custom events.
Create projects, API keys, environments, event names, and a documented event schema.
Ingest idempotently, filter obvious bots, truncate IP data, and avoid fingerprinting.
Build dashboards for visitors, sessions, funnels, retention, sources, pages, and events.
Expose filters by date, environment, device, country, referrer, and selected properties.
Add retention controls, raw-event export, deletion, health checks, and backup instructions.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out cross-site identity graphs.
Deliberately leave out session replay and automatic DOM capture.
Deliberately leave out warehouse-scale reverse ETL and enterprise governance.
Finish by running the tests and listing the exact commands used.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
Collect privacy-conscious first-party web analytics events with goals and campaigns, answer a small set of product questions, and retain raw data under the owner's control.
What you will need
- Docker
- ClickHouse
- PostgreSQL
- public HTTPS collector endpoint
- site script access
People still pay for Matomo Cloud because teams pay because analytics must keep collecting and remain trustworthy while the product changes underneath it. The recurring cost buys event schemas, bot filtering, identity, late data, retention, query cost, privacy, backups, and always-on ingestion, not just the visible interface.
xmature analytics depth, privacy controls, hosted operations, and premium plugins
xidentity stitching
xsession replay
xwarehouse connectors
xhigh-volume global ingestion and support
Prefer something ready-made?
UmamiGoals, campaigns and first-party data in a much smaller self-hosted package.Open source↗
MatomoThe same analytics engine with goals and campaigns; you replace the cloud bill with PHP and database upkeep.Open source↗License, setup, and limitations for each alternative.
How much does Matomo Cloud cost?
- Monthly billing
- $26/mo$26/mo
- Per year
- $312/yr$312/yr
- Annual billing
- $260/yr17% cheaper than paying monthly
- On a Brazilian card, with 3.5% IOF
- R$136/moR$1,359/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Matomo Cloud’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| business, 50,000 hits | $26/workspace≈ $26 | $21.67/workspace≈ $21.67 | 50,000 hits/month, 30 websites, 30 team members, 100 segments, 150 goals, 30 custom dimensions, 24 months raw-data retention, and report retention forever |
| business, 100,000 hits | $42/workspace≈ $42 | $35/workspace≈ $35 | 100,000 hits/month, 30 websites, 30 team members, 100 segments, 150 goals, 30 custom dimensions, 24 months raw-data retention, and report retention forever |
| business, 300,000 hits | $85/workspace≈ $85 | $70.83/workspace≈ $70.83 | 300,000 hits/month, 30 websites, 30 team members, 100 segments, 150 goals, 30 custom dimensions, 24 months raw-data retention, and report retention forever |
| business, 600,000 hits | $139/workspace≈ $139 | $115.83/workspace≈ $116 | 600,000 hits/month, 30 websites, 30 team members, 100 segments, 150 goals, 30 custom dimensions, 24 months raw-data retention, and report retention forever |
| business, 1 million hits | $204/workspace≈ $204 | $170/workspace≈ $170 | 1,000,000 hits/month, 30 websites, 30 team members, 100 segments, 150 goals, 30 custom dimensions, 24 months raw-data retention, and report retention forever |
| business, 2 million hits | $399/workspace≈ $399 | $332.50/workspace≈ $333 | 2,000,000 hits/month, 30 websites, 30 team members, 100 segments, 150 goals, 30 custom dimensions, 24 months raw-data retention, and report retention forever |
| business, 5 million hits | $975/workspace≈ $975 | $812.50/workspace≈ $813 | 5,000,000 hits/month, 30 websites, 30 team members, 100 segments, 150 goals, 30 custom dimensions, 24 months raw-data retention, and report retention forever |
| enterprise | custom | - | Custom allowances; required above 10 million hits/month |
Free tierno free tier
Billing termsmonthly + annual (2 months free, about -17%); no-card free trial; plan changes are prorated
Additional costsHits above the allowance are billed as overages rather than blocked; the current page exposes $2.60 per extra 5,000 hits on the 50,000-hit plan, while other bracket overage rates are not published in the static table. Crash reports, events, and other tracking requests consume the same hit quota.
verified 2026-08-12 · source ↗
Is it cheaper to build or buy Matomo Cloud?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (multi-day). Does not price what you give up (support, integrations, security).
Can I rebuild Matomo Cloud?
Kinda. The core of Matomo Cloud is buildable in a weekend with the prompt on this page, but there are real gaps: mature analytics depth, privacy controls, hosted operations, and premium plugins, identity stitching. Read the honest list above before committing.
How much does Matomo Cloud cost?
Matomo Cloud costs about $26/mo (Essential, checked 07/31/2026), which is $260 per year.
What do I lose by replacing Matomo Cloud?
Honestly: mature analytics depth, privacy controls, hosted operations, and premium plugins; identity stitching; session replay; warehouse connectors; high-volume global ingestion and support. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Matomo Cloud?
Yes: Umami (Goals, campaigns and first-party data in a much smaller self-hosted package.) Matomo (The same analytics engine with goals and campaigns; you replace the cloud bill with PHP and database upkeep.) The prompt is for when you want it exactly your way.