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

Most teams meet Seer the same way: someone clicks “Find Root Cause” on an issue, likes what they see, and then asks, “Okay, how do we turn this on for everyone, and what does $40 per ‘active contributor’ actually mean?” This guide walks through how to add Seer to your Sentry account and how billing works so there are no surprises at the end of the month.

Quick Answer: Seer AI Debugger is a paid add-on for Sentry (Team, Business, and Enterprise plans) that costs $40 per active contributor per month. An “active contributor” is anyone who opens at least 2 pull requests in a month on any repo connected to Seer.

The Quick Overview

What It Is: Seer is Sentry’s AI debugger. It uses your Sentry data (errors, spans, commits, logs, profiling, replays) to flag breaking changes, run root cause analysis, and even propose fixes and open PRs.
Who It Is For: Engineering teams already using Sentry for Error Monitoring and Tracing who want to cut down the time from “alert fired” to “fix merged,” and teams who want AI-assisted code review wired into their existing GitHub/GitHub Enterprise workflow.
Core Problem Solved: When production breaks, Seer pulls together the context you already send to Sentry and uses it to identify likely root causes and fixes—without your team manually stitching stack traces, spans, and commits together.

How It Works

At a high level, you connect Seer to your Sentry organization and (optionally) your GitHub repos. Sentry’s SDKs continue sending events like they do today—errors, transactions, spans, logs, Session Replays, profiling data. Seer then uses that context to analyze issues, identify suspect changes, and help you fix problems faster.

Once enabled, you’ll see Seer entry points directly inside Sentry:

On issue detail pages (e.g., an error or performance issue) via actions like “Find Root Cause”
In code review flows for GitHub/GitHub Enterprise pull requests
In debugging workflows where Seer can suggest fixes or open PRs

Behind the scenes, Seer uses the same data you already trust Sentry with: encrypted at rest and in transit, hosted on Google Cloud Platform, and governed by the same privacy and security controls (SOC 2 Type II, ISO 27001, HIPAA attestation, US or Germany data residency).

1. Enable Seer on a Supported Plan

To add Seer AI Debugger, you need to be on a paid Sentry plan:

Team
Business
Enterprise

Seer is not available on the free Developer plan.

From there:

Sign in to Sentry as an organization owner or admin.
Go to Settings → Billing (or Subscriptions, depending on your account view).
Find the Seer AI Debugger add-on.
Click Add (or Enable), confirm pricing ($40/active contributor/month), and update your subscription.

Seer is an add-on to your existing Sentry plan—quotas and billing for events, spans, replays, etc., stay as configured; Seer is charged separately based on active contributors.

2. Configure Seer Settings in Sentry

Once the add-on is active:

Go to Settings → Organization → Seer (or AI section, depending on UI version).
Open Seer Settings.
Configure:
- Which projects Seer can access
- Which features you want to use (e.g., root cause analysis on issues, AI-assisted fixes)
- Any guardrails or approval flows your team requires

This lets you roll out Seer gradually—start with one critical project or team, then expand once you’ve validated the workflow.

3. Connect GitHub for AI Code Review (Optional but Recommended)

Seer supports AI code review on:

GitHub
GitHub Enterprise

Currently, AI code review is only available for these Git systems—other CIs or SCMs are not supported for Seer’s code review feature.

To connect:

In Sentry, go to Settings → Integrations → GitHub (or GitHub Enterprise).
Click Install or Configure and follow the OAuth/app installation flow.
Ensure the integration is installed on the repos where your team opens PRs.
Confirm in Seer Settings that AI Code Review is enabled and linked to the appropriate projects/repos.

Once this is done, Seer can analyze pull requests, use Sentry context (recent errors, performance regressions, suspect commits), and comment on potential issues before they hit production.

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
Root Cause Analysis	Uses Sentry context (stack traces, spans, commits, logs, profiling) to find likely causes of an issue.	Cuts down time spent guessing why something broke in production.
AI Code Review for GitHub	Reviews PRs on GitHub/GitHub Enterprise using live Sentry telemetry and history.	Catches risky changes before deploys, tied to real production behavior.
AI-Assisted Fixes & PRs	Suggests fixes and can open pull requests with proposed changes.	Moves from “we know the bug” to “we shipped the fix” faster.

Ideal Use Cases

Best for teams who already rely on Sentry for production debugging: Because Seer is only as useful as the context it sees. If you’re sending errors, traces, logs, replays, and profiling to Sentry, Seer can stitch that together into concrete root cause hypotheses and fix suggestions.
Best for teams with GitHub-centric workflows: Because AI code review is currently supported only on GitHub and GitHub Enterprise, and Seer’s pull request analysis hooks directly into those workflows.

Limitations & Considerations

