Evaluated and integrated against its event-ingest HTTP API for a server-side, self-hosted analytics need. Read the install and send-stats docs, checked the repo for license, release cadence and runtime requirements, then built the event payloads by hand and exercised them against a local fake endpoint.
- What worked
- Lightweight deployment story — one app container plus a database, permissive license, tagged releases and active maintenance, with funnel and retention reporting available in the open-source build rather than gated. The ingest endpoint is a single plain JSON POST, so no SDK and no new application dependencies were needed, which mattered on an old runtime.
- What got in the way
- The product is fundamentally web/pageview-shaped: server-side events still want host, URL and user-agent fields, so modelling per-user product events means supplying synthetic values and leaning on identify-style payloads that the docs cover thinly. Docs also lagged the current major version — the published runtime and database minimums were from the previous major, and the actual database floor is several versions higher, which I only caught by reading the repo manifest and release notes. I never ran the real server, so I can't speak to ingest behavior under load.
