Application Performance Monitoring
Fast & Cost-Effective APM with AI-based sampling. Runs On-Prem with no traces data sent out of your cloud.
Easy log management with fast search & data privacy at the core. No log data leaves your cloud. Ever.
Track hosts, databases, containers, and cloud services in real time — with unlimited retention and full data control.
Track every user journey in real time. Get instant visibility into performance bottlenecks with 4X faster, on-prem RUM.
Prevent downtime before it happens with proactive, scripted tests. Simulate user journeys and detect issues before customers are impacted.
Catch every error in real time. Aggregate, analyze, and resolve issues 4× faster with CubeAPM.
Track Kubernetes clusters, nodes, and pods with real-time performance insights
Application Performance Monitoring
Fast & Cost-Effective APM with AI-based sampling. Runs On-Prem with no traces data sent out of your cloud.
Easy log management with fast search & data privacy at the core. No log data leaves your cloud. Ever.
Track hosts, databases, containers, and cloud services in real time — with unlimited retention and full data control.
Track every user journey in real time. Get instant visibility into performance bottlenecks with 4X faster, on-prem RUM.
Prevent downtime before it happens with proactive, scripted tests. Simulate user journeys and detect issues before customers are impacted.
Catch every error in real time. Aggregate, analyze, and resolve issues 4× faster with CubeAPM.
Track Kubernetes clusters, nodes, and pods with real-time performance insights
Sentry Pricing Calculator
Sentry Pricing Calculator
Enter your error volume, tracing spans, and feature usage to get an instant monthly Sentry cost estimate - and see how CubeAPM compares.
▶ Pay-as-you-go rates
| Volume / month | Team plan | Business plan |
|---|---|---|
| 50K – 100K | $0.0003625/error | $0.0011125/error |
| 100K – 500K | $0.0002188/error | $0.0006250/error |
| 500K – 10M | $0.0001875/error | $0.0003750/error |
| 10M – 20M | $0.0001625/error | $0.0003250/error |
| 20M+ | $0.0001500/error | $0.0003000/error |
▶ Pay-as-you-go rates
| Volume / month | Team plan | Business plan |
|---|---|---|
| 5M – 100M | $0.0000020/span | $0.0000040/span |
| 100M+ | $0.0000018/span | $0.0000036/span |
▶ Pay-as-you-go rates
| Volume / month | Rate (both plans) |
|---|---|
| 0 – 5 GB | Free (included) |
| 5 GB+ | $0.50/GB |
▶ Pay-as-you-go rates
| Volume / month | Rate (both plans) |
|---|---|
| 0 – 5 GB | Free (included) |
| 5 GB+ | $0.50/GB |
▶ Pay-as-you-go rates
| Volume / month | Rate (both plans) |
|---|---|
| 0 – 1 GB | Free (included) |
| 1 GB+ | $0.3125/GB |
▶ Pay-as-you-go rates
| Volume / month | Rate (both plans) |
|---|---|
| 50 – 5K | $0.003750/replay |
| 5K – 100K | $0.003563/replay |
| 100K – 900K | $0.003206/replay |
| 900K – 4.5M | $0.002886/replay |
| 4.5M+ | $0.002453/replay |
▶ Pay-as-you-go rates
| Monitors | Rate (both plans) |
|---|---|
| 1 (first) | Free (included) |
| 2+ | $0.78/monitor/mo |
▶ Pay-as-you-go rates
| Monitors | Rate (both plans) |
|---|---|
| 1 (first) | Free (included) |
| 2+ | $1.00/monitor/mo |
▶ Pay-as-you-go rates
| Usage | Rate (both plans) |
|---|---|
| No free tier | - |
| All hours | $0.0315/profile-hour |
▶ Pay-as-you-go rates
| Usage | Rate (both plans) |
|---|---|
| No free tier | - |
| All hours | $0.25/profile-hour |
▶ Pay-as-you-go rates
| Usage | Rate (both plans) |
|---|---|
| No free tier | - |
| Per active contributor | $40.00/contributor/mo |
This estimate uses the exact formulas from sentry.io/pricing.
Where your Sentry costs come from
Unlimited users · Unlimited retention · No per-event fees
| Component | Sentry | CubeAPM |
|---|
What's included with CubeAPM
| Feature | Sentry | CubeAPM |
|---|---|---|
| Billing dimensions | 11 independent meters | 1 flat rate ($0.15/GB) |
| Error monitoring | Per-error tiered pricing (2 plan tiers) | Included in $0.15/GB |
| Tracing / spans | Per-span (2× higher on Business) | Included in $0.15/GB |
| Log ingestion | $0.50/GB above 5 GB free | Included in $0.15/GB |
| Users | Unlimited | Unlimited |
| Profiling | $0.03–$0.25/hr, no free tier | Included in $0.15/GB |
| Data sovereignty | Data leaves your infrastructure | Stays in your VPC |
| Deployment | SaaS (Sentry-hosted) | Your own cloud account |
Plan base fee: Team Annual $26/mo · Team Monthly $29/mo · Business Annual $80/mo · Business Monthly $89/mo
Errors: Free tier 50K/month. Team: $0.0003625/error (50K–100K), $0.0002188 (100K–500K), $0.0001875 (500K–10M), $0.0001625 (10M–20M), $0.0001500 (20M+). Business: 3× higher rates at each tier.
Spans: Free tier 5M/month. Team: $0.000002/span (5M–100M), $0.0000018 (100M+). Business: 2× higher rates.
Logs: $0.50/GB above 5 GB free. Same rate on both plans.
Application Metrics: $0.50/GB above 5 GB free. Same rate on both plans.
Attachments: $0.3125/GB above 1 GB free.
Session Replays: Free tier 50/month. Tiered: $0.003750 (50–5K), $0.003563 (5K–100K), $0.003206 (100K–900K), $0.002886 (900K–4.5M), $0.002453 (4.5M+).
Cron Monitors: $0.78/monitor above 1 included.
Uptime Monitors: $1.00/monitor above 1 included.
Continuous Profiling: $0.0315/hour. No free tier.
UI Profiling: $0.25/hour. No free tier.
Seer AI: $40.00/active contributor/month. No free tier.
CubeAPM: $0.15/GB platform fee. ~$0.02/GB estimated cloud infra overhead. $1,000/month minimum. GB equivalents: 1M errors = 1 GB · 1B spans = 5 GB · 1M replays = 50 GB · 100 cont. profile hrs = 1 GB · 100 UI profile hrs = 0.5 GB.
Not affiliated with or endorsed by Functional Software, Inc. (Sentry).
Why use this Sentry pricing calculator?
Sentry’s pricing is event-based, meaning costs accumulate across multiple data categories simultaneously. Small changes to instrumentation, sampling configuration, log volume, or the number of monitored jobs can shift your monthly bill in ways that are not obvious until the invoice arrives.
This calculator helps you:
- Estimate Sentry costs before committing to a plan or scaling workloads
- Identify which categories drive the most spend: errors, spans, replays, logs, profiling, or Seer
- Model cost scenarios across Team and Business tiers
- Compare Sentry's per-event pricing with a flat ingestion-based alternative using the same assumptions
How Sentry pricing works
Plans at a glance
- Developer: Free, one user, limited quotas, no third-party integrations
- Team: $26/month, unlimited users, third-party integrations, 90-day retention
- Business: $80/month, unlimited custom dashboards, advanced quota management, SAML/SCIM
- Enterprise: Custom pricing, dedicated support, SLA
How billing works
Each paid plan includes a base monthly quota per data category. Usage above that quota is billed through one of two mechanisms:
- Reserved volume: prepurchased at a discounted rate, expires at month end if unused
- Pay-as-you-go (PAYG) budget: shared across all categories, billed at a ~25% premium over reserved rates
Billing units by category
- Errors: per event
- Spans (Tracing): per individual span
- Logs and Application Metrics: per GB ingested
- Session Replays: per session
- Uptime and Cron Monitors: per active monitor per month
- Profiling: per profile hour
- Seer: per active contributor per month
Why Sentry's pricing becomes complex at scale
Sentry’s pricing is not based on a single consumption unit. Every product category has its own included quota, overage rate, and reserved vs. PAYG structure. As teams enable more features, costs compound across independent dimensions rather than scaling predictably with application growth.
Multiple billing units across products
Sentry charges separately for each of these categories:
- Errors
- Spans (distributed tracing)
- Logs
- Application metrics
- Session replays
- Uptime monitors
- Cron monitors
- Continuous profiling
- UI profiling
- Seer AI debugging (separate subscription)
Enabling additional products over time compounds costs across dimensions that were not part of the original budget.
Tiered overage rates for errors
Error overage rates are not flat; they decline in steps based on total volume:
- Cost estimates based on average rates will understate actual spend at lower volumes
- Accurate forecasting requires modeling the specific volume tier your usage falls into
- Business plan error rates are up to 3x higher than Team in the 50K–100K tier
PAYG rates carry a ~25% premium over reserved rates
For every category, pay-as-you-go rates are higher than prepaid reserved rates:
- Teams consistently exceeding reserved quotas pay a premium avoidable with upfront commitment
- The premium is approximately 25% across most categories
- Profiling and logs have no reserved option at all; they are always billed at PAYG rates
Monitors are billed per unit, independent of data volume
Each active monitor is a separate line item:
- Cron monitors: $0.78/monitor/month
- Uptime monitors: $1.00/monitor/month
- Teams monitoring many jobs or endpoints will see per-unit costs stack up regardless of check frequency or data volume
- 1 of each is included on paid plans; everything beyond that draws from the PAYG budget
Logs and application metrics cannot be prepaid as reserved volume
A commonly overlooked constraint:
- Both categories include 5 GB on paid plans
- Any usage beyond 5 GB is PAYG only at $0.50/GB, no reserved option exists
- Unlike errors and spans, there is no way to lock in a lower rate through upfront commitment
- This makes log cost forecasting harder for high-volume applications
Retention differences across plans
Data lookback periods vary by plan:
- Developer (free): 30-day lookback
- Team: Up to 90-day lookback
- Business: Up to 90-day lookback plus additional sampled retention
Teams upgrading to Business solely for longer retention should factor the full plan cost ($80/month) against the compliance or operational requirement driving that need.
Why this matters for cost estimation
Because each pricing unit applies independently, Sentry costs can increase from multiple directions simultaneously:
- More deployments increase error volume
- More service calls increase span volume
- More user sessions increase replay counts
- More active engineers increase Seer costs
- More jobs and endpoints increase monitor unit counts
- Longer retention requirements force plan upgrades
This is why Sentry feels straightforward at small scale but increasingly difficult to forecast as application complexity grows. The calculator is designed to surface these cost drivers before they become difficult to control.
What typically causes Sentry bills to spike
Error volume
- Unsampled validation errors or expected exceptions not filtered at SDK level
- Bot traffic or health check noise reaching Sentry without inbound filtering
- A noisy third-party integration sending high-frequency low-signal errors
Span volume
- Newly instrumented microservices sending 100% of traces without a sample rate
- High-frequency background jobs or polling operations fully instrumented
- Database query spans enabled on high-throughput services
Replay and profiling
- Session replay enabled globally across all pages at 100% sample rate
- Profiling activated on production services without estimating hourly volume against the PAYG budget
Budget and quota configuration
- PAYG budget set too low, causing data to drop silently mid-month
- No spend notifications configured to alert before budget exhaustion
How to manage Sentry costs
Engineering and FinOps teams manage Sentry spend by controlling how events are generated, sampled, and retained before reaching Sentry’s ingestion pipeline.
Filter and deduplicate errors
Not every exception is worth capturing. Common approaches:
- Configure inbound filters to block known bot traffic and health check endpoints
- Suppress validation errors and expected exceptions at the SDK level before they are sent
- Group duplicate errors aggressively to reduce raw event count against quota
- Use Sentry’s before-send SDK hook to drop low-signal error classes entirely
Try in the calculator: reduce your estimated monthly error count by 20 to 30% and observe how quickly overage charges drop.
Sample traces to control span volume
Span volume can grow quickly in microservices architectures:
- Set a meaningful sample rate (10 to 20% is common in production) rather than sending 100% of traces
- Use tail-based sampling to retain traces for slow requests and errors, and drop the rest
- Avoid instrumenting high-frequency background tasks unless they are business-critical
- Limit database span capture on high-throughput query paths
Try in the calculator: lower your span volume input and observe APM overage costs decline.
Use session replays selectively
Replays are one of the faster-scaling cost categories at higher traffic:
- Enable replays only on pages or flows where error context is most valuable
- Set a replay sample rate below 100%; error-triggered replays are higher value than ambient recording
- Review replay quota consumption in the dashboard before expanding to new surfaces
Right-size reserved volume each billing period
Since unused reserved volume expires at month end:
- Review the previous month’s actual consumption in the quota dashboard before purchasing additional reserved volume
- Set a PAYG budget that covers typical overages without over-allocating for capacity that will go unused
- Configure spend notification thresholds to alert before the PAYG budget is exhausted
- For variable workloads, it is often safer to rely on a generous PAYG budget than to over-purchase reserved volume
Audit Seer contributor counts monthly
Seer costs can be controlled directly:
- Review which repositories are Seer-enabled; disable it on low-priority or archived repos
- Monitor PR activity on connected repositories to anticipate contributor counts before the monthly reset
- Evaluate whether all Seer-enabled repositories require AI debugging or whether a subset covers most of the value
When cost optimization becomes ongoing work
While these steps reduce Sentry bills, they require continuous tuning as applications evolve and teams grow. At larger scale, managing the following becomes a recurring operational task:
- Sampling rate configuration across services
- Quota and PAYG budget reviews each billing cycle
- Monitor count audits as new jobs and endpoints are added
- Seer contributor tracking across repositories
This is often when teams evaluate alternative platforms where cost boundaries are enforced structurally rather than managed through continuous configuration.
What about self-hosted Sentry?
Sentry provides an open-source, self-hosted version available on GitHub at no licensing cost. It can be deployed on your own infrastructure, but comes with significant operational requirements.
What self-hosted Sentry requires
The self-hosted stack depends on multiple services that you are responsible for running and maintaining:
- PostgreSQL (primary database)
- ClickHouse (event storage and analytics)
- Apache Kafka (event ingestion pipeline)
- Redis (caching and queues)
- Zookeeper (Kafka coordination)
- Nginx and multiple Sentry worker processes
Trade-offs to consider
- No SLA, no vendor support, and no managed upgrades
- Operational complexity scales with data volume
- The self-hosted release may lag behind the cloud version on new features
- Your engineering team absorbs the maintenance burden
Sentry Pricing vs CubeAPM: A Structural Difference
The key difference between Sentry and CubeAPM is not features; it is the pricing model and where the platform runs.
- Sentry operates as a fully managed SaaS platform where pricing scales across multiple event categories independently
- CubeAPM runs inside customer-controlled infrastructure and bills on per-GB ingestion rate
- CubeAPM has no per-event fees, no per-host fees, no per-user charges, and no per-monitor unit costs
| Area | Sentry | CubeAPM |
|---|---|---|
| Pricing model | Per-event, per-category across errors, spans, replays, monitors, profiling, and Seer | Ingestion-based only (no host, user, or series fees) |
| Cost predictability | Varies with event volume, contributor count, and monitor count | Stable with data volume |
| Error monitoring | Billed per error, tiered by volume | Included in the rate ($0.15/GB) |
| Distributed tracing | Billed per span, tiered by volume | Included in the rate ($0.15/GB) |
| Log management | $0.50/GB over 5 GB included, PAYG only | Included in the rate ($0.15/GB) |
| Uptime and cron monitors | $1.00 and $0.78 per monitor/month | Included in the single ingestion-pricing of $0.15/GB |
| Retention | Up to 90 days on paid plans | Unlimited |
| Data residency | SaaS & Self-hosted | On-prem or customer-controlled cloud |