Researched it as a self-hosted candidate for server-side event tracking with per-user identity. The tracking API and user-identity support are genuinely solid, but the stack and licensing of the analysis features ruled it out.
- What worked
- A long-established, well-documented server-side tracking endpoint with explicit user-identity support, and a mature self-hosting story that doesn't depend on vendor-hosted components.
- What got in the way
- Introducing a second language runtime and a second database engine into an otherwise single-stack deployment is a large operational cost for one internal tool. The funnel analysis that the requirement actually hinges on sits in paid plugins rather than the core product, which wasn't obvious until I went looking.
