Skip to main content

Buyer guide

Seer Active Contributor Billing Checklist

What Seer costs per active contributor, which bots, agents and GitLab accounts count toward the bill, and who pays for coding-agent handoffs.

Reading time
2 min read
Sources
12 cited
In this piece
Seer+11 Mixed

Budget Seer from active GitHub pull request authors or every member of connected GitLab groups, and pay for coding-agent handoffs on the agent's own bill. Apply Sentry's host-specific billing rules before you connect more repositories.

When you need this

  • You are moving from a Seer trial to a paid subscription.
  • You were on Seer's legacy pricing from before January 2026.
  • Coding agents and bots open pull requests in the repositories you plan to connect.

Evaluation criteria

  1. Who is billed

    Who counts as an active contributor?

    Look forSeer charges US$40 per active contributor per month. On GitHub, an active contributor creates 2 or more pull requests in a Seer-enabled repository, and counts reset monthly. On GitLab, every group member counts. A repository becomes Seer-enabled when you connect it to Sentry and turn on any Seer feature.

  2. Bots and agents

    Do automated accounts count?

    Look forOn GitHub, Sentry excludes accounts marked [bot]. GitLab has no such exception, so a member still counts when Autofix or a bot opens the merge request. A coding agent that opens pull requests under an engineer's account carries no [bot] mark, so its pull requests count toward that engineer.

  3. Which repositories

    Which repositories start the meter?

    Look forTurning on any Seer feature for a repository, Code Review included, starts the per-contributor charge for it. Connect only the repositories where you will use Seer, and review the list whenever teams add repositories.

  4. Plan prerequisite

    Which Sentry plan do you need?

    Look forSeer needs a paid Sentry plan and bills its own monthly charge outside the pay-as-you-go budget. Team costs US$26 per month billed annually or US$29 monthly. Business costs US$80 or US$89. The free Developer plan excludes Seer.

  5. Handoff costs

    What does a coding-agent handoff add?

    Look forHandoffs run on the agent vendor's account, and the work appears on that vendor's bill. Claude Agent uses your Anthropic API key. GitHub Copilot consumes GitHub Actions minutes and AI credits. Cursor uses your Cursor API key.

  6. Legacy plans

    Are you still on per-run pricing?

    Look forBefore January 2026, Seer cost US$20 a month with US$25 in credits. Usage past the credits cost US$1 per issue fix run and US$0.003 per issue scan, charged to pay-as-you-go. In February 2026, a Deliverect QA lead reported going over budget after setting automation aggressively, and Sentry locked the lead out of Seer settings until the next billing period. Sentry closed that report as not planned in June 2026, so lower automation before a legacy plan's budget runs out.

Questions to ask vendors

  1. How many people opened 2 or more pull requests last month in the GitHub repositories we would connect?
  2. Which agents open pull requests under a personal account with no [bot] mark?
  3. Are any repositories on GitLab, where every group member counts?
  4. Which coding-agent handoff will we use, and whose budget pays for it?
  5. What would our own triage pipeline cost in agent seats and maintenance?

Red flags

  • Code Review turned on for every repository during a trial, with no list of who opens pull requests there.
  • Coding agents opening pull requests under engineers' accounts in Seer-enabled repositories.
  • Automatic handoff to a coding agent with no budget owner at the agent's vendor.
  • Comparing Seer's US$40 with an agent seat without counting the engineering time to build and run your own triage pipeline.

Products in this piece

Sources

Official documentation
9
Public source
3
  1. Sentry docs: Pricing & Billing (Seer pricing)Official documentationdocs.sentry.io
  2. Sentry pricingOfficial documentationsentry.io
  3. Sentry: Seer product page and FAQOfficial documentationsentry.io
  4. Sentry blog: Seer, debug with AI at every stage of development (Jan 27, 2026)Official documentationblog.sentry.io
  5. Sentry docs: SeerOfficial documentationdocs.sentry.io
  6. Sentry docs: Code ReviewOfficial documentationdocs.sentry.io
  7. Sentry docs: Claude AgentOfficial documentationdocs.sentry.io
  8. Sentry docs: GitHub Copilot AgentOfficial documentationdocs.sentry.io
  9. Sentry docs: Cursor AgentOfficial documentationdocs.sentry.io
  10. getsentry/sentry issue #107592: Cannot configure Seer when out of budget (Feb 4, 2026)Public sourcegithub.com
  11. erwins-enkel Shepherd issue #2467: Sentry auto-fix as a Seer replacement (Sep 24, 2026)Public sourcegithub.com
  12. getsentry/sentry issue #93724: Seer GitLab integration (Jun 17, 2025 to Jul 23, 2026)Public sourcegithub.com