Epure
Documentation

Documentation

Error tracking for exceptions: grouped issues, stack traces, breadcrumbs. Self-host is one Rust binary, PostgreSQL 16, two Docker Compose containers. Cloud is the same binary, hosted. Keep the official Sentry SDK for your runtime; change only dsn. Land the first issue with the Quickstart. Not sure Browser vs Node vs Django? Pick your SDK.

Start here

New to EpureWelcome → Quickstart → first issueFrom Sentry60-second DSN swap, then this checklistHow-tosDSN swap, Coolify, migrate pathsSelf-host opsProduction checklist, config, upgradesAPI & agentsIngest, MCP, epure-cli, PAT

What is Epure?

Grouped exceptions on hardware you control, or on Epure Cloud. Envelope and store ingest, JS/TS sourcemaps, and keyboard triage.

Issues feed showing unresolved exceptions with counts and status

Send the first exception

QuickstartCompose (if needed), copy a DSN, captureException, open IssuesInstallClone, optional `.env` for ports, two containers, GET /healthOne-click deployRender, Railway, Coolify, Dokploy — templates in the GitHub repoWelcomeWhat ships and three paths in

After the first issue

Triage issuesQuery tokens, keyboard, merge and splitAlertsVelocity, regressions, ingest cap railPick your SDKReact, Next, Express, Django: which packageInstrument JSBrowser and Node shared DSN optionsUpload source mapsDemangle minified JS/TS stacks for a releaseManage projectsDSN keys, retention, ingest caps

Operators and API

ConfigurationEnv vars, CORS origins, session cookiesTroubleshooting403s, CORS failures, empty Issues listIngest APIEnvelope, store, Issues, EventsMCP and epure-cliPAT, stdio MCP, CLI commandsFAQ indexCommon questions in one pageDocs changelogTagged binary + docs notes; narrative at /changelog

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. Managed hosting of the same path is Epure Cloud (plans and pricing live there, not in the self-host guides).

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 (docker compose up; copy .env.example only 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.

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. Agent automation uses a separate PAT on `/api/v1/agent/*`. DSN headers on dashboard APIs return **401**. Full table: [Authentication](/docs/api/authentication).
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](/docs/get-started/verify).
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](/docs/api/errors).

How-tos

Next Page

On this page

What is Epure?