Keep your Sentry SDK. Change one line.
Squasher accepts error events from Sentry SDKs. Point the DSN at Squasher, and each new production issue gets AI triage, on every plan.
Free plan. No credit card required.
| Signal | Sentry | Squasher |
|---|---|---|
| Errors | Included: Own SDKs | Included: Sentry SDKs or ours |
| Logs | Included: 5 GB, then per GB | Included: SDKs, OTLP, drains |
| Tracing | Included: Sentry SDK spans | Partly: OpenTelemetry only |
| Profiling | Costs extra: Pay as you go | Not offered or not listed: Not offered |
| AI root cause | Costs extra: Seer add-on | Included: On every plan |
| Status pages | Not offered or not listed: Not listed | Included: On every plan |
Where Sentry wins, and where Squasher does.
Both group errors into issues. The difference is what sits around them, and what the AI costs.
Sentry
Pick Sentry when
- You need profiling, or native crash reporting for mobile and games.
- You trace through Sentry's SDKs and do not plan to use OpenTelemetry.
- You want Seer to review pull requests before they deploy.
- Your team works from release health, suspect commits, and code owners.
Squasher
Pick Squasher when
- You want AI triage on every plan, with no per-contributor add-on.
- Your logs come from Vercel, Railway, or another platform drain, or from OpenTelemetry.
- You want uptime monitors, heartbeats, incidents, and a status page in the same tool.
- You want to test with the SDK you already ship: one DSN, one service.
Sentry and Squasher, feature by feature.
Sentry is the broader platform. Squasher covers the error workflow and the signals around it.
Events from Sentry SDKs
- Sentry
- Native
- Squasher
- Error and message events. Change the DSN.
Own SDKs
- Sentry
- Web, backend, mobile, and games
- Squasher
- Browser, Next.js, Node.js, Workers, Rust
Tracing
- Sentry
- Spans from Sentry SDKs
- Squasher
- OpenTelemetry. Sentry transactions are not read.
Logs
- Sentry
- 5 GB on each plan; $0.50/GB more on paid plans
- Squasher
- SDK logs, OTLP, and log drains
Session replay
- Sentry
- 50 replays on each plan
- Squasher
- Browser SDK, linked to errors by session
Profiling
- Sentry
- Yes
- Squasher
- No
Cron and uptime
- Sentry
- 1 cron and 1 uptime monitor included
- Squasher
- Heartbeats and uptime monitors
Status pages
- Sentry
- Not listed
- Squasher
- On every plan
AI root cause
- Sentry
- Seer, $40 per active contributor a month
- Squasher
- AI triage on every plan
AI fix pull requests
- Sentry
- Seer fix generation
- Squasher
- On Team and up
Users
- Sentry
- 1 on Developer, unlimited on paid plans
- Squasher
- No per-seat price
MCP server
- Sentry
- Yes
- Squasher
- Yes
Sentry facts checked 2026-10-20 on Sentry’s own pages: Sentry pricing, Sentry pricing docs (Seer price), Seer docs. Squasher facts come from our docs and pricing.
One setting, not a new SDK.
Squasher reads the event items Sentry SDKs already send. Swap the DSN, and your capture calls keep working.
- Node.js, Python, Go, Ruby, PHP, Java, .NET, React Native, and browser SDKs.
- The exception, message, tags, user, request, release, and environment are kept.
- Set tracesSampleRate to 0, and send traces with OpenTelemetry.
1import * as Sentry from "@sentry/node";2 3Sentry.init({4 // Before: dsn: "https://abc123@o1.ingest.sentry.io/456"5 dsn: "https://sq_pk_your_key@ingest.squasher.ai/your-project-id",6 // Sentry transaction items are not ingested; send APM data with OTLP.7 tracesSampleRate: 0,8});
Node.js example.
AI triage is part of the plan.
Sentry sells Seer per active contributor. Squasher runs AI triage on new production issues, on every plan.
- Reads the error type, message, service, environment, and event counts.
- Writes the likely cause, the impact, and a next step.
- Create fix opens a pull request after your tests pass, on Team and up. You merge it.
TypeError: Cannot read properties of undefined (reading 'amount')
HighUnresolvedError
AI triage
checkout-api throws a TypeError in production when it reads amount from an undefined value: 1,339 events in 12 minutes. Likely cause: a price is read before it has loaded. Impact: high, the failing requests are checkouts. Next step: guard the read of amount and wait for the price.
- Events
- 1,339
- First seen
- 12 min ago
- Last seen
- 1 min ago
Fingerprint
9f2c41e8a0b7d3c6Issue
- Status
- Unresolved
- Priority
- High
- Environment
- production
- Service
- checkout-api
- Assignee
- Squasher AI
Workflow
[Squasher] Fix: TypeError — Cannot read properties of undefined (reading 'amount')
OpenOpened by the Squasher hosted agent · #482
- src/payments/currency.ts+2 −1
- src/payments/currency.test.ts+6
All checks have passedReview required
Example issue and pull request
The plans, side by side.
Both start free and bill paid plans by volume. The difference is what the base price includes.
Sentry
List prices from their pricing page
- Developer
- $0
- 1 user, 5K errors, 5 GB logs, 5M spans, 50 replays, 30-day lookback
- Team
- $26/month, billed annually
- Unlimited users, 50K errors, 5 GB logs, 5M spans, 50 replays, up to 90-day lookback
- Business
- $80/month, billed annually
- Team, plus unlimited dashboards, advanced quota management, and SAML and SCIM
- Seer
- $40 per active contributor a month
- AI root cause analysis, fix generation, and code review, on Team and Business
Squasher
Monthly plans. No per-seat price.
- Free
- $0/month
- 10 GB of errors, logs, traces, and metrics, 5K replays, 30-day error history
- Pro
- $29/month
- 100 GB of errors, logs, traces, and metrics, 10K replays, 90-day error history
- Team
- $99/month
- 250 GB of errors, logs, traces, and metrics, 40K replays, 90-day error history
- Scale
- $299/month
- 1 TB of errors, logs, traces, and metrics, 150K replays, 90-day error history
How to compare
- Sentry's Team and Business prices are for annual billing with default prepaid volume. Billed monthly, they are $29 and $89.
- The Seer price is on Sentry's pricing docs. Sentry's pricing page lists Seer at an additional cost.
- Sentry counts an active contributor as anyone who opens 2 or more pull requests in a Seer-enabled repository.
- Price a normal month of errors, log GB, and replays on both before you decide.
Sentry facts checked 2026-10-20 on Sentry’s own pages: Sentry pricing, Sentry pricing docs (Seer price), Seer docs. Squasher facts come from our docs and pricing.
Move one service first.
Run both tools for about a week. If anything looks wrong, restore the old DSN.
Build the DSN
Use an ingest-only API key and your project ID. The key can send events but cannot read data.
https://<ingest-key>@ingest.squasher.ai/<project-id>Change it in one service
Pick a low-risk service or a preview environment. Keep the Sentry SDK, swap the DSN, and turn off Sentry transactions.
Sentry migration guideSentry.init({ dsn: "<the DSN from step 1>", tracesSampleRate: 0,});Send traces with OpenTelemetry
Point your OTLP exporter at Squasher, so errors, logs, and spans share trace IDs.
OTEL_EXPORTER_OTLP_ENDPOINT="https://ingest.squasher.ai"OTEL_EXPORTER_OTLP_HEADERS="x-squasher-key=$SQUASHER_API_KEY"Compare, then move alerts
Compare one known error in both tools. Rebuild your alert routes in Squasher before you turn off the old ones.
Notification routing
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 -yQuestions, answered.
Is Squasher a drop-in Sentry alternative?
For error events, yes. Squasher accepts the event items that Sentry SDKs send, so you change the DSN and keep your capture calls. Sentry transactions are not read, so send traces with OpenTelemetry. Other Sentry alternatives usually ask you to install a new SDK first.
Do I have to remove the Sentry SDK?
No. Keep it installed and change where it sends errors. To roll back, restore the old DSN.
Can I run Sentry and Squasher at the same time?
Yes. Most Sentry SDKs take one DSN, so point one service or preview environment at Squasher, or use a tunnel or proxy. Run both for about a week and compare the same error in each before you move alerts.
How does the AI pricing compare?
Sentry's pricing page lists Seer, its AI debugger, at an additional cost: $40 per active contributor a month, per Sentry's pricing docs. Squasher's AI triage is on every plan, and fix pull requests are on Team and up. Checked 2026-10-20.
What does Sentry do that Squasher does not?
Sentry has profiling, tracing through its own SDKs, release health, and native SDKs for mobile and game crash reporting. Squasher has no native mobile SDK; mobile apps can send errors through Sentry's iOS, Android, and React Native SDKs.
Which Sentry SDK versions work?
SDKs that use the envelope protocol. For example: @sentry/node and @sentry/browser 7.0.0 or later, sentry-python 2.0.0 or later, and sentry-ruby 4.0.0 or later. Older SDKs that post to /store/ are not supported.
Is the key in the DSN safe in browser code?
Use an ingest-only API key. It can send events but cannot read data or manage the project, the same model as Sentry's public DSN key.
Keep exploring.
Try it on one service.
Change one DSN in a preview environment and compare the same error in both tools.
Free plan. No credit card required.


