Epure
GitHub
Changelog · Apache 2.0

What we ship. What comes next.

Phase 1 exception tracking in one launch cut. Keep your Sentry SDK. Swap the DSN. Star the repo when you want the source.

Star on GitHubSee docs

v0.1.0-phase1 · 2026-09-15 · two containers

  • Measured

    ~82 MiB

    Idle stack RAM

  • Measured

    18.1 MiB

    Release binary

  • Stack

    2

    Containers

  • Warm path

    0.18 s

    Ingest → UI

v0.1.0-phase1 · 2026-09-15

In the binary today.

One launch cut. Exception-only. Longer notes live in the docs changelog.

  • Ingest + spike valve

    Envelope and store paths. 202 responses. Caps stop a runaway fingerprint from melting the box.

  • Sourcemaps + grouping

    JS/TS demangle. SHA-256 fingerprints. Breadcrumbs. PII scrub at ingest.

  • Postgres 16 + RLS

    Org isolation in the database. Monthly partitions. TTL drop for old events.

  • Keyboard triage

    j/k/e/i/x. Query syntax. Merge/split. Bulk resolve. Markdown export for LLMs.

  • Lifecycle signals

    Regression, snooze, velocity alerts. Slack / Discord / generic webhooks.

  • Admin + RBAC

    Multi-project orgs. DSN rotate/revoke. Owner / Admin / Member.

Full changelog in docs

Roadmap

Self-host live. Public next. Cloud after.

Exception tracking only. You can see what shipped, what is next, and what we refuse to build.

  1. GRND

    Self-host

    Live

    Open source error tracking on your box. Two containers. Full Phase 1 core.

    • Spike valve + sourcemaps + RLS
    • Keyboard triage + webhooks
    • Apache 2.0 · clone and run
  2. OPEN

    Public launch

    Next

    Ship the public repo, honest docs, and a Show HN when the paint is dry.

    • Public GitHub publish
    • Migration + compatibility guides
    • Dashboard polish before launch
  3. CLD

    Cloud

    Queued

    Same binary, our ops. Pro $24 / Plus $79 flat. Soft-sample on spike. No surprise invoice.

    • Managed Postgres + TLS
    • Stripe checkout → first event
    • Count 100% · store 10% on overage
  4. HZN

    Scale

    Later

    Only after Cloud earns its keep. Heavy tenants stay exception-only. Still no Redis on OSS.

    • Plus SSO / audit when Plus needs it
    • Cloud split modes for hot orgs
    • ClickHouse for raw payloads (Cloud only)

Out of scope

We stay exception-only. No kitchen-sink observability bolted on later.

  • Tracing / APM
  • Session replay
  • Profiling
  • Generic logs
  • iOS / Android
  • Redis on OSS
Star on GitHubCloud pricing
Contribute

Three ways to help the next release.

Stack gate stays fixed: Rust + PostgreSQL 16 + RLS. Two containers. No Redis.

  • Report a bug

    Use Bug or SDK compatibility templates. Search existing issues first.

  • Improve docs

    Install steps, compatibility notes, and migration guides help the next clone.

  • Send a focused PR

    Fork, branch off main, run ./scripts/test.sh. Open an issue first for large changes.

Read CONTRIBUTING

Out of scope for Phase 1 PRs: Redis, ClickHouse, Kafka, tracing, replay, profiling, logs, iOS/Android, Cloud billing, or “100% Sentry parity.”

License

OSS is the product. Cloud is hosting.

Phase 1 core lives in the self-hosted binary under Apache 2.0. Cloud is managed hosting of that same path.

  • Apache 2.0

    Use, modify, redistribute. Attribution and patent terms follow the license in the repo.

  • Self-host stays free

    Full triage in OSS. You pay the VPS. No seat lock on the core path.

  • Cloud is flat

    Pro $24 / Plus $79 when it launches. Not an EE fork that strips triage.

License
Apache 2.0
Self-host
Free forever. Install path
Cloud
Flat Pro $24 / Plus $79. Pricing
FAQ

Before you star the repo.

What shipped in Phase 1?
Exception ingest (envelope and store), spike valve, JS/TS sourcemaps, grouping, PostgreSQL 16 with RLS, keyboard triage, regressions, webhooks, and lite RBAC. Two containers, Apache 2.0. No tracing, replay, profiling, or iOS/Android. Operator notes: docs changelog.
Is Cloud live?
No. Phase 1 is the self-hosted binary. Pro $24 and Plus $79 are published prices for managed hosting after clones: see pricing. Self-host is what you can run today.
Will you cripple the OSS build later?
The Phase 1 product is the self-hosted binary. Cloud is managed hosting of that same path, with triage staying in OSS.
How often do you ship?
Phase 1 landed as v0.1.0-phase1. The next public signal is the GitHub publish and Show HN cut. Watch releases for dated notes after that.
What license is Epure under?
Apache 2.0. You can use, modify, and redistribute the Phase 1 binary. Attribution and patent terms follow the license in the repo.
Is this 100% Sentry compatible?
No. We keep official Sentry SDKs on the wire and accept envelope/store for exceptions. Transactions are discarded. No replay, profiling, sessions, or mobile symbolication in Phase 1. Honest split: Epure vs Sentry.
How do I propose a large feature?
Open a GitHub issue first. PRs that assume Redis, Kafka, ClickHouse, or Cloud billing get closed. Focused fixes and docs land faster. Start from the contributing guide.
Where do I report a security issue?
Follow SECURITY.md. Prefer a private GitHub advisory, or email `security@news.epure.sh`. Do not file public issues for unpatched vulnerabilities.

Read the code. Run the binary.

Star the repo so the next person finds it. Docs when you want it on your box.

Star on GitHubSee docs

Apache 2.0 · Rust + Postgres 16 · two containers