How do I add Seer AI Debugger in Sentry, and how is “active contributor” counted for the $40/user/month add-on?

If you’re already using Sentry to track errors and performance, adding Seer AI Debugger is how you turn that production context into automated root cause analysis and AI-assisted fixes—without bolting on yet another tool. This guide walks through how to add Seer to your Sentry organization and how “active contributor” is counted for the $40/user/month add-on.

Quick Answer: You add Seer AI Debugger as an add-on to any paid Sentry plan (Team, Business, or Enterprise), then connect it to your GitHub repos. An “active contributor” is anyone who opens at least 2 PRs in a month on any repo connected with Seer; that count drives the $40/active contributor/month charge.

The Quick Overview

What It Is: Seer is Sentry’s AI debugger. It uses your existing Sentry context (errors, traces, commits, logs, profiling) to flag breaking changes, identify likely root causes, review code, and even propose fixes or open pull requests.
Who It Is For: Teams already sending production data to Sentry who want faster triage, AI-powered root cause analysis, and AI code review tied directly to their actual runtime behavior.
Core Problem Solved: When production breaks, it takes too long to connect “what users experienced” to “what changed in this deploy” and “where in the code it failed.” Seer reduces that guesswork by using Sentry’s telemetry to focus AI analysis on the real culprit.

How It Works

Seer sits on top of your existing Sentry setup. You send events to Sentry via SDKs as usual—errors, transactions (traces + spans), logs, Session Replay, profiling—and Seer uses that context plus your GitHub commits and pull requests to do three big jobs:

Flag potentially breaking changes.
Automatically analyze issues for root cause.
Review code and suggest (or generate) fixes.

Behind the scenes, Seer never uses your data to train its generative models by default and without your express consent, and AI-generated output from your data is only shown to your organization—not to other customers.

1. Add Seer to your Sentry plan

To use Seer, you need a paid Sentry plan (Team, Business, or Enterprise). Then:

Go to Organization Settings
- In Sentry, open the organization dropdown (top left) and go to Organization Settings.
Open Billing or Subscriptions
- Navigate to Billing or Subscriptions (name may vary slightly depending on your account and region).
Find Seer AI Debugger
- Under add-ons, locate Seer AI Debugger.
Enable Seer
- Turn it on for your organization.
- Pricing: $40 per active contributor per month for unlimited use.

If you don’t see Seer in your account, contact your Sentry admin or Contact Sales—it may need to be enabled for your region or plan.

Note: Some older docs mention a flat $20/month plus credits. The current model is the $40/active contributor/month add-on with unlimited usage, on top of Team, Business, or Enterprise.

2. Connect GitHub and configure Seer settings

Seer relies on your GitHub integration to understand code changes, pull requests, and who’s contributing.

Install the Sentry GitHub integration
- In Organization Settings → Integrations, find GitHub or GitHub Enterprise.
- Click Install or Configure.
- Grant Sentry access to the repositories you want Seer to analyze.
Enable Seer features in settings
- Go to Seer Settings (usually under Organization/Add-ons or a dedicated Seer section).
- Confirm which features you want:
  - AI Debugging / “Find Root Cause” in issues
  - AI Code Review on pull requests
  - Any gated workflows your org requires (e.g., per-project controls)
Scope repos for AI code review
- Choose which connected GitHub repositories should have AI code review turned on.
- You can start with a smaller repo or service if you want to try Seer before rolling it out org-wide.

AI code review is currently supported only on GitHub and GitHub Enterprise, not other CI or VCS providers.

3. Use Seer in your daily debugging workflow

Once Seer is enabled and GitHub is connected, you’ll see it in places you already work:

On issue detail pages (“Find Root Cause”)
- Open an issue in Sentry (error, performance problem, etc.).
- Click Find Root Cause to trigger Seer.
- Seer uses stack traces, spans, recent commits, logs, and profiling data to:
  - Identify the likely faulty commit or code path.
  - Explain the probable cause in plain language.
  - Suggest a fix strategy, sometimes down to code-level changes.
On GitHub pull requests (AI code review)
- When a contributor opens a PR in a repo connected to Seer:
  - Seer can analyze the diff in the context of Sentry data (recent errors, slow spans, etc.).
  - It surfaces potential regressions, anti-patterns, or risky changes.
  - It can propose code-level improvements or fixes and, in some flows, open or update PRs with suggested changes.
Across releases and deploys
- Seer can highlight breaking changes across deployments using Sentry’s release and changeset data.
- You get more than “this error spiked”—you see which code change likely caused it and who to pull in to fix it.

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
AI Root Cause Analysis	Uses Sentry issues (errors, spans, logs, profiling) to explain why it broke	Faster triage; less time reading stack traces and guessing
AI Code Review (GitHub)	Reviews PRs using Sentry context plus code diff	Catches risky changes earlier, before they hit production
Breaking Change Detection	Correlates new errors/slowdowns with recent commits and releases	Quickly ties incidents to the specific change and owner

