Skip to content

Know why production broke.
Then squash it.

AI-native observability. Every root cause cites its evidence, and Squasher checks that the fix held after deploy. No per-seat pricing. OpenTelemetry-native.

Free plan. No credit card required. Or let your coding agent set it up.

Works with the platforms you already ship on.

  • Vercel
  • Cloudflare
  • AWS
  • OpenTelemetry
  • Supabase
  • Railway
  • GitHub
  • Slack
  • Linear
  • PagerDuty

From the first error to a verified fix.

This is the Squasher dashboard. Click around, or follow the steps.

app.squasher.ai/acme/checkout-api/logs

acmecheckout-apiExplore

⌘ K
ExploreLogsTracesSessions

Logs

Live
Search and inspect logs for this project.
LevelTimestampMessage
info14:06:13.251POST /api/checkout 500 in 2.31 s
error14:06:13.246TypeError: Cannot read properties of undefined (reading 'amount')
warn14:06:13.244pricing: price still pending at render
info14:06:12.988order 7f13 received, currency EUR
info14:06:12.730GET /api/cart 200 in 84 ms
info14:06:12.114cart.load cart=8f21 items=3

Example project and data

Every instrument on one panel.

Errors show what broke. Logs, traces, and replays show why, linked by trace and session ID.

    1. 14:06:09infoPOST /api/checkout 200 188ms
    2. 14:06:11infocart.load cart=8f21 items=3
    3. 14:06:12warnpricing: price pending at render
    4. 14:06:12errorTypeError: reading 'amount' of undefined
    5. 14:06:14infoPOST /api/checkout 500 2.31s
    6. 14:06:15warnretry pricing.load attempt=2
    7. 14:06:16infoGET /api/cart 200 84ms
    8. 14:06:18errorTypeError: reading 'amount' of undefined
    9. 14:06:09infoPOST /api/checkout 200 188ms
    10. 14:06:11infocart.load cart=8f21 items=3
    11. 14:06:12warnpricing: price pending at render
    12. 14:06:12errorTypeError: reading 'amount' of undefined
    13. 14:06:14infoPOST /api/checkout 500 2.31s
    14. 14:06:15warnretry pricing.load attempt=2
    15. 14:06:16infoGET /api/cart 200 84ms
    16. 14:06:18errorTypeError: reading 'amount' of undefined

    Logs

    Every log line, searchable, and linked to its trace.
    1. POST /api/checkout
    2. cart.load
    3. pricing.load
    4. db.query prices
    5. render.total
    6. 0 msrender.total threw2.31 s
    See where a slow request spent its time.
  • shop.example.com/checkout
    Total
    Pay
    Something went wrong

    error at 1:031:40

    What the user saw, right before the error.
    • checkout-api
    • pricing
    • web
    • webhooks
    • 30 checks · 3 regions1 failed · incident opened
    Checks that open an incident when they fail.
  • OKsupport.reply1.2k tok840 ms
    OKtool lookup_order210 tok95 ms
    Slowsummarize.ticket3.4k tok2.1 s
    OKsupport.reply1.1k tok790 ms
    Model and tool calls, with tokens and latency.
    • SEV-2checkout-api: error burstInvestigatingIdentifiedResolved
    • SEV-3Webhook deliveries failing with 502Monitoring
    • SEV-4Slow pricing queryResolved
    One timeline, from the first alert to resolved.

Previews show example data.

The cause, named. The fix, drafted.

AI triage is on every plan. Incident alerts in Slack carry the impact, the likely cause, and a next step.

  • New issues get a likely cause, the impact, and a next step.
  • Create fix opens a pull request on Team and up. Squasher never merges on its own.
  • Ask the Squasher Agent follow-up questions. It searches your logs and traces.
How AI triage works

#incidents

12

SquasherAPP2:06 PM

checkout-api: error burst

Severity: SEV-2Status: Investigating

Started 4m after deploy of checkout-api@a41c

▸ Impact

Error logs on checkout-api went from 3 to 41 a minute. Checkouts return 500.

▸ Root cause

The errors began 4 minutes after checkout-api@a41c deployed. That release is the likely cause.

▸ Recommended action

Roll back a41c, or open the TypeError issue and run Create fix.

Monitor: checkout errors · Opened 2:06 PM

View in SquasherInvestigate

SquasherAPP2:31 PM

checkout-api: error burst

Severity: SEV-2Status: Resolved

Example alert.

Set up in one prompt.

Paste it into your coding agent. It installs Squasher, sends one real event, and reports what changed. Then it can use Squasher to debug.

Or set it up yourself

Paste into your coding agent
Install Squasher for this project. If Squasher skills or MCP are not configured in this agent environment, run `bash <(curl -fsSL https://squasher.ai/install.sh) --agents -y`. Then read https://skills.squasher.ai/squasher-onboard/SKILL.md, map every runnable app/service/worker/frontend/agent in the repo, choose the matching Squasher SDK, log drain, OTLP, or Agent SDK path, initialize with SQUASHER_API_KEY and SQUASHER_PROJECT_ID from environment variables, send one real verification event, and report the files changed plus the verification step. Do not hardcode or reveal real API keys.
bash <(curl -fsSL https://squasher.ai/install.sh) --agents -y

Priced by volume, never by seat.

Start free. Invite the whole team. AI triage is included on every plan.

Compare every plan

Free

For side projects, evals, and internal tools.

$0/ month

No card needed. No overage charges.

Start free
10 GB telemetry
5K replays
500 AI credits

Included

  • AI triage on new issues
  • 500 AI credits / month (an investigation uses 50)
  • 1 project

Pro

For small production apps that want one tool, not five.

$29/ month

Flat price. No per-seat fees.

Start on Pro
100 GB telemetry
10K replays
3K AI credits

Everything in Free, plus

  • 3,000 AI credits / month (an investigation uses 50)
  • 5 projects
  • 30 monitors with 30-second checks

Team

Most Popular

For product teams replacing separate error, replay, and status tools.

$99/ month

Flat price. No per-seat fees.

Start on Team
250 GB telemetry
40K replays
12K AI credits

Everything in Pro, plus

  • 12,000 AI credits / month (an investigation uses 50)
  • Unlimited projects
  • 25 status pages

Scale

For high-volume teams with security, procurement, and support needs.

$299/ month

Flat price. No per-seat fees.

Start on Scale
1 TB telemetry
150K replays
30K AI credits

Everything in Team, plus

  • 30,000 AI credits / month (an investigation uses 50)
  • 100 status pages
  • 250 monitors with 30-second checks

Need more volume, a security review, or custom terms? Get in touch.

Go squash some bugs.

Connect one service and send one real event. The crew takes it from there.

Free plan. No credit card required.