Umami vs. Amplitude
Web and product analytics, open source and cookie-free by default
Umami and Amplitude both cover web and product analytics. Umami is open source, self-hostable, and cookie-free by default. Amplitude goes deeper on experimentation and identified-user analysis.
Feature comparison
| Feature | Umami | Amplitude |
|---|---|---|
| Analytics workflows | ||
| Web analytics | ||
| Custom events | ||
| Funnels | ||
| Retention | ||
| Cohorts | Not on the Free plan | |
| UTM and channel reporting | ||
| Custom dashboards | ||
| Session replay | Cloud Business+ or self-hosted | 10K free sessions / mo |
| Heatmaps | Cloud Business+ or self-hosted | Plus plan and above |
| Autocapture of clicks and forms | ||
| Feature flags | ||
| Experiments | Measure via tags | |
| Official MCP server | Read-only | Read and write |
| Collection & identity | ||
| Web install | Script tag | Script tag or SDK |
| Cookies in the default setup | None | Cookie (other storage optional) |
| Collected by default | No personal data | IP address, device and user IDs (configurable) |
| Identity model | Anonymous sessions, optional distinct IDs | Device IDs merged with user IDs |
| Deployment | ||
| Open source | MIT | |
| Managed cloud | US or EU | |
| Self-hosting | Docker and PostgreSQL | |
| Pricing | ||
| Free cloud tier | 100K events / mo | 2M events / mo |
| Pricing model | Plans with included events | Event-based |
| Paid cloud plans | From $20 / mo | Usage-based Plus, custom above |
| Self-hosting cost | Free | Not available |
Last verified October 2026. Spot something out of date? Let us know.
Where they overlap
Umami and Amplitude both cover web analytics and product analytics. Each has events, funnels, retention, cohorts, dashboards, session replay, and heatmaps, and each reports on channels and campaigns. Both install on the web with a script tag, and both have an official MCP server for AI assistants.
Where Umami differs
Privacy defaults. Umami's tracker uses no cookies and collects no personal data unless you send it. Amplitude's Browser SDK stores its identity in a cookie by default and tracks IP address along with device and user IDs. Amplitude supports other storage options and lets you disable these fields, and its documentation leaves the consent model to the customer.
Open source and self-hosting. Umami is MIT licensed and can run on your own infrastructure with Docker and PostgreSQL. Amplitude is a managed cloud service with US and EU data centers.
Plan structure. Umami Cloud includes cohorts on every plan and gates session replay and heatmaps to Business. Amplitude includes session replay on every plan, and gates behavioral cohorts and heatmaps to its paid plans. Compare the features you need against both pricing pages before deciding.
Identity. Umami works with anonymous sessions and lets you link them with an optional distinct ID. Amplitude resolves device IDs to user IDs to build a per-user history.
Where Amplitude goes further
Amplitude includes feature flags and web experimentation, autocapture of clicks, form interactions, and downloads, and an MCP server that can create and edit charts, dashboards, cohorts, and experiments as well as query them. Its free plan is larger: 2 million events and 10,000 session replays per month, compared with 100,000 events on Umami's Hobby plan, where session replay requires a Business plan. Teams that need identified-user analysis with experimentation in one product will find more of that in Amplitude.
Which one fits
Choose Umami if you want web and product analytics that are cookie-free by default, want to self-host or keep analytics data on your own infrastructure, or prefer plans with a fixed monthly price and included events.
Choose Amplitude if you need experimentation and feature flags tied to your analytics, depend on identified-user analysis, or want autocapture instead of defining events yourself.
Trying Umami alongside Amplitude
You can add the Umami tracker next to the Amplitude script and compare the two on live traffic. Installing the tracker starts new data collection only. It does not import historical Amplitude events, and event names and properties need to be mapped to Umami custom events by hand.