Epure
For self-hosters

Self-host Epure in two containers.

No event quota. Free under AGPL-3.0. Your Sentry SDK stays.

Self-host free

Free under AGPL-3.0. Rather not run a server? Cloud Pro is $29 a month.

The Epure project dashboard with sample data: open issues, the valve, and what needs triage.
Your server · sample data

Bottom line

Self-hosted Epure is free under AGPL-3.0. Two containers, Epure and Postgres 16, and no event quota. Idle was about 5 MiB plus 48 MiB on a small VPS, measured 23 Sep 2026.

Self-hosting Epure against self-hosting Sentry
DimensionEpureSelf-hosted Sentry
What you run2 containers28 services, errors-only profile
Quota on your hardwareNone. A flood is sampled and still counted.None
BackupOne pg_dump, plus the artifacts volumeThe whole stack
Your agentOne setting: EPURE_MCP_ENABLED=trueSentry's MCP server

Sentry: getsentry/self-hosted 26.10.1, checked 6 Nov 2026. GlitchTip, Bugsink and Telebugs are compared at /vs/self-host.

Updated · Epure v0.2.2 · Beta

Install it

Clone, pin the image, start. With no .env, Epure answers on localhost:8080.

git clone https://github.com/epure-sh/epure.git && cd epure
echo "EPURE_IMAGE=ghcr.io/epure-sh/epure:v0.2.2" >> .env
docker compose up -d

  1. 01Start the containers. Epure and Postgres 16 come up with Compose.

  2. 02Change the DSN. Point your Sentry SDK at your server. Restore the old DSN to undo.

  3. 03Read issues from the agent. Set EPURE_MCP_ENABLED=true, or run @epure-sh/mcp.

Screens show sample data.

What it needs

Two containers. No Redis, Kafka or ClickHouse. The idle reading is from 23 Sep 2026 and predates v0.2.0, so treat it as a floor.

Self-hosted Epure, measured
MeasureFigure
Containers2: Epure and Postgres 16
Idle RAMabout 5 MiB + 48 MiB
First issueabout 10 seconds from a warm compose
Event quotaNone

Idle reading: 2026-09-23, 2 vCPU / 769 MiB VPS. First issue: CHANGELOG v0.1.0.

The engine is AGPL-3.0. @epure-sh/cli and @epure-sh/mcp are Apache-2.0. Compare five self-hosted trackers.

Checked in the code

From the Epure v0.2.2 source and tests. Readings carry their date.

  • Epure + Postgres 16

    2

    Containers to self-host

  • 2026-09-23, 2 vCPU / 769 MiB VPS

    5 + 48 MiB

    Idle memory

  • self-hosted is never limited

    None

    Event quota

  • client packages Apache-2.0

    AGPL-3.0

    Engine licence

Skip self-hosting if

Nobody will own backups and upgrades
Cloud Pro is $29 a month.
You need SSO
Epure does not offer it.
You need tracing or replay
Epure tracks errors only.
You need mobile symbolication
Epure symbolicates JS and TS source maps only.

Self-hosting questions

Is self-hosted Epure free?
Yes. The engine is AGPL-3.0. The CLI and MCP packages are Apache-2.0. You pay for the server.
Is there an event limit when you self-host?
No. The spike valve still stores 100 events a minute per error and 150 per throw site, and counts the rest.
Which image tag should I pin?
The latest release with a published image: EPURE_IMAGE=ghcr.io/epure-sh/epure:v0.2.2. The changelog lists every tag.
Does the agent work on a self-hosted server?
Yes. Set EPURE_MCP_ENABLED=true, or run @epure-sh/mcp on the machine that has the editor.

Run it on your server.

Two containers, no event quota. Restore the old DSN to undo.

Install with Docker ComposeSelf-host free

Free under AGPL-3.0. Rather not run a server? Cloud Pro is $29 a month.