Epure
Epure vs GlitchTip

GlitchTip self hosted vs a smaller errors-only tracker

GlitchTip made Sentry-SDK self-hosting light. Epure is Rust + Postgres only, error tracking, keyboard triage. No session replay, APM, or profiling. Cloud Pro is $29/mo for 200k events.

GitHub

Both keep Sentry SDKs · Different compose · Apache 2.0 vs MIT

localhost:8080/p/checkout-web/issues
checkout-webproduction

Feed

Last seen7d
0 snoozed18.9k events
is:unresolvedSearch exceptions…
Bottom line

Epure vs GlitchTip, in one answer.

Both accept official Sentry SDKs and a DSN swap for exception ingest. GlitchTip is the established MIT Django + Celery + Redis path (about four compose services). Epure is Rust + PostgreSQL 16, two containers, no Redis default. Self-host is $0 on both if the license fits. Epure Cloud Pro is $29/mo for 200k events; Scale is $89/mo for 1.5M. Prefer GlitchTip when MIT or maturity wins.

Best for Epure
2 containers, no Redis, keyboard triage, Apache 2.0. Self-host is $0.
Best for GlitchTip
MIT license, established Django + Celery + Redis stack, years in production.

Last reviewed

Verdict

Two light Sentry-wire tools. Different bets.

GlitchTip is the established MIT Sentry-SDK host. Epure is the Rust plus Postgres path.

Pick Epure if

You want two containers and keyboard issue triage.

  • You refuse Redis/Celery in the error stack.
  • You want keyboard-first issue triage and spike soft-sample.
  • You want Cloud Pro at $29/mo for 200k events, flat.
  • You only need error tracking, not traces and replay.
GitHub

Pick GlitchTip if

You want the mature MIT project and Django ops you already know.

  • MIT license is a hard requirement for your counsel.
  • You’re happy with Django + Celery + Redis ops today.
  • You already run GlitchTip Cloud and the bill is fine.
  • You need features Epure has not shipped yet. Check their docs.
See GlitchTip
Scoreboard

Side-by-side where it matters.

Same SDK wire. Different containers, license, and product shape.

DimensionGlitchTipEpure
Compose footprint≈4 containers2 containers
StackDjango · Celery · Redis · PGRust · PostgreSQL 16
LicenseMITApache 2.0
SDK pathSentry wireSentry wire · swap DSN
ScopeErrors (+ extras)Error tracking
UI / triageFunctional Angular UIKeyboard-first issue list
Cloud entry~$15 plans · limitsPro $29 · 200k · flat
MaturityYears in productionFirst public cut

Competitor footprints from public docs. Maturity favors GlitchTip today. We say that out loud.

Why switch

Same DSN trick. Different ops and triage bet.

The SDK wire is table stakes. The stack, triage, and Cloud price are the split.

01

Two boxes, no Redis

GlitchTip’s light stack still pulls workers and Redis. Epure embeds the queue in the Rust process and stores in Postgres with RLS.

02

Triage that respects time

Keyboard-first issue navigation: j/k, resolve, ignore, search. Built for daily crash fixing.

03

Cloud without surprise meters

Cloud Pro is $29/mo, Scale is $89/mo, soft-sample on spikes, no overage invoice. Self-host stays $0.

Self-host + Cloud

Both are cheap. The shape differs.

Self-host is free on both. Cloud is where the product bet shows up.

GlitchTip

OSS + Cloud
  • Self-host licenseMIT · $0
  • Typical VPS$5–10 class
  • Cloud entry~$15
  • Stack opsDjango + Redis
ShapeLight+

Figures from public GlitchTip docs and pricing pages.

Epure

OSS + Cloud
  • Self-host licenseApache 2.0 · $0
  • Typical VPS$4–6 class
  • Cloud Pro$29 · 200k flat
  • Stack opsRust + Postgres
ShapeMinimal

Hardware-bound volume on self-host. Cloud Pro is $29/mo for 200k events.

Switch

From GlitchTip: same SDK, new DSN.

If you already point Sentry SDKs at GlitchTip, pointing them at Epure is the same move. Runbook: [Migrate from GlitchTip](/guides/migrate-glitchtip).

migrate-dsn.sh
Full install checklist
Stay on GlitchTip if

Maturity still counts.

GlitchTip has years of production hours. That is a real advantage.

  1. 01

    MIT is non-negotiable

    Epure is Apache 2.0. If counsel requires MIT specifically, GlitchTip wins that row.

  2. 02

    You already operate Django well

    If Celery and Redis are normal for your team, GlitchTip’s ops model is familiar. Switching for two containers alone may not pay.

  3. 03

    You need battle-tested today

    Epure just shipped its first public cut. Prefer GlitchTip when you cannot tolerate early-product edges.

FAQ

Why not GlitchTip?

Aren’t you the same thing?
We share one adoption trick: the Sentry SDK wire. The stacks differ, Rust plus Postgres against Django plus Redis, and so does the UI bet.
Is Apache 2.0 worse than MIT?
Different OSI licenses. MIT is simpler; Apache 2.0 adds patent grants. Pick what your counsel accepts. We do not pretend they are identical.
Can I migrate without rewriting instrumentation?
Yes. Keep official Sentry SDKs. Change the DSN. We publish a compatibility matrix and do not claim 100% protocol parity.
How do the compose footprints compare?
GlitchTip typically runs app, worker, Redis, and Postgres. Epure runs two containers: Rust binary plus PostgreSQL 16. Idle RSS receipts are dated rows on Sentry self-hosted RAM.
Does Epure need Redis?
No. The ingest queue lives in the Rust process. Postgres holds issues and events. Redis and Celery are not part of the OSS compose.
What about Cloud pricing?
GlitchTip publishes entry plans around $15. Epure Cloud Pro is $29/mo for 200k events; Scale is $89/mo for 1.5M, flat. Self-host stays $0 on both. Pricing.
Where do I compare Sentry, Bugsink, or Telebugs?
See Epure vs Sentry for the full platform, Epure vs Bugsink for Shield plus SQLite, and Epure vs Telebugs for pay-once Rails.
Also compare

More head-to-heads.

Same template. Different job.

Try the two-container path.

Star Epure, compose up, point a DSN. Keep GlitchTip if maturity wins.

GitHub

Keep Sentry SDK · swap DSN · Apache 2.0