diff --git a/src/docs/product/accounts/pricing.mdx b/src/docs/product/accounts/pricing.mdx index c59ebe884dfdd..dff06eb1ad6bc 100644 --- a/src/docs/product/accounts/pricing.mdx +++ b/src/docs/product/accounts/pricing.mdx @@ -26,17 +26,6 @@ On top of that, you can choose to pay for a set, prepaid volume of additional da 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. - - -Sentry has moved to unit-based Performance pricing. This means customers will be charged based on a volume of total units for two different Performance event types: - -- **Transactions** - Consumes 1 Performance Unit and is sent by projects with [Tracing](/product/sentry-basics/tracing/) enabled. -- **Transactions with Profiling** - Consumes 1.3 Performance Units and is sent by projects that have both [Profiling](/product/profiling/) and [Tracing](/product/sentry-basics/tracing/) enabled. - -_For example, if you send 1M Transactions and 1M Transactions with Profiling, you'll be consuming 2.3M units of your total quota [(1M at 1 unit) + (1M at 1.3 units)]._ - - - ### Per-Category Pricing 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), [Performance](#performance-pricing), [Replays](#replays-pricing), and [Attachments](#attachments-pricing), each have their own unique pricing structures, as listed in the tables below: