Sentry’s usage-priced products are the offerings that sit beside the main error and tracing allowances. Some are included in small amounts on every plan and then bought through the pay-as-you-go (PAYG) budget; others, notably Seer, are separate charges. The pricing documentation says that logs, application metrics, profile hours and additional monitors can be purchased only with the PAYG budget, that the Seer add-on is billed separately, and that size analysis builds above the included number need an Enterprise plan.[1] The same documentation lists “continuous profiling (available only through PAYG)” and “UI profiling (available only through PAYG)” as not part of the preset included volume.[1]
Editions
These products are available on Team, Business and, with custom volumes, Enterprise. The comparison on the pricing page shows logs, application metrics, uptime and cron monitoring, and size analysis on all four plans, with the Developer plan holding the same base allowances as the paid plans (5GB of logs and application metrics, one monitor of each kind, 100 size analysis builds).[7] Seer is described as an add-on subscription for Team and Business plans.[1] The feature lines under Seer on the pricing page are root cause analysis, fix generation, and error prediction and code review, marked as at an additional cost.[7]
Metrics
Seer
Seer is Sentry’s AI debugging agent, which catches breaking changes before deployment and debugs and fixes issues in production.[1] It is accessed by enabling it on an existing subscription. Seer usage is billed as its own monthly charge and does not count against the PAYG budget.[1]
The metric is the active contributor: any user who makes two or more pull requests to a Seer-enabled repository. A repository is Seer-enabled when it is connected to Sentry and has one or more Seer features enabled.[1] Each active contributor costs $40 per month on both Team and Business.[1] Contributor counts reset at the end of each month.[1] A user who contributes to more than one connected repository counts as one seat.[2] See Seer active contributor and Seer add-on.
The documentation gives a worked example: with 10 GitHub repositories, five of them connected to Seer, and 10 users with two or more pull requests in the month, the charge is $400; if only three users reach two pull requests the next month, it is $120.[2] The counting rules differ by source-code host:[1]
- For GitHub, all members of the repositories except GitHub bots marked as [bot] are counted as active contributors.
- For GitLab, all accounts (group members) are counted as active contributors, even when using Autofix or bots for fixes.
The Seer spend page states a narrower rule for GitLab: pull requests created by Seer and Seer Autofix are counted as active contributors.[2] The two pages differ in wording, so the customer should confirm with Sentry how its host and repository membership are counted. Sentry advises managing Seer-enabled repositories, because only active contributors in those repositories count, and checking the active contributors shown in the organization’s billing overview.[2]
Seer has a trial, started from Organization Settings > Subscription, from the issue details page or from the Seer settings page. Sentry states that Seer does not use application data, error information or source code to train AI models, and that generated output is shown only to members of the organization.[1] Seer and other AI and machine learning features are not available in self-hosted Sentry, where they are described as currently closed source.[9]
Legacy Seer pricing
As of January 2026 legacy Seer pricing is no longer offered as an add-on. A customer that subscribed before January 2026 is likely on legacy pricing of $20 per month per Sentry subscription plus $25 of Seer event credits, usable for any combination of Issue Scans or Issue Fixes. Usage beyond the credit draws from the PAYG budget.[1] Issue Scans, which classify and triage issues, are billed per run in tiers from $0.0030000 down to $0.0021870 per scan as volume rises. Issue Fixes are billed at $1.00 per run, with interactions in one run billed once, and restarting with “Start Over” billed as a separate run.[1] See Seer legacy subscription and Seer issue fix run (legacy). The legacy pricing page adds that Seer and logs are available only through a shared PAYG budget.[6]
Logs and application metrics
Logs and application metrics are each priced per GB. Every plan includes 5GB of each, and additional usage can only be purchased with the PAYG budget at $0.50 per GB on Team and Business.[1] Logs are structured log entries from applications; application metrics are counters, gauges and distributions, and each metric event is trace-connected.[8] Both are counted individually and not grouped into issues.[8] Once the included quota is exceeded the customer is charged against the PAYG budget.[4][5] The metrics documentation notes that high-cardinality custom attributes, such as user or request IDs, inflate volume.[5]
Profiling
Profile hours are determined by the length of the profile in milliseconds and are billed in hours, with partial hours prorated and rounded down to the nearest cent. They can only be bought through the PAYG budget.[1] The rates are $0.0315 per hour for continuous profiling and $0.25 per hour for UI profiling on both Team and Business. Transaction-based profiling is billed under either UI or continuous profile hours by extracting the duration from the samples that make up the profile.[1] See Continuous profile hour and UI profile hour. On legacy plans, transactions with profiling enabled count as 1.3 performance units instead.[6]
Cron and uptime monitors
All plans include one cron monitor and one uptime monitor. Additional monitors can only be purchased with the PAYG budget, at $0.78 per cron monitor and $1.00 per uptime monitor.[1] The pricing page lists the uptime charge as “per uptime alert additional”.[7] See Cron monitor and Uptime monitor.
The monitor documentation sets out the counting mechanics.[3]
- When a monitor is added or reactivated, Sentry first looks for reusable quota from monitors of the same type that were deactivated or deleted in the same billing period; if found, the monitor is activated at no extra cost. Otherwise reserved quota or PAYG budget is used.
- Deactivated or deleted monitors still count toward the billing quota if they were active earlier in the current billing period.
- At the start of each billing period all quotas reset, reusable quota is lost, and monitors are re-evaluated. With sufficient budget, active monitors stay active; without it they may be automatically deactivated. Manually deactivated or deleted monitors stay that way.
- The documentation’s example is an organization with one reserved monitor and PAYG for five, running six monitors. After the period resets it pays the PAYG charge for the five additional monitors only.
The practical point is that churn within a month is free to rebalance, but headcount of monitors at the start of a new period is what the budget must cover.[3]
Size analysis
Size analysis, a feature for mobile development teams to monitor and reduce app size, gives every organization 100 builds that can be uploaded per billing period. Additional builds are only available through an Enterprise plan, with pricing agreed through sales.[1] See Size analysis build. The pricing page shows unlimited build monitors alongside the 100 builds.[7]
Programs
Product trials apply to these products. A one-time 14-day product trial is available for each product not already in the customer’s plan, during which events are unlimited and trial usage is not billed.[1] Seer has its own trial.[1] The PAYG budget can be shared or, for some organizations, set per category, although Seer and logs are only available through a shared budget on legacy plans.[6]
Practical points for asset managers
- Seer is the one Sentry charge that behaves like a named-user licence, because it counts people who contribute to enabled repositories. Reconcile the active contributor count with the repositories connected to Seer each month.[2]
- Check whether Seer is on current ($40) or legacy ($20 plus credits) pricing, since legacy plans can no longer be newly added.[1]
- Confirm that PAYG is set high enough for profiling, additional monitors and logs. Without a budget these cannot be used beyond the free allowances.[1]
- Review the monitor list at the start of each billing period, as monitors may be deactivated if budget is short.[3]
Out of scope
Reserved volume, the tiers for errors, spans and replays, and plan prices are covered in Sentry plans, reserved volume and pay-as-you-go. Quota counting for errors and spans is in Sentry quota counting, Spike Protection and rate limits.