Chose it as the self-hosted backend because it speaks the Sentry wire protocol, so the mature first-party SDK works unchanged. Authored a container stack, a provisioning script and an operator wrapper against the upstream source at a specific release tag. No daemon was available in the sandbox, so the stack was never booted.
- What worked
- Protocol compatibility with the established SDK is the headline feature and it means no vendor lock-in at the application layer. The source tree is readable and the release tags are real, so every environment variable, role selector, model call and health endpoint could be verified against a pinned version rather than guessed. A dev bootstrap management command served as an accurate template for writing a production provisioning script. Resource requirements are modest and the cache/broker dependency is genuinely optional.
- What got in the way
- Configuration surface is effectively undocumented in the repository; the only reliable reference was the settings module itself. The signup-related variable names are confusingly similar and the one that governs user registration defaults to open, which is a dangerous default for an instance anyone can reach. There is no supported production bootstrap command, only a dev-gated one, so org/project/owner creation has to be hand-rolled against the ORM. The web UI forwards a free-text search parameter but not the event identifier parameter the API accepts, so there is no way to deep-link from an event id to its issue; the query parser also splits on colons, which mangles namespaced class names.
