Skip to content

Commit ced7d21

Browse files
authored
Revert "Update pricing.mdx (#6264)" (#6278)
This reverts commit 6d3de18.
1 parent f2b7b58 commit ced7d21

File tree

1 file changed

+59
-78
lines changed

1 file changed

+59
-78
lines changed

src/docs/product/accounts/pricing.mdx

Lines changed: 59 additions & 78 deletions
Original file line numberDiff line numberDiff line change
@@ -8,28 +8,65 @@ redirect_from:
88
description: "Learn about pricing variables, managing volume, and different Sentry plans."
99
---
1010

11-
This page gives you an in-depth understanding of our pricing and billing structure, including:
11+
This page clarifies concepts around pricing and billing like:
1212

13-
- [How our pricing works](#pricing-how-it-works) and [per-category-pricing](#per-category-pricing)
1413
- [Reserved (prepaid)](#prepaid-reserved-capacity) and [on-demand](#on-demand-capacity) volume
14+
- [How our pricing works](#pricing-how-it-works), including [pricing tables](#pricing-tables)
1515
- [Billing periods](#billing-cycles)
1616
- [Taxes](#taxes) and [exemptions](#tax-exemptions)
1717

18+
## Volume {#capacity}
19+
20+
Your _volume_ is the total number of [events](/product/sentry-basics/key-terms/) and attachments — or the total amount of [data](/product/sentry-basics/key-terms/) — sent by and billed to your organization. You can purchase volume in two ways: [prepaid (or reserved)](#prepaid-reserved-capacity) and [on-demand](#on-demand-capacity).
21+
22+
### Prepaid (Reserved) Volume {#prepaid-reserved-capacity}
1823

19-
## Pricing: How It Works
24+
_Reserved_ volume (or quota) allows you to prepay for data at significant discounts. Your prepaid, reserved volume is always applied before on-demand volume. Unused reserved volume expires at the end of each billing month.
2025

21-
We bill based on the amount of data you want us to process. Our [Developer, Team, and Business plans](https://sentry.io/pricing/), each come with a pre-set number of events (such as errors and transactions) that are included in the price.
26+
Every Sentry account includes a varying amount of reserved volume. For example, our Team plan includes a minimum of 50k errors, 100k transactions, and one GB of attachments per month:
2227

23-
On top of that, you can choose to pay for a set, prepaid volume of additional data at a discounted price. You can also set aside an on-demand budget to cover potential overages, which will only be used once the prepaid budget has run out.
28+
![Reserved Volume settings in Subscriptions](reserved-volume.png)
29+
30+
To see prepaid pricing per volume tier, check out our [pricing tables](#pricing-tables).
31+
32+
### On-Demand Volume {#on-demand-capacity}
2433

25-
- **[Prepaid volume:](#prepaid-reserved-capacity)** A predetermined amount of data you pay for in advance at a discount, on a monthly or annual basis.
26-
- **[On-demand volume:](#on-demand-capacity)** An overage budget that kicks in only if your prepaid volume has been used up. Having this makes it possible to control the maximum amount you will spend for overages each month.
34+
_On-demand_ volume is billed at the end of each billing month. You are charged per processed event or attachment, rounded up to the nearest cent. Your on-demand volume is determined by your [on-demand budget](#on-demand-cap) (or quota), which can be configured on either a shared or per-category basis. By setting on-demand budgets, you can control the maximum amount you'll pay for on-demand volume each month. Once your usage has consumed the maximum budget volume, you'll still be able to access prior event data, however, any additional data you send will be rejected.
2735

28-
If you run out of **both** your prepaid and on-demand volume, any new data you send will be rejected and you won’t be charged for it.
36+
To see on-demand pricing per volume tier, check out our [pricing tables](#pricing-tables).
37+
38+
#### On-Demand Budgets {#on-demand-cap}
39+
40+
Organizations on all plans have the option to set a shared on-demand strategy. Organizations on plans with [performance monitoring](/product/performance/) features have the ability to choose between a shared or per-category on-demand strategy:
41+
42+
- **Shared:** Your on-demand budget is shared among errors, transactions, and attachments.
43+
44+
- **Per-category:** Separate on-demand budgets for errors, transactions, and attachments. Any overages in one category will not consume the budget of another category.
45+
46+
![On-Demand Budgets settings in Subscriptions](on-demand-budgets.png)
2947

30-
### Per-Category Pricing
48+
If you raise your on-demand budget mid-month, your organization will start accepting additional data as soon as your new budget is applied. If you lower your on-demand budget mid-month to below the current month's usage, your on-demand budget will be reduced to match your usage. On your next bill date, your on-demand budget will be lowered to the requested amount.
3149

32-
If you'd like to buy either prepaid or on-demand data on top of what's included in your plan, you can buy as much as you think you'll need per data category. [Errors](#errors-pricing), [Transactions](#transactions-pricing), [Replays](#replays-pricing), and [Attachments](#attachments-pricing), each have their own unique pricing structures, as listed in the tables below:
50+
After a new budget is in effect, all additional data will be rejected and no additional on-demand volume will be added. At the end of the billing month, you will be charged for any on-demand volume consumed.
51+
52+
We guarantee new budgets will be applied and effective within 24 hours. However, in most cases the new budget will be applied within minutes.
53+
54+
## Pricing: How it Works
55+
56+
Our pricing model is similar to the way that you purchase data for a cell phone:
57+
58+
- We bill you for [prepaid volume](#prepaid-reserved-capacity) monthly or annually.
59+
- You can also set up an [on-demand budget](#on-demand-capacity) for possible overages, which is priced differently.
60+
61+
You're only billed for on-demand volume if you use it. If you run out of prepaid and on-demand volume, then we drop events and attachments, and you're not billed for that data.
62+
63+
To determine your on-demand pricing, start at the tier where your prepaid purchasing ends. For example, you've purchased 500k of reserved errors, with an on-demand budget of $25, on a Team plan. If you use 600k errors, you would pay for 500k prepaid errors at $0.000175/each and 100k on-demand errors at $0.000195/each, using $19.50 of your on-demand budget.
64+
65+
In another scenario, you've purchased 400k reserved errors with an on-demand budget of $25 on a Team plan. If you use 500k errors in total, you you would pay for 100k at $0.00029/each, the next 300k at $0.000175/each, and 100k on-demand errors at $0.000228/each, using $22.80 of your on-demand budget.
66+
67+
### Pricing Tables
68+
69+
We have three tables for [errors](#errors-pricing), [transactions](#transactions-pricing), and [attachments](#attachments-pricing) pricing:
3370

3471
<!-- prettier-ignore-start -->
3572

@@ -56,14 +93,6 @@ If you'd like to buy either prepaid or on-demand data on top of what's included
5693
| >10M-15M | $0.000039 | $0.000051 | $0.000074 | $0.000096 |
5794
| >15M-100M | $0.000027 | $0.000036 | $0.000040 | $0.000053 |
5895

59-
#### Replays Pricing
60-
61-
| Total Replays Volume | Prepaid Buckets | Team/Business Prepaid | Team/Business On-Demand |
62-
|---|---|---|---|
63-
| >10k-25k | 15k | $0.002850 | $0.003705 |
64-
| >25k-100k | 25k | $0.002850 | $0.003705 |
65-
| >100k-1M | 100k | $0.002565 | $0.000195 | $0.003335 |
66-
6796
#### Attachments Pricing
6897

6998
| Total Attachments Volume | Team/Business Prepaid | Team/Business On-Demand |
@@ -74,75 +103,27 @@ If you'd like to buy either prepaid or on-demand data on top of what's included
74103

75104
<!-- prettier-ignore-end -->
76105

106+
You can buy prepaid volume in increments as shown in the table below:
107+
77108
<!-- prettier-ignore-start -->
78109

79110
<!-- Don't remove spaces from first column header or number ranges in column will break onto two lines making them hard to read -->
80111

81-
#### Consolidated Pricing
82-
83-
| Errors Volume&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Purchase Increment | Transaction Volume | Purchase Increment |
84-
|---|---|---|---|
85-
| >50k-100k | 50k | >100k-250k | 150k |
86-
| >100k-500k | 100k | >250k-500k | 250k |
87-
| >500k-2M | 500k | >500k-10M | 500k |
88-
| >2M-20M | 1M | >10M-100M | 5M |
89-
| >20M-50M | 2M | | |
90-
91-
| Attachments Volume | Purchase Increment | Replay Volume | Purchase Increment |
92-
|---|---|---|---|
93-
| >25 - 100 (GB) | 25 (GB) | >10k - 25k | 15k |
94-
| >100 - 10k (GB) | 100 (GB) | >25k - 100k | 25k |
95-
| | | >100k - 1M | 100k |
112+
| Errors Volume&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Purchase Increment | Transaction Volume | Purchase Increment | Attachments Volume | Purchase Increment |
113+
|---|---|---|---|---|---|
114+
| >50k-100k | 50k | >100k-250k | 150k | >25 - 100 (GB) | 25 (GB) |
115+
| >100k-500k | 100k | >250k-500k | 250k | >100 - 10k (GB) | 100 (GB) |
116+
| >500k-2M | 500k | >500k-10M | 500k | | |
117+
| >2M-20M | 1M | >10M-100M | 5M | | |
118+
| >20M-50M | 2M | | | | |
96119

97120
<!-- prettier-ignore-end -->
98121

99-
If the amount of prepaid data you want to buy falls in-between increments, you may want to consider setting an on-demand budget instead. Because on-demand is set in dollar amounts rather than data volume.
100-
101-
Use the slider on the [pricing](https://sentry.io/pricing/) page to determine the amount of prepaid data you might need based on the volume of event types you send.
102-
103-
![Reserved Volume settings in Subscriptions](reserved-volume.png)
104-
105-
For more information on how to manage your monthly spending, check out our [Quota Management documentation](/product/accounts/quotas/).
106-
107-
## Volume {#capacity}
108-
109-
Your volume is the total number of events and attachments or the total amount of data— sent by your organization. If you'd like to purchase more than what's included in your [plan](https://sentry.io/pricing/), you can do so in two ways: by buying a **prepaid (or reserved) volume** and/or by setting up an **on-demand volume budget**, which will cover potential overages.
110-
111-
### Prepaid (Reserved) Volume {#prepaid-reserved-capacity}
112-
113-
When you buy reserved volume (or quota), you prepay for data at significant discounts. Your prepaid, reserved volume is always applied before on-demand volume kicks in. Unused reserved volume expires at the end of each billing month.
114-
115-
Each Sentry plan includes different amounts of reserved volume. For example, our Team plan includes a minimum of 50k errors, 100k transactions, 500 replays, and 1GB of attachments per month. To see prepaid pricing for each plan, check out our [per-category-pricing](#per-category-pricing).
116-
117-
118-
119-
120-
121-
### On-Demand Volume {#on-demand-capacity}
122-
123-
Buying on-demand volume lets you control the maximum amount you’ll pay for overage each month after your reserved volume runs out. If you go over your on-demand volume, you’ll still have access to previous event data, but any new data you send will be rejected and you won’t be charged for it.
124-
125-
With on-demand volume, you pay for any event or attachment processed, (rounded up to the nearest cent), after your reserved volume has run out. On-demand volume is billed at the end of each billing month. To see on-demand pricing per plan type, check out our [per-category-pricing](#per-category-pricing).
126-
127-
#### Shared and Per-Category On-Demand {#on-demand-cap}
128-
129-
Organizations on all plans have the option to set a shared on-demand strategy. Organizations on plans with [performance monitoring](/product/performance/) features have the ability to choose between a shared or per-category on-demand strategy:
130-
131-
- **Shared:** Your on-demand budget is shared between categories such as errors, transactions, and replays.
132-
133-
- **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.
134-
135-
![On-Demand Budgets settings in Subscriptions](on-demand-budgets.png)
136-
137-
### Changing Plans Mid-cycle
138-
139-
If you decide to increase your on-demand budget mid-month, Sentry will start processing additional data as soon as the increase becomes effective.
140-
141-
If you want to decrease your on-demand budget mid-month, but have already consumed more data than the new desired amount allows, your budget will be lowered to match what you’ve already used and any new data will be rejected. Your on-demand budget will be decreased to the desired amount on your next billing date.
122+
On-demand purchasing isn't restricted by any increments since you set a dollar amount for your budget, rather than a certain amount of data. So if you want to purchase an amount of prepaid volume data that falls between increments, you should set that up as on-demand budget.
142123

143-
If you upgrade from a Team to a Business plan mid-cycle, any existing on-demand budget will be recalculated based on Business tier pricing. This may mean that your on-demand budget will be consumed faster than it was before.
124+
The slider on the [pricing](https://sentry.io/pricing/) page allows you to choose the prepaid volume you'd like for each type of event (errors, transactions) or attachments storage to see what you'd pay.
144125

145-
In most cases, new budgets will take effect within minutes. Otherwise, we guarantee a maximum turnaround time of 24 hours.
126+
If your projects use a high volume of data, you can control how many events or attachments Sentry receives. For more information on how to manage your monthly spending, check out our [Quota Management documentation](/product/accounts/quotas/).
146127

147128
## Billing Periods {#billing-cycles}
148129

0 commit comments

Comments
 (0)