Wystan + Sentry
Sentry owns the error — the stack trace, the release, the user it hit — and with Seer it now reviews your pull requests with production telemetry in hand. Wystan sits one level up: it groups Sentry’s errors by the product feature they land in, joins them to usage, ownership and history, and tells every PR what it is touching. Sentry says this stack trace broke; Wystan says Checkout broke. We consume Sentry, we don’t replace it.
The system of record for production errors. Symbolicated stack traces, release health, session replay, profiling — and Seer, the AI agent that finds root causes and reviews PRs with production context, flat-priced per active contributor.
- Error & performance monitoring with symbolicated stack traces
- Release health, session replay, profiling
- Seer: AI root-cause analysis + production-aware PR review
- Flat $40 / active contributor / mo for Seer, unlimited usage
- First-party MCP server
The product grain. Sentry attributes an error to an issue, a file and a release; Wystan attributes it to a named product feature and a user journey — and puts usage, ownership and history on the same row.
- Errors grouped by product feature (“Checkout broke”), not by stack trace
- Usage, ownership and history joined to the same feature
- PR comment: which features the diff touches + their live error count
- Weekly Slack digest: which features regressed this week
- Per-org pricing, unlimited developers — zero SDK changes, we read your Sentry
How they actually combine
chargeCustomer() in the billing
module.Just Wystan, on its own
Without Sentry, Wystan still maps, scores and comments — you lose the production error overlay, and keep everything that comes from git history: features, journeys, maintenance pressure, inactive-author ownership, rework and structural overlap. Without Wystan, Sentry tells you what broke and where in the code — but not which product capability it belongs to, how much traffic that capability carries, or how it has been trending. The two are designed to stack.
Where each one focuses
| Focus area | Sentry | Wystan |
|---|---|---|
| Primary unit | Issue / stack trace / release | Product feature + user flow |
| Production errors | ✓ the source | ✓ grouped per feature (read from Sentry) |
| PR review | Seer — the diff, with production context | Feature map + fix-work rank + structural reach + contribution evidence |
| History & trends | Release health | Maintenance pressure, rework and inactive-author ownership per feature, over time |
| Usage | — | PostHog traffic per mapped feature, kept as its own evidence channel |
| MCP server | ✓ | ✓ + 14 tools |
| Pricing | Seer $40 / active contributor / mo | $99–299 / org / mo, unlimited developers |
| Best fit | Debugging and incident triage | Knowing what changed, what it touched, and what is getting worse |