Sentry Seer
Sentry's AI agent that root-causes and fixes bugs from your own telemetry
Overview
Seer is the AI debugging agent built into Sentry. It uses the stack traces, spans, logs and commits Sentry has collected to find the root cause of an issue, draft a fix or pull request, or hand the fix to an external coding agent. It is a paid add-on to Sentry's Team and Business plans, billed at $40 per active contributor a month.
Pricing
Pricing shown for reference only. These figures reflect RECATOOLS research as of 14 Oct 2026 and may be out of date or incomplete. This is not financial or purchasing advice — always confirm the current price on the provider’s official website before making any decision.
- Root Cause Analysis
- Fix Generation
- Error Prediction and Code Review
- Only on Team or Business
- Unlimited users
- API and third-party integrations
- 20 custom dashboards
- Seer available (subscription required)
- Team features
- Unlimited custom dashboards
- Advanced quota management
- SAML and SCIM
- Business features
- Technical account manager
- Dedicated customer support contact
Use cases
What you can produce with Sentry Seer
- Automatic issue scans with an actionability score for each new Sentry issue
- Root-cause analysis drawing on stack traces, spans, logs, profiles and commits
- Generated code fixes opened as pull requests (GitHub) or merge requests (GitLab)
- Root-cause handoff to Claude Code, Cursor Cloud Agents or GitHub Copilot to write the fix
- Plain-language questions about your telemetry, plus dashboards, monitors and alerts, via Seer Agent (open beta)
- Pull-request checks for likely production errors (a feature Sentry has said is being retired)
Seer's advantage is its evidence: it starts from the production telemetry already sitting in your Sentry account rather than a pasted error message, and it can hand its root-cause analysis to Claude Code, Cursor or Copilot to write the patch. Flat pricing of $40 per active contributor a month, with unlimited use, is easy to budget.
It only makes sense if Sentry is already your monitoring backbone, the per-contributor charge counts anyone with two pull requests in a connected repo, and the code-review feature carries a retirement note on Sentry's own blog. Good for teams deep in Sentry; not a standalone AI fixer.
What we found
Seer is the AI debugging agent inside Sentry, the error-monitoring service run by Functional Software, Inc. in San Francisco. It began as Autofix, which Sentry opened as a waitlisted beta in March 2024, and became generally available under the Seer name in June 2025. Its premise is that a bug is easier to diagnose from production evidence than from source code alone, so it works from what Sentry has already collected: stack traces, spans, logs, profiles and the commits behind them.
Day to day it does four things. Autofix scans incoming issues, scores how likely each is to be fixable by a code change, finds a root cause and can open a pull request, or hand the final coding step to Claude Code, Cursor or GitHub Copilot. Seer Agent, still in open beta, answers plain-language questions about your telemetry and can build dashboards and alerts; since September 2026 it can also read Datadog and Google Cloud data. Code review checks pull requests against known failure patterns, though Sentry's own January 2026 launch post now carries a note that it is being retired, while the docs and pricing page still list it. Repositories must be on GitHub.com or GitLab.com; self-hosted instances are not supported.
Pricing changed in January 2026. At launch Seer cost $20 a month including $25 of usage credits; it is now $40 per active contributor per month with unlimited use, where an active contributor is anyone who opens two or more pull requests in a Seer-enabled repository that month. Sentry's own example: ten such people cost $400, three cost $120. It is only sold on top of a paid Team or Business plan, which start at $26 and $80 a month on annual billing, and existing customers can trial it for 14 days.
The dependency is the point and the limit. Without Sentry already instrumenting your application, Seer has nothing to reason from, and any generated fix still needs a human to read the diff.
Compiled by RECATOOLS from public sources: vendor documentation and pricing, code repositories and published reporting.
About this listing
This entry was compiled from publicly available data including Sentry Seer's official website, press releases, documentation, and reputable third-party publications. RECATOOLS is not affiliated with Sentry Seer unless explicitly stated.
Third-party AI tools update their pricing, features, availability, and policies frequently. Information here may be outdated by the time you read this — we make reasonable efforts to keep listings current, but cannot guarantee absolute accuracy.
For the latest details, please refer to Sentry Seer directly →
Spotted something out of date? Suggest an update →
Alternatives to Sentry Seer
More in Code & Dev Tools
