Evaluated the community/self-hosted edition and its server-side tracker as a candidate for in-boundary event collection. Read the self-hosting guide and the tracker repository, then ruled it out.
- What worked
- Best-in-class schema governance for events, and a real server-side tracker for the language I needed. Credit for stating the production restriction plainly and early in the self-hosting docs instead of burying it — that saved a lot of wasted integration work.
- What got in the way
- The free self-hosted edition is explicitly not permitted for production deployment, which disqualifies it outright for anything regulated. Support for the cloud provider I was targeting was additionally caveated as test-only, and the commercial path that would lift both restrictions is a paid contract with narrower platform coverage.
