diff --git a/docs/pricing/index.mdx b/docs/pricing/index.mdx index 6e372ff85b1ada..d19bb6413e157c 100644 --- a/docs/pricing/index.mdx +++ b/docs/pricing/index.mdx @@ -143,31 +143,14 @@ All Sentry plans include one cron monitor and one uptime monitor. Additional mon #### Seer Pricing -Seer is Sentry's AI agent that triages, debugs, and fixes application issues automatically. Access Seer by adding it to your existing subscription for an additional $20 per month. This $20 gives you $25 worth of Seer event credits, which can be used for any combination of [Issue Scans](/pricing/#issue-scans) or [Issue Fixes](/pricing/#issue-fixes) (see pricing tables below). Any usage beyond this $25 credit will draw from your [PAYG budget](/pricing/#terminology). +Seer is Sentry's AI debugging agent. It catches breaking changes before deploy and debugs and fixes issues in production. Access Seer by enabling it on your existing subscription in [settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/). Seer usage is billed separately as its own monthly charge and does not count against your PAYG budget. -{/* More details on how to understand your Seer usage is available here. */} -{/* TODO: Add line above when the link is available */} +Access Seer by adding it to your existing subscription for $40 per active contributor per month, where an active contributor is defined as any user who makes 2 or more PRs to a [Seer-connected repository](/organization/integrations/source-code-mgmt/github/#seer). At the end of the month, contributor counts reset. -#### Issue Scans -Issue Scan automatically classifies and triages issues to determine which are the most likely to be fixable with a code change. Issue Scans are billed per run. - -| Issue Scan Volume | Team PAYG | Business PAYG | -| ----------------- | ------------- | ------------- | -| >0-10k | $0.0030000 | $0.0030000 | -| >10k-100k | $0.0027000 | $0.0027000 | -| >100k-500k | $0.0024300 | $0.0024300 | -| >500k | $0.0021870 | $0.0021870 | - -#### Issue Fixes - -Issue Fix performs a deep root cause analysis of an issue, using all of the context that is available to Sentry, generating a code fix, and opening a Pull Request in Github. - -Issue Fixes are billed per run. Interactions with the same run will only be billed once; restarting a run with the "Start Over" button will be billed as a separate run. - -| Team PAYG | Business PAYG | -| ------------- | ------------- | -| $1.00/run | $1.00/run | +| Team | Business | +| ---------------------- | ---------------------- | +| $40/active contributor | $40/active contributor | diff --git a/docs/pricing/quotas/manage-seer-budget.mdx b/docs/pricing/quotas/manage-seer-budget.mdx index d41947cfc4dcf3..a008fcba4d9283 100644 --- a/docs/pricing/quotas/manage-seer-budget.mdx +++ b/docs/pricing/quotas/manage-seer-budget.mdx @@ -1,98 +1,33 @@ --- -title: Manage Your Seer Budget +title: Manage Your Seer Spend sidebar_order: 40 description: >- - Understand where and how to manage your Seer budget, see which projects are - consuming more than others, and how to increase or decrease your spend. + Understand where and how your Seer spend is affected. og_image: /og-images/pricing-quotas-manage-seer-budget.png --- - [Seer](/product/ai-in-sentry/seer/) is only available when purchased - as an add-on while on a Team or Business plan. Once Seer has been purchased, - your subscription will have $25 worth of Seer budget to be used across issue - scans and issue fixes. + [Seer](/product/ai-in-sentry/seer/) is only available when added to an existing Team or Business plan. Once Seer has been added, each [active contributor](#key-terms) will be charged at $40 per seat. Counts reset at the end of each month. ## Key Terms -- **Seer Budget**: The initial budget your subscription has allocated to be used exclusively by Seer products. This includes issue scans and issue fixes. +- **Seer**: Sentry's AI debugging agent that catches breaking changes before deploy, and debugs and fixes issues in production. -- **Pay-As-You-Go (PAYG) Budget**: A budget you set to pay for additional issue scans and fixes beyond your Seer budget. - -- **Issue Scan**: An analysis of an issue to help determine fixability. These scans are run automatically for every new error and performance issue. - -- [**Issue Fix**](/product/ai-in-sentry/seer/issue-fix/): A root cause and solution generated for an issue. You will only be charged one fix per issue, however if you "Start Over" your fix, this will count as a new fix and will be charged accordingly. - -- [**Seer Automation**](/product/ai-in-sentry/seer/#automation): Settings that combine issue scans and fixes into a powerful workflow: identifying actionable issues in real time and generating high quality fixes automatically. These options help manage Seer and PAYG spend by letting you choose when to run scans, which issues trigger fixes, and how far fixes progress (from root cause analysis to opening a pull request). - -## Before You Begin: Check Your Seer Usage - -You can look at your Seer usage in the [Usage Stats tab](/product/stats/#usage-stats) to understand the breakdown of your issue fixes and issue scans by time window and project. This may help you figure out where you need to further fine-tune your usage. - -This page is accessible to all members of your organization, so Owners in your Sentry org will be able to share it with the developers directly responsible for a given project. You'll also be able to use this page to assess whether your changes are working as intended. - -### How Can I See a Breakdown of Incoming Issue Scans and Fixes? - -The Usage Stats tab displays details about the total amount of data Sentry has received across your entire org for up to 90 days. The page breaks down the events by project into three categories: accepted, dropped, or filtered. Only accepted scans and fixes affect your budget: - -![Stats and Usage page example](./img/manage-seer-budget-01.png) - -### Which Projects Are Consuming My Seer Spend? - -The "All Projects" table on the Stats page breaks down your data by project, so you can identify the ones that are consuming the most budget. Clicking on the settings icon next to a project name in the table will open that project's settings page, where you can manage its Seer scan and automatic analysis settings. - -## Adjusting PAYG Budget - -Budgets can only be updated by a Billing- or Owner-level member of your Sentry org. - -Once your Seer budget is approaching or has exceeded its included budget, teammates with "Owner" org permissions will start receiving [notification](/product/alerts/notifications/#quota-notifications) emails. They'll then be able to choose to increase or decrease the PAYG budget to unlock additional usage. - -### Increasing Seer Budget - -If Issue Scans have stopped running or you're not able to initiate new Issue Fixes because you've exceeded your Seer budget, you can add to your budget at any time during your billing period by increasing your PAYG budget. This is ideal in situations where you're rolling out a new version of your application, for example. To add PAYG budget, set a monthly maximum shared budget in your [Subscriptions Page](https://sentry.io/orgredirect/organizations/:orgslug/settings/billing). - -[Learn more about setting your PAYG budget](/pricing/#pricing-how-it-works). +- **Active Contributor**: any user who makes 2 or more PRs on a Seer-connected repository. Users who contribute to more than one connected repository will still count as only one seat. ## Tips for Managing Spend -- Manage Automation Settings: Automation of issue scans and fixes will be the primary driver to Seer spend. Make sure you understand how automation may increase or decrease the number of scans and fixes across your projects. - -- Adjust Budget as Needed: If you anticipate needing more issue scans or fixes, consider increasing your PAYG budget beforehand. +Seer usage is billed separately as its own monthly charge and does not deduct from your pay-as-you-go budget. To avoid unexpected bills, keep an eye on the following: -- Monitor Your Usage: Regularly check your [Seer usage](/product/stats/#usage-stats) and PAYG budget to avoid unexpected bills. +- Manage Seer-Connected Repositories: Only active contributors on Seer-connected repos get counted towards your Seer invoice. To see which repos are connected to Seer, navigate to your organization's [settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/). -### Seer Fix and Scan Automation Settings - -Adjusting automation ensures issues are consistently ready for review, while also helping you manage your Seer and PAYG budget. Automation in Seer is the set of controls that determine how issues are automatically scanned, flagged, and fixed across your projects. Located in **Settings > Seer Automation**, these settings let you: - - - Enable or disable automatic issue scans: Seer will scan all new and ongoing issues, flagging the most actionable ones, enriching Slack alerts with additional context, and preparing issues for automated fixes. - - - Customize auto-triggered fixes: Choose to trigger fixes for all issues or only the most actionable, and refine the stopping point--from generating a root cause analysis to drafting a solution, or even opening a pull request automatically. - -Automation will run based on available Seer or PAYG budget. Once both budgets have depleted, Seer will stop running issue scans and fixes unless additional budget is made available or the billing cycle resets. - -If you find that you're running out of your Seer or PAYG budget too quickly, you can double-check your project's Seer automation settings. To ensure new projects are in check, you can also update the default settings for new projects. For more details on choosing the right automation settings for you, visit the [Automation Settings docs](/product/ai-in-sentry/seer/#automation). +- Monitor Your Usage: Regularly check your connected repos and active contributors to avoid unexpected bills. ## Example Scenario Let's illustrate how this works: -1. **Seer Budget:** - - By purchasing Seer, you get $25 of Seer credit each month. This credit is dedicated to Seer usage (issue scans and fixes). - - You also have added $100 to your shared PAYG budget that covers all Sentry events, including any Seer usage that exceeds your monthly credit. -2. **Issue Scans:** - - Automatic issue scans is enabled, meaning every new issue created triggers a scan automatically. - - In this billing cycle, let's suppose 1,000 new issues are created, which means 1,000 scans are run. - - The total issue scan cost is $3. -3. **Issue Fixes:** - - Your issue fix automation is set to "Highly Actionable and Above". - - Of the 1,000 issues scanned, 50 are identified as "Highly Actionable and Above". As soon as the issue is classified, Seer automatically creates RCAs and suggested fixes for these 50 issues so that they are immediately available for your review. - - The total issue fix cost is $50. -4. **Seer Bill:** - - - Total Seer usage: $3 (scans) + $50 (fixes) = $53. - - $25 is covered by your monthly Seer Credit. - - The remaining $28 is charged to your shared PAYG budget, alongside any other Sentry event overages. +You have a total of 10 GitHub repositories, 5 of which are connected to Seer. Across the 5 Seer-connected repos, there are a total of 10 users who have made 2 or more PRs within the monthly billing period. At the end of the billing period, you will be charged a total of $400 (10 active contributors x $40). - By understanding how Seer automation and billing works, you can effectively manage your Seer budget and usage. +In the next billing period, you continue to have 5 Seer-connected repositories but only 3 users made 2 or more PRs. At the end of the monthly billing period, you will be charged a total of $120 (3 active contributors x $40).