Your production errors, fixed by your agents

Keep the Sentry SDK you know and only change the DSN. ERHA groups the errors, tracks every release and opens a task that your project's agent takes on.

Create my spaceBook a demo
  • Works with the official Sentry SDKs
  • Source maps read to find your own code
  • One task per error, linked both ways
Online store
To handle3ResolvedIgnored
  • TypeError: Cannot read properties of undefined (reading 'price')src/checkout/summary.tsx · v2.14.0Regression214events
  • UniqueConstraintViolationException: duplicate key order_refsrc/Controller/OrderController.php · v2.14.0Task #31812events
  • ChunkLoadError: Loading chunk 412 failedapp/catalogue/page.tsx · v2.13.2New6events

One DSN to change, nothing else

ERHA speaks Sentry's protocol. You keep your language's official SDK and its instrumentation: only the address it sends to changes.

  • JavaScript
  • React
  • Next.js
  • Node.js
  • React Native
  • PHP
  • Symfony
  • Laravel
  • Python
  • WordPress
Or let an agent install itTurn the tool on for your application: the agent reads your repository, picks the right SDK, adds the code and opens a merge request.

Before

Sentry.init({
  dsn: "https://4f1c…@o0.ingest.sentry.io/42",
})

With ERHA

Sentry.init({
  dsn: "https://4f1c…@api.erha.ai/1287",
})

From error to fix, without switching tools

Errors live next to your project's tasks and agents. Nobody copies a stack trace into a ticket.

  1. 01

    The error comes in

    Occurrences of the same error are grouped, with the number of people affected and the release involved.

  2. 02

    A task opens

    In one click, or on its own for every new error. The stack trace and the link are in the description.

  3. 03

    An agent fixes it

    You start the task: the project's agent reads the error, fixes the code and opens a merge request with a preview.

  4. 04

    The error closes

    The finished task resolves the error. If it comes back in a newer release, the task goes back to to-do.

The line in your code, not in the minified file

ERHA reads your source maps and shows the stack trace with your files, your functions and your line numbers.

  • Uploaded at build time with a dedicated token, or read from your site
  • Source maps removed from your build by default
  • Your application's frames kept apart from libraries

TypeError: Cannot read properties of undefined (reading 'price')

  • Summarysrc/checkout/summary.tsx42:18
    40 const items = useCart()
    41 const shipping = useShipping(items)
    42 const total = lineTotal(items[0].price)
    43 return <Total value={total} />
  • lineTotalsrc/checkout/totals.ts17:9
  • renderWithHooksreact-dom

What error tracking does

Grouped errors

The same error shows once with its counters, however many times it happens.

Tracked by release

A resolved error that comes back in a newer release is flagged as a regression.

Ignore for a while

An hour, a week or for good: the error comes back on its own when the time is up.

In your Activity

New errors and regressions show up with the rest of the space's work.

Protected data

No IP address or email kept, secrets filtered out, events kept for 90 days.

Web, mobile and server

One screen for the front end, the API and the mobile app of the same project.

Frequently asked questions

Do we need to rewrite our instrumentation?

No. ERHA accepts what the official Sentry SDKs send. You keep the SDK and its calls, and you replace the DSN with your application's DSN in ERHA.

Which languages are supported?

Those with an official Sentry SDK: JavaScript, Node.js, PHP, Python and the others. For a site without a build step, such as WordPress or a plain HTML page, a tag in the head is enough.

How do source maps work?

You upload them at build time with our script and a dedicated token, or ERHA reads the ones published on your site. By default, the script then removes them from the build so they are not served.

What do you keep from each error?

The fields needed to diagnose it, for 90 days. Secrets are filtered out, no IP address or email is kept, and affected people are counted with a fingerprint that cannot identify them.

How much does it cost?

Error tracking is included in your space. Each application has a daily event quota; past it, events are refused until the next day. An agent's work on a fix is paid from the AI credit, like any task.

Hand over your first piece of work this week

Open your space in a few minutes, or book a demo to scope a first use case with the ERHA team.

Create my spaceBook a demo