Sentry-compatible error tracking that ships as a 29MB binary. Point your existing SDKs at it. Done.
urgentry vs Sentry self-hosted. Same SDKs, different resource bill.
| urgentry | Sentry Self-Hosted | |
|---|---|---|
| Binary / Image Size | 29 MB | ~3 GB (Docker images) |
| Setup Time | < 30 seconds | 15-45 minutes |
| Idle Memory | ~50 MB | ~2.5 GB (9+ containers) |
| Dependencies | None (SQLite built in) | Docker, Compose, Kafka, Redis, Postgres, Clickhouse, etc. |
| Minimum Server | $5/mo VPS | $40+/mo (4GB+ RAM required) |
| API Endpoints | 128 mapped, 37 matched | Full API |
Error tracking, performance, sessions, profiling, crons, and metrics. All in one binary.
Stack traces, breadcrumbs, context. Your Sentry SDK sends events here instead. Nothing to rewrite.
Transactions and spans. Track what's slow without shipping your data to someone else's cloud.
See what your users saw before the crash. Stored locally. No third-party replay vendor needed.
CPU profiles attached to transactions. Find the function that's burning your budget.
Know when your scheduled jobs don't run. Check-in API compatible with Sentry's cron monitoring.
Counters, distributions, gauges, sets. Ship metrics alongside errors in the same pipeline.
Download the binary. Start it. Point your DSN. That's the whole migration plan.