39.6k stars · MIT, with a proprietary ee/ directory · desktop-v0.61.263 (2026-09-08)
Analytics, session replay, feature flags, experiments and surveys behind one snippet — four standing recommendations collapsed into one.
▶Repo detailsthe review · specs · pros & cons · install
What it is
A product analytics platform that bundles event analytics, session replay, feature flags, experiments, surveys and error tracking behind a single snippet. It is fully self-hostable, but in practice it is a cloud product with a large free monthly allowance.
Why it matters
This ledger has recommended Umami for analytics (Ed. 1, repeated in Ed. 5), GrowthBook for flags and experiments (Ed. 3 #6), OpenReplay for session replay (Ed. 9 #3) and Formbricks for surveys — four installs, four databases, four things to back up. Fifteen days after the first of them, none exists. PostHog is all four behind one script tag, and the honest recommendation is the cloud free tier rather than the self-host: you get an answer to "why do people leave the map screen?" this evening instead of after a ClickHouse deployment. The trade deserves stating plainly — you are sending visitor behaviour to a US company instead of keeping it on your own box, which is exactly the privacy position Umami and remark42 (Ed. 5 #1) were chosen for, and exactly why CookieConsent (#5) sits on this page beside it.
- Replaces four separate standing recommendations with one snippet. This is a decision as much as a tool.
- Generous free cloud tier — at your current traffic the bill is plausibly zero for a long time.
- MIT core and genuinely open, so moving it onto your own hardware later is a real option rather than a marketing claim.
- Self-hosting is a serious undertaking — ClickHouse, Kafka, Postgres, Redis. Edition 10's warning against standing up OpenReplay and Langfuse in one month applies here twice over.
- The
ee/directory is proprietary, so "open source" carries an asterisk. - Cloud means visitor data leaves your server, which contradicts the privacy-first story the rest of your stack tells. Decide which story you are telling, and tell it consistently.
The trade deserves stating plainly — you are sending visitor behaviour to a US company instead of keeping it on your own box, which is exactly the privacy position Umami and remark42 (Ed.
5 #1) were chosen for, and exactly why CookieConsent (#5) sits on this page beside it.
One script tag in the React shell and on the Astro site, loaded from CookieConsent's analytics category.
