01
Small compose, not a fleet
Ingest, API, and UI in one process plus PostgreSQL 16 with RLS. No Redis. No Kafka. Self-host stays simple.
Epure vs Sentry
Exception tracking without metered bill shock
Sentry bundles APM, replay, and profiling on a per-event meter. Epure stays crash-first: official Sentry SDKs, Spike Valve, flat Cloud Pro at $29/mo for 200k full-payload events.
Keep @sentry/* · Swap DSN · Apache 2.0
localhost:8080/p/checkout-web/issues
checkout-webproduction
Feed
Last seen7d
0 snoozed18.9k events
is:unresolvedSearch exceptions…
IssueLast seen30dEvents
Bottom line
Epure vs Sentry, in one answer.
Epure is error tracking on two Compose containers (Rust app + PostgreSQL 16). If you only need grouped exceptions, you can run a much smaller tracker. Keep official Sentry SDKs. Change the DSN. Partial wire (envelope + store). No session replay, APM, or profiling. Self-host is $0. Cloud Pro is $29/mo for 200k full-payload events.
- Best for Epure
- Error tracking, Sentry SDK DSN swap, two Compose containers, Apache 2.0 self-host at $0.
- Best for Sentry
- Replay, APM, profiling, Seer, and enterprise packs on one invoice.
Last reviewed
Verdict
Pick the tool that matches the job.
Sentry wins breadth. Epure wins when you only need grouped production errors.
Pick Epure if
You want crashes fixed without paying for replay and traces.
- You already ship Sentry SDKs and only need a new DSN.
- You want predictable ingestion when retry loops spike production.
- You refuse Kafka and Redis for this job.
- Keyboard issue list. j/k, resolve, ignore.
Pick Sentry if
You need the full platform and will pay for it.
- Session replay, profiling, and distributed tracing are daily tools.
- You want Seer / AI grouping and deep GitHub PR comments.
- Ops can run (or buy) a large self-host or SaaS footprint.
- Enterprise compliance packs and SSO are non-negotiable today.
Scoreboard
Where each product actually wins.
Eight rows. We lose some on purpose. Tables that never lose read as ads.
| Dimension | Sentry | Epure |
|---|---|---|
| Primary job | Errors + APM + replay + … | Error tracking |
| Self-host footprint | 20+ containers · large box | 2 containers · app + PG 16 |
| SDK path | Native | Official SDKs · swap DSN |
| Session replay | Yes (metered) | Out of scope |
| APM / tracing | Yes (metered) | Out of scope |
| Cloud entry (paid) | Team ~$26 · 50k errors | Pro $29 · 200k · flat |
| Overages | Pay-as-you-go meters | No SaaS overage invoice · soft-sample on flood |
| License (self-host) | FSL / cloud-shaped | Apache 2.0 |
Competitor figures from public docs and pricing. We do not claim 100% Sentry protocol parity. Envelope + store for error tracking.
Why switch
Crash capture without the observability tax.
You want grouped production exceptions and invoices you can forecast. You don’t want to pay for replay and traces your team never opens.
02
Invoice without meters
Sentry Team starts at about $26 for 50k errors, then PAYG. Self-host Epure is $0 software. Cloud Pro is $29/mo for 200k flat with tiered soft-sample on spikes.
03
Same SDKs you already ship
Official Sentry clients. Change the DSN. We publish a matrix; we never claim full protocol parity.
At 200k errors
Same volume. Different invoice shape.
Sentry Team includes 50k errors. Past that you pay per error. Epure Pro is $29/mo for 200k, flat.
Sentry Team
Annual default · errors only- Team base (50k errors)$26
- Extra 150k errors (PAYG)~$40
- Replay / spans / profilingmeters
- Seats on Teamsee Sentry plan
Rough total~$66+
Team seat rules per Sentry pricing page. PAYG estimate from published Team rates for 50k–200k.
Epure Pro
Cloud Pro · 200k flat- Pro flat (200k errors)$29
- SaaS overage invoice$0
- Seats & projectsno seat meter on Pro*
- Flood behaviorsoft-sample (spike valve)
Invoice$29
Self-host stays $0 software; you own backups, upgrades, TLS. Cloud Pro is $29/mo for 200k. Tiered soft-sample caps fingerprint floods instead of a surprise invoice.
Switch
Compose up. Point the DSN. Open the list.
Same instrumentation, new destination. No proprietary SDK.
migrate-dsn.sh
When Sentry wins
Keep Sentry when breadth is the job.
Epure is not a Sentry killer. Name when the other product is the right call.
- 01
Session replay
If you debug production by watching sessions, keep Sentry. We will not fake replay.
- 02
APM and distributed tracing
Transaction and span product surfaces are out of scope. Epure discards those items on ingest.
- 03
Continuous profiling
Profiling packs stay with Sentry (or a dedicated profiler). Exception stacks are the Epure job.
- 04
Enterprise breadth
SSO tomorrow, Seer / AI grouping, deep PR comments, compliance packs: buy Sentry if procurement already closed.
- 05
You want 100% protocol parity
We implement envelope + store and publish a matrix. We never claim full Sentry protocol parity.
FAQ
Questions teams ask before swapping the DSN.
Can I keep the Sentry SDK and only change the DSN?
Keep the official Sentry SDK and change the DSN for exception ingest and issue triage. We do not claim 100% protocol parity. Transactions, replay, profiling, and mobile are not supported. Start: quickstart.
How do the costs compare?
Sentry SaaS meters volume and extras. Sampling reduces signal when production breaks. Self-host Epure is $0 on two containers; you own backups, upgrades, and maintain. Cloud Pro is $29/mo for 200k. Self-host. Pricing. Sentry cost calculator.
Will self-hosting Sentry be cheaper?
Hardware looks free until you count RAM, disk, and the engineer keeping 20+ containers alive. Epure is app + PostgreSQL 16 only. RAM receipts: Sentry self-hosted RAM.
Do I keep my Sentry SDK?
Yes. Leave @sentry/browser, @sentry/node, sentry-python, and the rest in place. Paste the Epure DSN. Set traces, replay, and profile sample rates to 0 so you stop shipping volume Epure discards. What a DSN swap covers, and what it does not: Change the DSN, keep the Sentry SDK. Map: platforms.
What do I lose if I switch?
Session replay, distributed tracing, continuous profiling, Seer, and mobile symbolication. Epure covers exceptions, JS/TS sourcemaps, and keyboard triage. If those Sentry products are daily tools, stay.
What about GlitchTip, Bugsink, or Telebugs?
Same SDK wire idea, different stacks. Epure vs GlitchTip for MIT Django plus Redis. Epure vs Bugsink for Shield plus SQLite. Epure vs Telebugs for the $299 Rails container. DSN swap: Guides.
Swap the DSN. Keep the SDK.
Star the repo, then open self-host docs when you want errors on your box.
Keep Sentry SDK · swap DSN · Apache 2.0