Open Source Error Tracking

Sentry, minus the infrastructure

One Go binary. 29 MB. Drop it on a $5 VPS and point your existing Sentry SDKs at it. Error tracking, performance monitoring, session replay, profiling — all yours, on your hardware.

Deploy in 60 seconds
Dashboard — Error Tracking Overview

29 MB

Single binary. That's it.

183

MB/s ingest on a laptop

128

Sentry API endpoints mapped

$5

VPS. All you need.

01

Your Sentry SDKs already work

Swap the DSN. That's the migration. Urgentry speaks the Sentry protocol — 37 endpoints matched today, 128 mapped. Your JavaScript, Python, Go, and Ruby SDKs connect without changes.

SDK Compatibility Diagram
02

SQLite for small. Postgres for big.

Running on your laptop or a single server? SQLite mode keeps things simple — zero config, zero dependencies. When traffic grows, switch to Postgres. Same binary, different flag.

Architecture Diagram
03

Everything you actually use

Error tracking. Performance monitoring. Session replay. Profiling. Cron monitors. Custom metrics. Built from the Sentry features developers rely on — not the enterprise upsell ones.

Feature Overview Screenshot
04

183 MB/s on a laptop

Go is fast. SQLite is fast. We didn't add abstractions that slow things down. Ingest throughput that makes dedicated infrastructure look wasteful.

Performance Benchmark Chart
"Your error data contains your stack traces, your user sessions, your application's nervous system. It should live on servers you control."

The Urgentry Manifesto

Works with what you have

Urgentry supports the Sentry SDK ecosystem. Pick your language, point the DSN, ship.

JavaScript / Node
Python
Go
Ruby
PHP
Java / Kotlin
Rust
.NET / C#

Stop renting your error data

Download the binary. Run it. Point your SDKs. Done before your coffee gets cold.

View on GitHub
curl -fsSL https://urgentry.dev/install | sh