Update pricing for size analysis GA#16157
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| - **Per-category:** Your on-demand budgets for categories such as errors, transactions, and replays, are set up individually so that any overages in one category won't consume the budget of another category. | ||
|
|
||
|  | ||
|
|
There was a problem hiding this comment.
Documentation image accidentally removed
Low Severity
The image reference for on-demand-budgets.png was removed from the "Shared and Per-Category On-Demand" section. This removal appears unrelated to the PR's stated purpose of updating size analysis pricing and likely wasn't intentional. The image provided visual guidance for understanding on-demand budget settings, and its removal reduces documentation clarity for users on legacy pricing plans.
sergical
left a comment
sergical
left a comment
There was a problem hiding this comment.
small nites, looks good to me tho
docs/pricing/legacy-pricing.mdx
Outdated
|
|
||
| #### Size Analysis | ||
|
|
||
| [Size Analysis](https://docs.sentry.io/product/size-analysis/) helps mobile development teams monitor and reduce mobile app size, which can help improve install and uninstall rates. It breaks down your mobile apps so you can see exactly where size is coming from, and surfaces insights that recommend specific fixes. Every organization has 100 size analysis builds that can be uploaded per billing period. Additional builds are only available through an Enterprise Plan. If you’d like to explore Enterprise plan options, email [[email protected]](mailto:[email protected]) to discuss pricing for additional builds. |
There was a problem hiding this comment.
i think we do relative links if it's inside docs to make sure preview branches dont point to prod
There was a problem hiding this comment.
Yeah good catch! This was copied from a notion doc and I missed it.
| #### Seer Pricing | ||
|
|
||
| [Seer](/product/ai-in-sentry/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 [on-demand 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 on-demand budget. |
There was a problem hiding this comment.
should this be to settings/seer/ as opposed to just settings?
There was a problem hiding this comment.
Good q, I'll follow up with the stakeholder.
There was a problem hiding this comment.
It should be this https://sentry.io/settings/seer/
| - Seer (available only through purchase of Seer) | ||
|
|
||
| On top of that, you can set aside a PAYG budget that can be used to send additional data in any category. Alternatively, you can choose to pay ahead of time to reserve additional volume at a discounted price. Any unused reserved volume will expire at the end of each billing month. | ||
| On top of that, you can set aside a PAYG budget that can be used to send additional data in applicable categories. Alternatively, you can choose to pay ahead of time to reserve additional volume at a discounted price. Any unused reserved volume will expire at the end of each billing month. |
There was a problem hiding this comment.
I can't tell if "applicable categories" are easy to infer. It'd be nice to know what that means.
docs/pricing/legacy-pricing.mdx
Outdated
| [Seer](/product/ai-in-sentry/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 [on-demand 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 on-demand budget. | ||
|
|
||
| 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. |
There was a problem hiding this comment.
| 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. | |
| Access Seer by turning it on in [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/) . Using Seer will add $40 per active contributor per month to your existing subscription, 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. |
sfanahata
left a comment
sfanahata
left a comment
There was a problem hiding this comment.
Left a recommendation for rewording, but otherwise, looks good!
Co-authored-by: Shannon Anahata <[email protected]>
3 participants
DESCRIBE YOUR PR
Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES