Documentation
Install Epure, point a Sentry SDK at your DSN, and triage the first issue on epure.sh docs.
Exception monitoring you run: one Rust binary, PostgreSQL 16, two Compose containers. Keep the official Sentry SDK for your runtime; change only dsn. First issue: Quickstart. Not sure Browser vs Node vs Django? Pick your SDK.
What is Epure?
Exception-only error tracking on hardware you control. Envelope and store ingest, JS/TS sourcemaps, and keyboard triage.
Send the first exception
After the first issue
Operators and API
FAQ
Do I install an Epure SDK?
No, there is no @epure/* package. Point an official Sentry SDK at your instance and change only dsn. Pick the package by framework: Pick your SDK. CI fixtures cover @sentry/browser and @sentry/node 7.120.0.
What is in self-host vs Cloud?
Self-host is this OSS binary: Rust, PostgreSQL 16, two Compose containers. Ingest is envelope plus store, with JS/TS sourcemaps, Issues triage, and a spike valve. Cloud comes later at Pro $24/mo and Plus $79/mo. See Welcome.
Does Epure support tracing, replay, or iOS?
No. Exception events, breadcrumbs, JS/TS sourcemaps, and the spike valve ship now. Transaction, replay, and profile items are discarded on ingest. Native iOS and Android crash reporting is out of scope: Java (JVM only) and Other runtimes.
How do I get my first issue?
Start the two containers (cp .env.example .env if you need another port). Register, name a project, copy the DSN from setup or Settings → SDK connection. Call Sentry.init with that dsn, then captureException. Ingest returns 202 before the Issues row appears. Full walkthrough: Quickstart.
What does HTTP 202 mean on ingest?
202 Accepted means the DSN and body passed the gate. Persist and JS/TS demangle run on a Tokio queue after the response. A 202 can still yield an empty Issues list when the environment filter is wrong. See Verify.
Is a DSN the same as a session cookie?
No. The DSN authenticates ingest (/envelope/, /store/, release files, user feedback). Issues, Events, and other /api/v1/* routes need a login cookie. DSN headers on dashboard APIs return 401. Full table: Authentication.
What is the 2 MB cap and the spike valve?
Ingest bodies over 2 MB return 413 payload_too_large. The spike valve is about 100 raw events per minute per fingerprint; saturated fingerprints still get 202 and a counter bump. The hourly project cap (default 5000) returns 403. See API errors.