You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/docs/product/accounts/pricing.mdx
+59-78Lines changed: 59 additions & 78 deletions
Original file line number
Diff line number
Diff line change
@@ -8,28 +8,65 @@ redirect_from:
8
8
description: "Learn about pricing variables, managing volume, and different Sentry plans."
9
9
---
10
10
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:
12
12
13
-
-[How our pricing works](#pricing-how-it-works) and [per-category-pricing](#per-category-pricing)
14
13
-[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)
15
15
-[Billing periods](#billing-cycles)
16
16
-[Taxes](#taxes) and [exemptions](#tax-exemptions)
17
17
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).
_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.
20
25
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:
22
27
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
+

29
+
30
+
To see prepaid pricing per volume tier, check out our [pricing tables](#pricing-tables).
31
+
32
+
### On-Demand Volume {#on-demand-capacity}
24
33
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.
27
35
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
+

29
47
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.
31
49
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:
33
70
34
71
<!--prettier-ignore-start-->
35
72
@@ -56,14 +93,6 @@ If you'd like to buy either prepaid or on-demand data on top of what's included
0 commit comments