OpenReplay vs Umami
| Tagline | Self-hosted session replay and product analytics for web apps | Simple, fast, privacy-focused web analytics in a single lightweight dashboard |
| Category | Product & Web Analytics | Product & Web Analytics |
| Replaces | Hotjar, Amplitude | Google Analytics |
| GitHub stars | 13k | 39k |
| Language | TypeScript | TypeScript |
| License | Apache-2.0 | MIT |
| Self-host difficulty | 5/5 Advanced | 3/5 Moderate |
| Deploy options | Kubernetes Docker Compose Manual | One-Click Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | yesterday | yesterday |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
OpenReplay
- Self-hosting requires a Kubernetes-based multi-service stack; resource-hungry and complex to operate.
- Product-analytics features (funnels, cohorts) are less mature than Amplitude/Mixpanel.
- No traditional aggregate web-analytics dashboard; it is session-centric.
Umami
- Deliberately minimal: no heatmaps, session replay, or deep product-analytics like funnels/retention found in Mixpanel/Amplitude.
- Event/custom-property analytics are basic compared to dedicated product-analytics tools.
- No built-in alerting or anomaly detection.
Bottom line
Choose Umami if you want the lower-effort setup; choose Umami for the larger community and ecosystem. Open each guide below for deploy steps and the full feature gap.
Umami
Simple, fast, privacy-focused web analytics in a single lightweight dashboard