Plan requirements: Seer is an add-on for Team, Business, and Enterprise plans. If you’re on the free Developer plan, you’ll need to upgrade to enable Seer.
GitHub-only code review: AI code review is only available on GitHub and GitHub Enterprise. If your CI/SCM is elsewhere, you can still use Seer’s in-app debugging, but not AI PR review.
Active contributor billing model: Seer pricing is per active contributor, not per Sentry seat. This is good for teams with many Sentry users but fewer active PR authors, but it does mean you should understand how “active” is defined (more on that below).

Pricing & Plans

Seer is priced as:

$40 per active contributor per month
Add-on to Team, Business, or Enterprise plans
Unlimited use per active contributor (no per-run fee for Seer features)

In practice:

Your Sentry base plan (Team/Business/Enterprise) covers your event/spans/replay/profiling quotas and core features.
Seer is billed separately based on the number of people who meet the “active contributor” threshold in that month.

How “Active Contributor” Is Counted

This is the key part for budgeting and explaining costs internally.

Definition: An active contributor is someone who opens at least 2 pull requests in a month on any repo connected with Seer.

The counting rules:

Scope: Repositories connected through the Sentry–GitHub or GitHub Enterprise integration and accessible to Seer.
Threshold: A user becomes an active contributor when they open 2 or more PRs in the billing month.
Identity: Contributors are mapped based on their GitHub identity for connected repos; they don’t have to be Sentry org owners/admins to be counted.
Billing moment: The number of active contributors is calculated and billed at the end of each month’s billing cycle.

Some concrete examples:

Example 1: Single contributor
- Alice opens 3 PRs this month on a repo connected to Seer.
- She qualifies as an active contributor.
- You are billed $40 for Alice for this month.
Example 2: Multiple contributors
- Alice opens 3 PRs.
- Bob opens 1 PR.
- Carol opens 2 PRs.
- Alice and Carol are active contributors; Bob is not.
- You are billed 2 × $40 = $80 for Seer this month.
Example 3: New team member mid-month
- Dave joins mid-month and opens 2 PRs after being added to the repo.
- Dave is an active contributor for that month and will be counted in the bill.

If you want to estimate Seer cost before rolling it out widely, look at how many developers typically open ≥2 PRs/month on your GitHub repos connected to Sentry.

Frequently Asked Questions

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

Short Answer: Make sure you’re on a Team, Business, or Enterprise plan, add the Seer AI Debugger add-on from Billing/Subscriptions, then configure Seer settings and (optionally) install the GitHub integration for AI code review.

Details:
From the Sentry UI:

Confirm your org is on a Team, Business, or Enterprise plan.
Navigate to Settings → Billing and locate the Seer AI Debugger add-on.
Click Add/Enable and confirm the $40/active contributor/month pricing.
After activation, open Settings → Organization → Seer (or equivalent AI settings).
Configure which projects Seer can access and which features to enable.
For AI code review, go to Settings → Integrations → GitHub/GitHub Enterprise and install/configure the integration on your repos.
Confirm Seer appears on issue detail pages (e.g., “Find Root Cause”) and in your GitHub PRs where applicable.

Once configured, your developers can start using Seer immediately, and active contributor tracking will begin for the current billing cycle.

Will Seer use my production data to train external AI models?

Short Answer: No. Your data is not used to train generative AI models by default or without your explicit consent, and AI-generated output from your data is only shown to you.

Details:
Seer runs on top of the same security and privacy posture as the rest of Sentry:

Data is encrypted with AES‑256 at rest and protected with TLS in transit.
Sentry is hosted on Google Cloud Platform, with annual third‑party penetration testing.
Sentry maintains SOC 2 Type II and ISO 27001 certifications and has HIPAA attestation.
You can choose data residency in the United States or Germany.

Specifically for AI features:

Your Sentry data will not be used to train any generative AI models by default and without your explicit consent.
AI-generated outputs that Seer produces from your data are visible only to your organization, not to other Sentry customers.

If you’re in a regulated environment, point your security team to Sentry’s AI privacy and security documentation for the full details.

Summary

Adding Seer AI Debugger to Sentry is straightforward: switch to (or confirm you’re on) a Team, Business, or Enterprise plan, add the Seer add-on, configure Seer settings, and hook up GitHub or GitHub Enterprise if you want AI code review. From there, Seer uses the telemetry you already send to Sentry—errors, traces, logs, replays, profiling, and commits—to flag breaking changes, analyze root causes, and help you ship fixes faster.

Billing is predictable once you understand the model: Seer costs $40 per active contributor per month, where an active contributor is anyone who opens at least 2 PRs in a month on a repo connected to Seer. That keeps the focus on the developers actively changing your code, not every Sentry user.

Next Step

Get Seer running in your own Sentry org and see how much debugging time you can save:
Get Started