PostHog vs Umami
PostHog and Umami both answer the same question: how do you know what users actually do? Product analytics with session replay, feature flags, experiments and surveys bundled into one open source platform. Open source privacy-focused analytics you can self-host on your own database, or use as a hosted service. Umami covers more of the ecosystem, so it survives a change of framework; PostHog is the better fit while you stay where it is strongest.
Verdict
Umami covers more of the ecosystem, so it survives a change of framework; PostHog is the better fit while you stay where it is strongest.
Pick PostHog if
- ✓Funnels, retention and cohorts answer product questions page views never could.
- ✓Session replay lets you watch the exact path a confused user took.
- ✓Feature flags and experiments share the same identity data as the analytics.
Pick Umami if
- ✓Self-hosting means the raw analytics data sits in a database you already run.
- ✓Stores into Postgres or MySQL, so you can query it with plain SQL.
- ✓No licence cost at all when you supply the hosting yourself.
| Comparison | PostHog | Umami |
|---|---|---|
| Pricing shape | Generous free monthly event allowance, then usage-based pricing per event, replay and flag request. | Free if you self-host on your own infrastructure, with a paid cloud plan by event volume. |
| Frameworks | Next.js, SvelteKit, Nuxt, React Native, Expo, Flutter | Next.js, SvelteKit, Nuxt, Laravel, Django, Rails |
| In one line | Product analytics with session replay, feature flags, experiments and surveys bundled into one open source platform. | Open source privacy-focused analytics you can self-host on your own database, or use as a hosted service. |
Pricing described qualitatively because published plans change often. Checked 2026-08-23. Confirm current terms on PostHog and Umami.
PostHog
Strengths
- ✓Funnels, retention and cohorts answer product questions page views never could.
- ✓Session replay lets you watch the exact path a confused user took.
- ✓Feature flags and experiments share the same identity data as the analytics.
- ✓Self-hostable and open source, so the data can stay on your infrastructure.
Tradeoffs
- ✗Full event tracking makes it a privacy and consent conversation, not a free pass.
- ✗The client library is heavy compared to a simple page-view script.
- ✗Breadth of features means real onboarding time before anyone gets value.
- ✗Event-based billing rewards discipline and punishes noisy instrumentation.
Umami
Strengths
- ✓Self-hosting means the raw analytics data sits in a database you already run.
- ✓Stores into Postgres or MySQL, so you can query it with plain SQL.
- ✓No licence cost at all when you supply the hosting yourself.
- ✓Multi-site and team support without paying per additional property.
Tradeoffs
- ✗Self-hosting means you own uptime, upgrades and database growth forever.
- ✗Analytics traffic writes to a database you must size and prune yourself.
- ✗Feature set trails commercial tools, especially around alerting and reporting.
- ✗Community support only, so an obscure bug can stall you.
Frequently asked questions
Is PostHog or Umami better?
Neither is better in the abstract. Umami covers more of the ecosystem, so it survives a change of framework; PostHog is the better fit while you stay where it is strongest. Decide on the tradeoff you can live with, then stop reading comparisons and ship.
What is the main drawback of PostHog?
Full event tracking makes it a privacy and consent conversation, not a free pass. The client library is heavy compared to a simple page-view script.
What is the main drawback of Umami?
Self-hosting means you own uptime, upgrades and database growth forever. Analytics traffic writes to a database you must size and prune yourself.
Can you switch from one to the other later?
Usually, at a cost that grows with how much of your product leans on the analytics layer. The sooner you wrap it in your own interface, the cheaper the exit stays.