Drop-in Sentry replacement

400 eps in 52.3 MB. Sentry needs 8 GB.

Keep the Sentry SDKs. Change the DSN.

In the current same-host benchmark lane, Tiny sustained 400 eps at 52.3 MB peak memory, and urgentry self-hosted sustained 2,200 eps. Against the current Sentry self-hosted reference row, urgentry delivered 2.2x higher throughput, 21x lower peak memory, and 29x faster query p95. Read the benchmark method and artifacts before you quote the headline.

$ curl -fsSL https://urgentry.com/install.sh | sh
urgentry vs sentry LIVE
Throughput 2.2× more
urgentry
2,200 eps
Sentry
1,000 eps
Peak memory 21× less
urgentry
392 MB
Sentry
8192 MB
Query latency p95 29× faster
urgentry
49 ms
Sentry
1401 ms
Tiny mode
400 eps
Same-host throughput
52.3 MB
Peak memory
Self-hosted mode
2,200 eps
Release lane throughput
391.8 MB
Peak memory

Everything you actually use in Sentry

Issues, replay, profiles, Discover, alerts, and traces. Start small.
Grow when your own traffic forces the move.

Error tracking

Stack traces, breadcrumbs, tags, user context, release tracking, grouping, and the triage flow teams already know.

Performance

Distributed traces and transaction timing. Track the slow path before it becomes the support queue.

Session replay

DOM snapshots, user actions, console context, and issue-linked replay without another product in the middle.

Profiling

Profiles, flamegraphs, and hot-path analysis tied back to the same releases and traces.

Cron monitors

Detect silent jobs and missing check-ins with the Sentry-compatible cron monitoring path.

Discover and logs

Query issues, events, transactions, and logs in one place instead of stitching together a heavier stack.

Switch from Sentry without re-instrumenting

You do not need to rewrite your app. Change the DSN, redeploy, and validate the workflow your team already uses.

  1. Install urgentry

    Start with the binary install and verify the version you pulled.

    curl -fsSL https://urgentry.com/install.sh | sh
  2. Start the server

    Tiny mode gets you to a working DSN fast.

    urgentry serve
  3. Update the DSN

    Point the existing Sentry SDK at urgentry and keep the rest of the instrumentation intact.

    dsn: "http://key@your-server:8080/1"
  4. Move traffic

    Validate the common path, then push production traffic when the proof is good enough.

// sentry config

Sentry.init({
  dsn: "https://key@o123.ingest.sentry.io/456",
  dsn: "http://key@your-server:8080/1",

  // everything else stays the same
  tracesSampleRate: 1.0,
  replaysSessionSampleRate: 0.1,
  profilesSampleRate: 1.0,
});
Source-available

Own the product.
Own the data.
Skip the stack tax.

urgentry is source-available and self-hosted. You get the product in your infrastructure, a live public repo, real releases, support docs, security reporting, and benchmark proof before you commit.

1 binary
Tiny mode start
218/218
common-path routes
2,200
self-hosted eps
391.8 MB
Self-hosted peak memory