Two-container error tracking footprint
Epure runs two Compose services: app + PostgreSQL 16. Compare that shape to Sentry self-host, GlitchTip, and one-container peers.
On this pageShowHide
Topology
Internet, then a TLS edge, then the Epure app, then PostgreSQL 16.
Footprint scoreboard
Sentry self-hosted
- Shape
- 20+ containers, Kafka in the default path
GlitchTip
- Shape
- about 4 (app, worker, Redis, Postgres)
Bugsink
- Shape
- 1 container possible (SQLite default)
Telebugs
- Shape
- 1 container (Rails + SQLite)
Epure
- Shape
- 2 (app + PostgreSQL 16)
| Dimension | Shape |
|---|---|
| Sentry self-hosted | 20+ containers, Kafka in the default path |
| GlitchTip | about 4 (app, worker, Redis, Postgres) |
| Bugsink | 1 container possible (SQLite default) |
| Telebugs | 1 container (Rails + SQLite) |
| Epure | 2 (app + PostgreSQL 16) |
One-container peers win install minimalism. Epure wins Postgres-default plus Apache 2.0. Details on the compare pages.
What is absent on purpose
- Redis or Celery as required dependencies.
- Kafka or ClickHouse as required dependencies.
- Session replay, APM, and continuous profiling as Epure features.
How to reproduce
- Installation and Compose prod.
docker compose psshows two healthy services.- Optional:
docker stats, then record a dated row on Sentry self-hosted RAM.
Questions
Is two always better than one?
No. If you want SQLite in one process, Bugsink or Telebugs may fit better. vs Bugsink. vs GlitchTip.
Where are RAM numbers?
How partial is SDK compat?
Keep the Sentry SDK and change the DSN for exceptions. Not 100% protocol parity.