36 Startup Terminal Phosphor Stacktrace

How it works

From exception to fix in four steps.

Stacktrace sits between your app and your team. It catches what broke, tells you why, and gets out of the way.

01

Capture with one SDK call

Initialize the SDK in your entrypoint. Every uncaught exception, promise rejection, and crash is sent automatically — with stack frames, request context, and breadcrumbs leading up to the failure.

Stacktrace.init({ dsn })

capture.ts

try {
  processOrder(req)
} catch (err) {
  Stacktrace.captureException(err, {
    user: { id: req.userId },
    tags: { route: "/checkout" }
  })
}

02

Group by root cause, not by message

1,000 identical crashes become one issue. Stacktrace groups by normalized stack frame, so a typo in a template doesn't flood your inbox with 50 slightly-different error strings.

fingerprint: stack-frame[0] + module

03

Link to the exact commit and line

Source maps are uploaded automatically on every release. Each issue links to the guilty commit, the diff, and the author — so you know who to ping and what changed.

release: v4.2.1 · commit a8f3c2d

release-link.json

{
  "issue": "TypeError @ orders.ts:42",
  "release": "v4.2.1",
  "commit": "a8f3c2d",
  "author": "marcus@stacktrace.io",
  "diff": "/repo/commit/a8f3c2d.diff"
}

04

Route alerts to the right person

Slack, PagerDuty, email, or webhook. Route by project, severity, or release tag. New issues page the on-call engineer; regressions page the author of the breaking commit.

route: new → on-call · regression → author

Error dashboard

Every error in your app, on one screen.

Issues grouped by root cause, sorted by impact. Click any issue to see the full stack trace, source context, and the commit that introduced it.

stacktrace — checkout-service production · v4.2.1

Open issues

23

↓ 12% vs last week

Events (24h)

8,412

↓ 5% vs yesterday

Affected users

1,247

↓ 8% vs yesterday

Resolved (7d)

61

↑ 34% vs last week

TypeError: Cannot read 'map' of undefined

1,247 events3h ago

ReferenceError: processOrder is not defined

842 events6h ago

NetworkError: 502 Bad Gateway (payments-api)

318 events8h ago

ChunkLoadError: Loading chunk 4 failed

204 events12h ago

ValidationError: email format invalid

156 events1d ago

TimeoutError: db query exceeded 5000ms

89 events1d ago

TypeError: Cannot read 'map' of undefined

at renderOrders (orders.ts:42)

→ 42 const items = order.items.map(i => i.name)

at OrderList (OrderList.tsx:18)

18 <OrderList orders={orders} />

· · ·

40 export function renderOrders(order) {

41 if (!order) return null

42 const items = order.items.map(i => i.name)

43 return <ul>{items}</ul>

44 }

Integrations

Plugs into the tools you already use.

One SDK for your runtime. Webhooks and native integrations for everything else. No custom adapters, no middleware.

{ }Node.js

pyPython

goGo

rsRust

jvJava

rbRuby

#Slack

PDPagerDuty

ghGitHub

glGitLab

jnJira

dcDiscord

Pricing

Pay for events, not seats.

Every plan includes unlimited team members, all integrations, and 30-day retention. Upgrade when you need more volume or longer history.

Compare plans

Developer$0 /moFor side projects.

Team$49 /moFor production apps.

Scale$199 /moFor high-volume systems.

Events / month

5,000

150,000

2,000,000

Retention

30 days

90 days

1 year

Team members

unlimited

Source maps & commit linking

yes

Slack & PagerDuty alerts

email only

all channels

Custom alert routing

—

yes

SSO & audit log

—

yes

SLA & support

community

email · 24h

priority · 1h

Start free →

Start 14-day trial

Talk to us →

Every crash, one click from the line that broke.