Ideal Use Cases

Best for teams running multiple services and releases per day: Because it connects runtime failures (Sentry issues) to the exact PR and commit, so you don’t have to manually stitch together logs, traces, and git history.
Best for teams wanting AI help that’s grounded in real telemetry, not guesses: Because Seer only reasons over your actual Sentry data—errors, spans, replays, logs, profiling—plus your GitHub changes, instead of running blind on generic patterns.

Limitations & Considerations

GitHub-only for AI code review:
Currently, AI code review is only available on GitHub and GitHub Enterprise. If your code lives elsewhere, you still get issue-level AI debugging, but not PR review.
Plan + contributor-based pricing:
Seer is an add-on to Team, Business, or Enterprise Sentry plans and billed at $40 per active contributor per month. Budgeting should reflect both your Sentry plan and the number of active contributors (explained below).

Pricing & Plans

Seer AI Debugger is not a standalone product; it’s an add-on layered on top of Sentry’s existing plans.

Base requirement: You must be on a paid Sentry plan (Team, Business, or Enterprise).
Seer cost: $40 per active contributor per month, for unlimited Seer usage across:
- AI root cause analysis in Sentry issues
- AI code review on supported GitHub PRs
- Other Seer workflows tied to your Sentry data

How “active contributor” is counted

This is the part teams usually need clarity on for budgeting.

An active contributor is someone who:
- Opens at least 2 pull requests in a month
- On any repository connected with Seer via the GitHub integration
The count is per month, and:
- Only contributors who meet that “≥ 2 PRs” threshold in that billing period are counted.
- The number of active contributors is tallied at the end of each month’s billing cycle.
Billing example:
- If 15 distinct developers each open 2 or more PRs in Seer-connected repos in May:
  - You’re billed for 15 active contributors × $40 = $600 for May’s Seer usage.
- If a developer opens just 1 PR in a month, they do not count as an active contributor for that month.

This model is intentionally tied to actual contribution volume, not just number of Sentry users. If someone is in Sentry but not opening PRs in repos under Seer, they don’t drive Seer cost.

Sample billing scenarios

Small team, focused repo
- 5 engineers actively working in a single repo connected to Seer
- All 5 open ≥ 2 PRs in a given month
- Seer cost: 5 × $40 = $200/month
Large org, limited rollout
- 50+ engineers overall, but you turn Seer on for 2 critical services only
- In those services’ repos, 10 engineers open ≥ 2 PRs in a month
- Seer cost: 10 × $40 = $400/month (only actual active contributors in those repos)

Frequently Asked Questions

How do I actually turn on Seer in my Sentry project?

Short Answer: Add Seer in your Sentry organization’s billing/subscription page, then configure Seer Settings and make sure the GitHub integration is installed and scoped correctly.

Details:
From Organization Settings → Billing/Subscriptions, enable Seer AI Debugger as an add-on on top of your Team, Business, or Enterprise plan. Then go to Integrations to install or configure GitHub/GitHub Enterprise, granting access to the repos where you want AI code review. Finally, open Seer Settings to confirm which features are enabled and which repos are included. After that, you’ll see “Find Root Cause” on issue detail pages and AI review running on PRs in connected repos.

How is “active contributor” different from a Sentry user seat?

Short Answer: Sentry user seats control who can log in and work in Sentry; active contributors are people opening ≥ 2 PRs/month in Seer-connected repos and determine Seer’s $40/user/month pricing.

Details:
You might have more Sentry users than active contributors—or vice versa—depending on how your team works. A Sentry user could be a product manager or SRE who never opens pull requests; they won’t be counted as an active contributor for Seer. Conversely, a developer who opens multiple PRs in repos connected to Seer will count as an active contributor that month, even if they’re not the heaviest Sentry dashboard user. At the end of each billing cycle, Sentry counts the distinct contributors who opened 2+ PRs in Seer-enabled repos and bills $40 per active contributor for that month.

Summary

Adding Seer AI Debugger to Sentry gives you AI help that’s grounded in your real runtime data—stack traces, spans, commits, logs, profiling—not just generic code patterns. You enable it as an add-on to a paid Sentry plan, connect GitHub, and then use it directly from Sentry issues (“Find Root Cause”) and GitHub PRs (AI code review). Pricing is simple: $40 per active contributor per month, where an active contributor is anyone who opened 2 or more PRs in Seer-connected repos in that billing month.

If you’re already using Sentry to watch what breaks in production, Seer is the next step: it helps explain why it broke and how to fix it faster.

Next Step

Get Started