Live · every environment

Every error.
The moment it happens.

ErrTap connects errors, uptime, cron heartbeats, logs, releases, and alerts in one calm operational view, so the first signal leads to a confident fix.

  • Free to start
  • No credit card
  • Install in minutes

TypeError e.items.map is not a function

Lagos · production · 12s ago

Staging API is down

3 of 5 probes failing · incident opened

SDKs for the stack you ship

  • Browser
  • Node.js
  • Next.js
  • NestJS
  • React Native
  • Laravel
  • .NET
Overview

A briefing, not a wall of charts.

Open ErrTap and it tells you what changed: what is escalating, what is down, which job went quiet, and which deploy started it.

ErrTap overview: 944 events in the last 24 hours with a severity-stacked error pulse, the issues that need you, a live globe of where errors happen, uptime and heartbeats.ErrTap overview: 944 events in the last 24 hours with a severity-stacked error pulse, the issues that need you, a live globe of where errors happen, uptime and heartbeats.
Product tour

Everything after the alert, in one place.

Real screens from the ErrTap dashboard. Nothing here is a mockup.

ErrTap Issues screenErrTap Issues screen

01 / 07 · Issues

Triage at keyboard speed.

Every issue ranked by severity and velocity, with its own history, users hit, and escalating or regressed flags.

  • J / K to move, X to select, E to resolve
  • Escalating means 3× its own 14-day baseline
  • Resolved issues reopen themselves if they return
Signals

Follow a failure from symptom to cause.

Six signals that usually live in six tools, connected on one project timeline.

Error intelligence

Turn event floods into one issue

Fingerprinting normalizes volatile data and groups matching failures, so ownership starts with the real problem.

2,481
repeat events → 1 issue
Escalating
24h agonow
Triage

Keyboard-first inbox

Move, select, resolve and assign without touching the mouse.

  • JKmove
  • Xselect
  • Eresolve
  • Iignore
  • Aassign
AI root cause

An answer, with receipts

A root-cause read grounded in the stack, release and surrounding context.

Root cause

items is undefined when the cart API times out; useCart.ts:42 maps before the fallback.

stack framerelease 2.8.13 logs
Uptime & crons

Catch the outage and the job that went quiet

HTTP and TLS checks run continuously; heartbeat deadlines surface silent queue, billing and backup failures.

API health99.8%
api.errtap.com/health126 ms p50
  • nightly-backup6h ago
  • billing-sync14m ago
  • email-digestMissed
Release health

Blame the deploy, not the team

Tie regressions to the exact release that introduced them.

  • 2.8.1Latestproduction · 1d ago
  • 2.8.0production · 2d ago
  • 2.7.0production · 3d ago
Performance

Vitals from real sessions

p75 LCP, INP and CLS per page, scored against Google’s thresholds.

2.1s
LCP · p75
184ms
INP · p75
0.12
CLS · p75
Logs & context

Logs beside the issue

Structured logs attached to the error they explain.

09:23:41infocheckout.started cart=4 items
09:23:42warncart-api slow 2380ms
09:23:44errorTypeError e.items.map…
Alert routing

Alert once, with the context to act

Rules connect the incident, environment, release and owning channel in a notification your team can trust. Cooldowns and deduplication keep it quiet.

  • New production error
  • Regression
  • Downtime
  • Cron missed
  • Emailon-call@
  • WebhookSlack or any URL
  • Deduped1 alert per subject
Built for production

One layer for the complete production loop.

Connected production context

Errors, checks, heartbeats, logs, releases, and incidents share one project timeline.

Fast asynchronous ingestion

SDK events are accepted quickly and processed off the request path through durable workers.

Safe alert execution

Encrypted channel secrets, cooldowns, and subject-aware deduplication keep alerts useful.

Project-scoped setup

Every project gets a DSN and install path for the stack it actually runs.

Clear operational history

Issues, status changes, comments, releases, and audits remain readable after the incident.

One issue now shows us the failed deploy, affected environment, relevant logs, and the alert trail. Triage finally starts with context.

Production engineering

ErrTap design partner

202 ingest6 signals1 timelineAudit ready
Install anywhere

Your first event in under five minutes.

Create a project, copy its DSN, and add three lines. Sentry SDKs work with the same DSN if you are moving over.

Browser
Node.js
Next.js
NestJS
React Native
Laravel
.NET
HTTP API
app.tsnpm i @errtap/browser
import { init } from '@errtap/browser';

init({
  dsn: 'https://et_…@api.errtap.com/1',
  environment: 'production',
  release: process.env.GIT_SHA,
});

// window.onerror and unhandled rejections are captured.
First event received202 Accepted
Pricing

Free to start. Fair as you grow.

Every plan includes error tracking, uptime checks and alerts. Upgrade when your event volume does.

Hobby

$0/mo
  • 50k events / mo
  • 1 project
  • 3 uptime checks
  • 1-day retention
Start free

Pro

Most popular
$29/mo
  • 2M events / mo
  • Unlimited projects
  • 50 uptime checks
  • 30-day retention
Start free trial

Team

$60/mo
  • 10M events / mo
  • Unlimited projects
  • 100 uptime checks
  • 90-day retention
Start free trial

Enterprise

Custom
  • Volume event pricing
  • Custom retention
  • SLA + on-call support
  • Dedicated success engineer
Talk to us
FAQ

Questions, answered.

Built for production data boundaries
Can ErrTap replace separate error and uptime tools?

Yes. ErrTap connects error tracking, logs, checks, cron heartbeats, releases, incidents, and alert delivery inside each project.

Does ingestion slow down application requests?

No synchronous issue write happens on the hot path. Accepted events are queued for grouping and processing.

Which platforms are supported?

ErrTap ships SDK and setup guidance for browser, Node.js, Next.js, NestJS, React Native, Laravel, .NET, and direct HTTP ingestion.

How are alert secrets protected?

Notification-channel secrets are encrypted at rest and are never returned to the dashboard after storage.

Can we start without a sales call?

Yes. Create an account, add a project, copy its DSN, and send the first event on the free plan.

Your users should never be your monitoring system.

Start with the complete production trail. Scale when your event volume does.