01
Apache 2.0 on GitHub
Telebugs includes source after checkout and forbids redistribute. Epure is Apache 2.0 from the first clone. No domain license, no Paddle receipt.
Epure vs Telebugs
Same DSN. Pay once or clone Apache 2.0.
Telebugs sells a polished one-container installer for $299. Epure is OSI open source: Rust plus Postgres, two containers, no license fee.
Both keep Sentry SDKs · $299 once vs Apache 2.0 · $0
Bottom line
Epure vs Telebugs, in one answer.
Pick Epure when you want Apache 2.0, PostgreSQL 16, keyboard triage, and a $24 Cloud path with zero overages. Pick Telebugs when you want to pay $299 once for a Rails+SQLite container, their CLI and email support, and no public Cloud.
- Best for Epure
- Apache 2.0, $0 self-host, Rust + Postgres, keyboard triage, Pro $24 (coming).
- Best for Telebugs
- $299 once per domain, one container, Rails + SQLite, CLI, founder email support.
Last reviewed
Self-host
$0
Apache 2.0 vs Telebugs $299 once per domain
Idle RAM
~82 MiB
Measured Epure stack vs Telebugs 1 GB documented minimum
Store
Postgres
PostgreSQL 16 + RLS vs SQLite in the Telebugs container
Cloud Pro
$24
Managed path · 200k · flat (coming)
Verdict
Same job. Different procurement.
Telebugs is a paid appliance. Epure is an OSI clone-and-run binary.
Pick Epure if
You want to run and fork without a license checkout.
- Apache 2.0 and a public GitHub tree matter.
- You already operate Postgres and want RLS in the tracker.
- You want keyboard triage and a spike valve.
- You may want managed Cloud at $24 later.
Pick Telebugs if
You want to pay once and get installer plus founder support.
- $299 once per domain is cheaper than thinking about compose.
- You want their CLI (update, backup, password reset) as the ops surface.
- SQLite in one Rails container is the store you want.
- You need a vendor email thread, not a GitHub issue.
Scoreboard
Where each product actually wins.
Telebugs wins pay-once simplicity. Epure wins OSI, Postgres, and a Cloud option.
| Dimension | Telebugs | Epure |
|---|---|---|
| License | Commercial · source after purchase | Apache 2.0 |
| Self-host price | $299 once / domain | $0 |
| Compose footprint | 1 container | 2 containers |
| Stack | Rails · SQLite | Rust · PostgreSQL 16 |
| SDK path | Sentry wire · swap DSN | Sentry wire · swap DSN |
| Scope | Errors (no replay / APM) | Exceptions only |
| Documented RAM floor | 1 GB / 1 CPU | ~82 MiB idle (measured) |
| Managed cloud | None (self-host only) | Pro $24 · Plus $79 (coming) |
Telebugs price, license, stack, and 1 GB minimum from telebugs.com (2026-09). Epure idle RAM measured 2026-09-12 on Docker Desktop. We do not claim 100% Sentry protocol parity.
Why switch
Clone it. Do not buy a seat at the gate.
Both drop the Sentry flotilla. One charges $299 to start. The other is a public repo.
02
Postgres, not SQLite-as-primary
Telebugs stores app data, cache, and jobs in SQLite inside one container. Epure uses PostgreSQL 16 with RLS. That is the store, not a sidecar experiment.
03
A Cloud path if you stop babysitting the box
Telebugs is self-host only. Epure Cloud is managed hosting of the same binary: Pro $24 for 200k events, zero overages, when it ships.
Year one
One invoice vs no license fee.
Telebugs is $299 plus the VPS. Epure is the VPS. Cloud is optional later.
Telebugs
Pay once · self-host only- License (1 domain)$299
- 1.x updatesincluded
- Event quota (vendor)none
- Typical VPS1 GB class
Software$299
Public Telebugs pricing 2026-09. Extra domains need extra licenses. Major versions may be a separate paid upgrade.
Epure
Apache 2.0 · Cloud optional- Self-host license$0
- Cloud Pro (optional)$24/mo · 200k
- Overages$0
- Typical VPS$4–6 class
Software (self-host)$0
Idle stack measured ~82 MiB (2026-09-12). Cloud is not live yet.
Switch
From Telebugs: same SDK, new DSN.
If Sentry SDKs already point at Telebugs, pointing them at Epure is the same move.
migrate-dsn.sh
Stay on Telebugs if
Paying once can be the right buy.
Telebugs is a finished appliance with a human on email. Name when that wins.
- 01
You want a vendor, not a repo
Kyrylo sells install, 1.x updates, and email support. If that is the procurement you already approved, keep it.
- 02
One container and a CLI are the ops surface
telebugs update, backup, password reset. Epure is compose plus Postgres backups. Different chores.
- 03
You do not want a public Cloud later
Telebugs has no hosted product. If self-host forever is the plan and $299 is fine, there is no Cloud pitch to ignore.
FAQ
Why not Telebugs?
Aren’t you the same thing?
We share the Sentry SDK wire and an errors-only scope. Telebugs is commercial Rails plus SQLite in one container for $299 per domain. Epure is Apache 2.0, Rust plus PostgreSQL 16, two containers, $0 to self-host.
Is Telebugs open source?
No. You get source after purchase to inspect and modify one licensed instance. You cannot redistribute it. Epure is Apache 2.0 on GitHub from the first clone.
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.
Isn’t one container better than two?
For install time, often yes. Telebugs wins that row. Epure keeps Postgres in its own container on purpose. If you want a single SQLite volume, stay on Telebugs.
How do RAM numbers compare?
Telebugs documents 1 GB RAM and 1 CPU as the minimum, and publishes ~50 fully processed reports per second on 2 vCPU / 4 GB. Epure idle stack measured ~82 MiB on 2026-09-12 (Docker Desktop). Those are different measurements. Read both before you size a box.
Does Epure have a pay-once plan?
No. Self-host is $0. Cloud, when it ships, is Pro $24 / Plus $79 per month with zero overages. If you only want a one-time check, Telebugs matches that shape.
Where do I compare Bugsink or GlitchTip?
See Epure vs Bugsink for the Shield plus SQLite-first Django container, Epure vs GlitchTip for MIT Django plus Redis, and Epure vs Sentry for the full platform.
Clone it. Skip the $299 gate.
Star Epure, compose up, point a DSN. Keep Telebugs if pay-once support wins.
Apache 2.0 · Rust + Postgres · Pro $24 flat