Open source · Apache 2.0

Your data.
Same Sentry SDKs.

Q: How do I install Epure?

Clone the repo, docker compose up. No .env required. If 8080 is taken, cp .env.example .env and set EPURE_PORT. Register, copy a DSN. Default dashboard is localhost:8080. Production: ./configure --prod or deploy/env.production.example plus the compose overlay. Coolify: Deploy on Coolify. Other panels: one-click deploy and Self-host § Deploy. Full walkthrough: self-hosting installation.

Q: What ops do I still own?

The box, TLS in front of the app port (default 8080; EPURE_PORT in .env), Postgres backups, disk during a spike, and version upgrades. Cloud Pro at $29/mo is managed hosting of the same path: see pricing.

Apache 2.0 open core for teams that need Postgres on their metal: production exceptions, Spike Valve, and MCP triage without a metered SaaS inbox.

GitHub

Two-container Compose · Unlimited seats · Optional Cloud when you want managed

localhost:8080/p/checkout-web/issues

checkout-webproductionSearch…⌘K

Feed

Last seen7d

0 snoozed18.9k events

is:unresolvedSearch exceptions…

IssueLast seen30dEvents

Why install

Self-host when compliance or sovereignty is the requirement.

Run the same product path as Cloud on infrastructure you control, without shipping client stack traces to a third-party observability suite.

Errors stay on your disk
Dedicated VPC, on-prem, or regulated workloads. PostgreSQL 16 with RLS is yours to audit and back up.
Small compose, not a fleet
Ingest, API, and UI in one process plus Postgres. No Redis. No Kafka.
Same SDKs you already ship
Official Sentry clients. Change the DSN. Land the first issue without a rewrite.

Install tonight

Compose up. Point the DSN. Open the list.

Docker Compose v2. Optional `.env` for the host port. Compose pulls ghcr.io/epure-sh/epure. Default is localhost:8080 with real issues.

Clone and compose up
One command. Optional .env for the host port. Migrations on boot. Health answers ok.
Create a project DSN
Register, name a project, copy the key from setup or Settings → SDK connection.
ResolveIgnoreSnooze
Land the first issue
Same Sentry SDK. New host. Confirm 202 in the list.

Full install checklist One-click deploy Render · Railway · Coolify · Dokploy

Render
Sync render.yaml from GitHub. Private Postgres + public Epure image.
Deploy to Render
Railway
Drag deploy/railway/docker-compose.yml onto a new project canvas.
Open compose file
Coolify
Docker Compose build pack → base dir deploy/templates/coolify.
Coolify guide
Dokploy
Compose path deploy/templates/dokploy/docker-compose.yml from Git.
Dokploy compose

Panels & PaaS

Import from GitHub. Same compose path.

No marketplace export required. Templates live in the public repo. Production passwords and HTTPS session cookies match the VPS overlay. Walkthrough on the one-click deploy guide and installation docs.

Deploy to Render Docs checklist

What you run

A free open source error tracking tool.

Apache 2.0. Same product path as Cloud. Exceptions and grouped issues, not traces and replay.

Sub-10ms ingest + spike valve
202 fast. Duplicate storms don’t melt the box or hide the count.
Grouping + JS/TS sourcemaps
Readable stacks. One crash, one issue you can resolve once.
Keyboard triage
j/k through the list. Resolve, ignore, snooze without fighting the mouse.
Webhooks + releases
Ping Slack or your bot. Tie issues to the deploy that shipped them.
RLS multi-tenant Postgres
Org isolation in the database. Monthly partitions. TTL for old events.
No EE trap on triage
Core ingest and issue UI ship in OSS. Cloud is managed hosting, not a locked fork.

Footprint

Open source error tracking vs the stacks you tried.

If Sentry self-host OOMed your VPS, start here.

Dimension	Sentry self-host	GlitchTip	Epure
Compose footprint	20+ containers	≈4 containers	App + Postgres
Typical RAM floor	16–32 GB class	Modest VPS	Small VPS / laptop
License	BSL / cloud-shaped	MIT	Apache 2.0
SDK path	Native	Sentry wire	Sentry wire · swap DSN
Scope	Errors + APM + replay + …	Errors (+ extras)	Exceptions · grouped issues
Self-host price	Your infra + ops time	Free OSS	Free · hardware-bound

Competitor footprints from public docs. We don’t claim 100% Sentry protocol parity.

Ops honesty

You own the box. We keep the stack small.

Backups, upgrades, disk during a spike, TLS in front of the app port (default 8080). That work is yours. Two containers means it stays doable for a solo founder on a Friday night.

Prefer managed Postgres and backups? Cloud Pro is $29/mo flat. Install free either way.

FAQ

Before you paste the clone.

Is self-hosted really free?

Yes. Apache 2.0, full core: ingest, grouping, issue UI, spike valve, JS/TS sourcemaps, keyboard triage, webhooks. You pay the VPS. No seat lock. Cloud prices live on pricing.

How do I install Epure?

Clone the repo, docker compose up. No .env required. If 8080 is taken, cp .env.example .env and set EPURE_PORT. Register, copy a DSN. Default dashboard is localhost:8080. Production: ./configure --prod or deploy/env.production.example plus the compose overlay. Coolify: Deploy on Coolify. Other panels: one-click deploy and Self-host § Deploy. Full walkthrough: self-hosting installation.

Will this run on a small VPS?

That is the design: one app process plus Postgres. Idle stack measured ~82 MiB on 2026-09-12 (Docker Desktop). Size the disk for event growth.

How does this compare to Sentry self-host?

Sentry self-host publishes a 20+ container stack in the 16-32 GB class. Epure is two containers of error tracking, Apache 2.0. Keep official Sentry SDKs and swap the DSN. Receipts: Sentry self-hosted RAM. Details: Epure vs Sentry.

What ops do I still own?

The box, TLS in front of the app port (default 8080; EPURE_PORT in .env), Postgres backups, disk during a spike, and version upgrades. Cloud Pro at $29/mo is managed hosting of the same path: see pricing.

Do I change my Sentry SDK?

No. Keep @sentry/browser, @sentry/node, sentry-python, and the rest. Repoint the DSN. Short path: Migrate from Sentry. Pick your package on integrations. We do not claim full protocol parity.

Why not GlitchTip?

Same SDK wire path. Epure tracks exceptions on Rust plus Postgres with no Redis, and prices Cloud Pro at $29/mo with no auto-overage invoice. GlitchTip is MIT Django plus workers. Read Epure vs GlitchTip if that stack is already home.

Why not Bugsink or Telebugs?

Both keep Sentry SDKs and skip the 20-container flotilla. Bugsink is one Django container under Polyform Shield with SQLite first. Telebugs is $299 once, Rails plus SQLite, no public Cloud. Epure is Apache 2.0 and Postgres by default. Row by row: Epure vs Bugsink, Epure vs Telebugs.

Can I deploy on Render or Railway instead of a VPS?

Yes. Import from GitHub: Deploy to Render, Railway compose drag-and-drop, or Coolify/Dokploy compose paths. Details: one-click deploy, installation § PaaS, Self-host § Deploy.

Will you cripple the OSS build?

The self-hosted binary is the full product. Cloud is managed hosting of that path, not an EE fork of triage. What shipped is on the changelog.

Star the open source error tracking tool.

Join Cloud waitlist or clone the repo and run Compose on your box.

GitHub

Apache 2.0 · docker compose up