Matomo vs Umami

For most teams, yes, with caveats. Matomo's heatmaps and session-recording plugin captures click maps, scroll maps, and session replays comparable to a basic Hotjar setup. What you give up is some of the polish: Hotjar's funnel-from-recording flows, its survey tooling, and the speed of its UI when you have thousands of recordings. Matomo's plugin is fine for spot-checking pricing pages, debugging a confusing checkout, or showing rage-clicks to a designer. It is less suited to a product team that runs continuous qualitative research as a discipline. The plugin is a paid Matomo add-on, so factor in licensing alongside hosting costs.

Yes. The big absences are heatmaps, session replay, A/B testing, an ecommerce module with product-level reports, a built-in tag manager, and a dedicated GA4 historical importer. Multi-site administration for many properties is also weaker. Whether any of that matters depends on what your stakeholders actually ask for. Most product teams running one to a dozen sites use less than ten per cent of Matomo's surface area; for them, Umami's smaller feature set is a benefit, not a gap. Agencies, enterprises, and ecommerce operators often genuinely need at least one of the missing pieces, and that is the line where Matomo starts to make sense.

Umami runs comfortably in 256-512MB of RAM on a small VPS. A $5 per month Hetzner or DigitalOcean instance with Postgres on the same box handles a small portfolio of sites without trouble. Matomo's official minimum is also around 512MB, but that is optimistic. With plugins enabled and the archiving job running across 90 days of data, plan for 2GB of RAM, SSD storage, and tuned PHP-FPM and MySQL. Matomo also benefits noticeably from putting MySQL on dedicated storage as traffic grows, where Umami's narrower schema scales gracefully on shared resources for far longer.

At 100,000 pageviews per month, Umami Cloud Pro lands around $19 per month. Matomo Cloud at the same volume is roughly $39 per month, with entry plans starting around €29 for lower volumes. The price difference reflects the products: Umami Cloud is hosting a smaller application and a narrower feature set, while Matomo Cloud is hosting the full plugin ecosystem with the operations burden removed. Both are honest deals for what they include. If you need Matomo's depth, Cloud is almost always cheaper than running it yourself once you cost in your own time.

Umami is cookieless by default. You install it, paste the snippet, and you are done. There is no consent banner needed for analytics under most readings of GDPR and ePrivacy. Matomo can run cookieless too, but it is a configuration: you disable the visitor cookie, turn off any plugins that rely on persistent identifiers, and accept that some cross-visit attribution becomes weaker. The Matomo path is well-documented and works, but it is a deliberate choice rather than the out-of-the-box behaviour. For a team that wants to never think about consent banners again, Umami removes the question entirely.

Sort of. Matomo has a dedicated GA4 importer plugin that pulls historical data through the Google Analytics Data API and reshapes it into Matomo's schema. It is slow, it does not import everything, and there are known caveats around custom dimensions and conversions, but it is a real, supported tool. Umami does not have a comparable importer; the practical path is to export from GA4 to BigQuery or CSV and load the data into Umami's database manually, which is more work and produces a less complete result. If a clean GA4 historical migration matters to you, Matomo is the safer bet.