Skip to content

New: Tracewell now reads Next.js 15 source maps on upload. See the setup

Sign in Start free
Error monitoring for small teams

Fix the bug before your users report it

Add one line to your app. Tracewell catches every exception, groups duplicates and pings Slack with the exact line that broke.

Start catching errors See a live alert

Free up to 50k events a month · set up in 2 minutes

Quantum Zephyr Nebula Horizon Modulus Patrick Vector
Sound familiar?

Right now, your users are your error monitor

A deploy goes out, checkout breaks, and you find out from a support ticket an hour later. Then you grep logs until dinner.

Time from bug to fix, same bug

3 h 13 min19 min

Without Tracewell

  1. Deploy v2.14.1
  2. Support email
  3. 3 refunds
  4. Found by grep

With Tracewell

  1. Deploy v2.14.1
  2. Slack: TypeError
  3. Maya: mine
  4. Fixed. Nobody noticed
Setup

One line in, every exception caught

No agent, no config file, no sampling rules to tune. Your first alert lands before the coffee does.

~/shop-api — zsh
  1. 01

    Install the SDK

    $ npm i @tracewell/node
added 1 package
  2. 02

    Add one line

    trace.init({ key })
  3. 03

    Deploy as usual

    $ git push
✓ live · 0.9s
Grouping

1,284 errors, one issue to fix

Tracewell fingerprints every stack trace. The same crash becomes one issue, with a count, the users it hit and the release it came in.

  • One alert per bug, not per event
  • Regressions reopen the old issue
Slack alerts

The exact line, in the channel you watch

Every alert names the file, the line, the commit and its author, with the code around it. Tap Assign and the fix starts in Slack, not in a dashboard.

Read an alert
Inside an alert

Everything you need to fix it, nothing to dig for

  1. 1

    The exact line

    With the code around it, from your source maps.

  2. 2

    Who changed it

    The commit and author, straight from GitHub.

  3. 3

    Who it hit

    Users, browsers and the release, so you know the blast radius.

  4. 4

    What led there

    The last clicks and requests before the crash.

Integrations

Works with the stack you already run

  • Node.js and Next.js

    Source maps upload on build.

  • Python and Django

    Celery tasks caught too.

  • Ruby, Go and PHP

    Same one-line init.

  • Slack

    Alerts, assign and resolve.

  • GitHub

    Commit and author on every issue.

  • Linear and Jira

    One click turns an issue into a ticket.

What a lead engineer says

“We used to learn about bugs from our support inbox. Now Tracewell pings us before the first ticket lands, and most fixes ship inside twenty minutes.”
Priya RamanLead engineer, Pollen · team of 12
19 minmedian time from crash to fix
−72%bug reports from users in 3 months
Portrait of Priya Raman, lead engineer at Pollen
Pricing

Priced for teams of five, not five hundred

Flat team pricing. No per-seat fees, so your whole team gets the alerts.

Hobby

For side projects and first launches.

Free
  • 50k events a month
  • 1 project
  • Slack alerts
  • 7-day history
Start free

Team

For startups shipping every day.

$29/ month, whole team
  • 500k events a month
  • Unlimited projects
  • GitHub commit and author
  • Assign from Slack
  • 90-day history
Try Team free

Growth

For busy apps with real traffic.

$99/ month, whole team
  • 5M events a month
  • Spike protection
  • SSO and audit log
  • 1-year history
  • Priority support
Start with Growth
FAQ

Questions, answered

Will the SDK slow my app down?
No. Events are queued in memory and sent in the background, adding under 1 ms to a request. If our API is down, your app never waits.
What if a bad deploy floods us with errors?
Duplicates group into one issue, and spike protection caps what counts toward your plan. You never get a surprise bill or 4,000 Slack pings.
Does user data leave our servers?
Only what you allow. Emails, tokens and card numbers are scrubbed in the SDK before sending. Data is encrypted and stored in the EU or US, your choice.
Can we switch from our current tool?
Yes. Swap the init line, keep your source-map upload step, and run both side by side for a week if you like. Most teams switch in an afternoon.
Do we need a dashboard open all day?
No. You can assign, mute and resolve from Slack. The dashboard is there when you want history or trends.

Hear about the next bug before your users do

Free for your first 50k events. Your next crash shows up in Slack with its line number.

Start catching errors Read the docs

Your first 60 seconds

$ npm i @tracewell/node
  • Install the SDK0:10
  • Add trace.init()0:30
  • First alert in Slack0:58