Frequently asked questions and answers for Seer effective January 21, 2026

What’s new with Seer?

How does Seer pricing change?

Seer will move to a per active contributor billing model, in which an active contributor is defined as any user that opens 2 or more PRs in a Seer-connected repository.

Under this model, there is no ability to reserve or limit active contributors on self-serve. Additionally, active contributors will not draw down from an org’s PAYG budget. Seer active contributors will be billed as its own monthly charge.

With the move to user-based pricing, we’ll no longer be billing based on event usage. This means orgs purchasing Seer gets *unlimited RCAs, Issue Fixes, and Code Reviews across any Seer-connected repo.

See current pricing here.

Do we pro-rate active contributors?

No. Active contributors will be charged at $40 per month, regardless of when they become active within the billing cycle.

For example, if a user authors their second PR in a Seer-connected repository on the last day of the billing cycle, they will still be charged at $40 per month.

How are we handling users who complain about their Seer bill?

Similar to other product SKUs, if someone writes in complaining about an unexpected Seer charge, we’ll waive the first instance and share education on how Seer pricing works.

The best mechanism to control spend is by ensuring only the intended projects and GitHub repos are connected to Seer.

What happens to orgs already paying for Seer?

Orgs who have purchased Seer will be given free, unlimited access to Code Review, in addition to their existing subscriptions, for a minimum of 1 billing cycle after Billing GA. Please see migration plan here.

Self-Serve Orgs

Orgs interested in moving to the new billing model can opt-in at the end of the grace period. For orgs who do not opt-in, they’ll lose access to Seer at the end of the 30 day period.

Orgs who do not have GitHub-connected repos will no longer be able to use Seer when the SKU changes at the end of their billing period. To continue using Seer, orgs will need to connect to GitHub.

Sales-Led Orgs

Please redirect to Sales for discussion.

How do we handle existing self-serve Seer orgs who want to migrate?

Orgs who want to migrate prior to the end of the GA can do this through checkout. Orgs will need to remove the SKU at checkout. This will still allow them to continue using Seer until the end of their monthly billing cycle.

Because orgs cannot have both billing models at the same time, they will have to wait until the end of their billing cycle until they can add new Seer. At this time, they’ll see the option to trial Seer and from here, they can follow the standard steps of trialing and adding Seer at checkout.

How do we handle existing Seer orgs who do not want to migrate?

Orgs who do not want to migrate can simply do nothing. At the end of the 30 day period, they’ll no longer have access to Seer.

What about orgs who purchased Seer on annual plans but do not want to migrate?

We will credit orgs who purchased Seer on an annual plan but do not opt-in to the new billing model for the remainder of their payment. Orgs who prefer a refund can write in to Support for help.

Are all repositories in our GitHub organization included in this PR calculation? If not, what repositories are included?
​

Orgs can choose which repos to connect to Seer. Only the contributors to those connected repos will count. If an individual contributes to multiple connected repos, they are only counted once.
Ex: if Acme connects 4 repos to Seer, and Joe is an active contributor to 3, he is still only counted at 1 active contributor.

Is Seer covered under BAA?

Yes, the Business Associate Agreement (BAA) applies to the Sentry service, including our Seer features.

One caveat: Sentry MCP is an experimental feature and is labelled accordingly.