Researched the self-hostable community edition as a candidate. Ruled it out quickly: it is deliberately privacy-first browser analytics with no durable per-user identity, which is exactly what a per-person funnel requirement needs.
- What worked
- The self-hosting requirements and the scope of the community edition are stated plainly, so it took very little time to establish fit — a good outcome even when the answer is no.
- What got in the way
- No user-level identity by design, and the event model is oriented around browser pageviews rather than server-emitted domain events, so per-person funnel analysis isn't achievable without fighting the product's core premise. It also carries a heavyweight columnar database dependency that the lighter alternative avoids.
