Why urgentry exists

Error tracking should not require 23 containers, 16 GB of RAM, and a dedicated DevOps team. Most teams that self-host Sentry spend more time maintaining the infrastructure than fixing the bugs it reports.

Maintained by Wraxle LLC
Last updated

urgentry is a clean-room implementation of the Sentry API in a single Go binary. It matches 218 out of 218 OpenAPI routes, works with every existing Sentry SDK, and runs on SQLite for development or Postgres for production.

The goal is simple: make self-hosted error tracking as easy to run as the application it monitors.

Stewardship

  • Maintained by Wraxle LLC. The public repo, public docs, and release tags are the primary evidence trail for what urgentry claims.
  • Public proof over vague promises. Migration, benchmark, support, and security pages are published together so operators can check the product story against the repo and docs.
  • Private security lane. Bugs and feature requests stay public, but vulnerabilities use the private reporting path documented on the security page and mirrored at /.well-known/security.txt.

Principles

  • Single binary. One download, one process, no runtime dependencies.
  • SDK compatible. Drop-in replacement. Point your existing SDKs and everything works.
  • Two modes. SQLite for simplicity, Postgres for scale. Same binary.
  • Source-available. FSL-1.1-ALv2. Your data, your infrastructure, your rules.
  • Clean room. No copied code. Built from public API specifications and black-box behavior.

Source Availability

urgentry is source-available under FSL-1.1-ALv2.
Contributions, bug reports, and feature requests are welcome.