Top-up Credits
Top-up credits are a one-time purchase that covers observability overage β extra RUM and OTLP volume beyond your plan's monthly quota. They let your telemetry keep flowing after an app's monthly quota is exhausted, without forcing a plan upgrade. Credits are bought through Stripe, added to a per-account balance, and drawn down only when a quota is exceeded.
This page covers how to buy credits and how they're consumed. For the related per-app quotas see Observability quotas; for plan-level quotas see Plans & Quotas.
How credits work
- One-time, not recurring β you pay once and the credits sit on your balance.
- Never expire β unused credits roll over indefinitely.
- Drawn down only on overage β while you're within an app's monthly quota, nothing is deducted. Credits are consumed only after the quota is used up.
- Account-wide β the balance belongs to your account and backs all of your observability apps, not a single one.
Balance types
Credits are tracked as separate typed balances. Each type covers one kind of observability volume:
| Balance type | Covers | Unit |
|---|---|---|
| RUM Sessions | Frontend browser sessions | sessions |
| RUM Events | Frontend events (pageloads, vitals, errors, β¦) | events |
| Replay Storage | Session-replay data | GB |
| OTLP Spans | Backend trace spans | spans |
| OTLP Logs Storage | Backend structured logs | GB |
A deduction always comes from the matching type β RUM session overage draws from the RUM Sessions balance, OTLP span overage from the OTLP Spans balance, and so on. Running out of one type does not affect the others.
Top-up packages
Credits are sold as fixed packages. Prices and the volume each package grants are defined on the server (the only source of truth) and applied at checkout:
| Package | Price | Grants |
|---|---|---|
| Starter | $9.99 | 10,000 RUM sessions + 100,000 RUM events |
| Professional | $24.99 | 30,000 RUM sessions + 300,000 RUM events |
| Enterprise | $49.99 | 75,000 RUM sessions + 750,000 RUM events |
Buying a package adds its full grant to your balance. Need a different mix (for example, large OTLP or replay volumes), or custom rates? Contact [email protected].
Buying credits
- Go to Dashboard β Billing β Top-ups (or Dashboard β Top-up Balance β Buy).
- Pick a package.
- You're redirected to Stripe Checkout to pay.
- After a successful payment, Stripe sends a webhook to StatusRadar and the credits are added to your balance.
The success page confirms the payment; the actual crediting is done by the webhook so it happens exactly once even if you refresh or the webhook is retried. If you cancel checkout, no charge is made and no credits are added.
Payment methods
Top-up checkout uses the same Stripe-hosted payment page as subscriptions, so it supports cards and any wallet methods enabled on the account (such as Apple Pay, Google Pay, and Link). Card details never touch StatusRadar.
How credits are consumed
Credits are spent automatically as part of ingestion, in this order:
- Within quota β while the app is under its monthly RUM/OTLP quota, data is accepted against the plan. No credits are touched.
- Quota exceeded β once the monthly quota is used up, StatusRadar checks for a matching top-up balance.
- Balance available β the overage amount is deducted atomically from the balance and the data is accepted. The deduction is recorded so you can see exactly what was used and when.
- No balance β if there are no credits of the needed type, the overage is rejected (the request is refused at the collector) until the next monthly reset or until you buy more credits.
The deduction is a single atomic operation guarded against race conditions: if the balance is insufficient at the moment of deduction, nothing is consumed and the request is rejected rather than driving the balance negative.
This applies to both ingestion surfaces:
- RUM (
rum.statusradar.dev) β session and event overage draws from RUM Sessions / RUM Events; replay overage draws from Replay Storage. - OTLP (
otlp.statusradar.dev) β span overage draws from OTLP Spans; log-storage overage draws from OTLP Logs Storage.
Viewing balance and usage
From Dashboard β Billing β Top-ups (or Dashboard β Top-up Balance) you can see:
- Current balance for each type (only non-zero balances are shown).
- Purchase history β every package you've bought, its price, and status.
- Usage history β each deduction, the app it was charged to, the type, the amount, and the date, plus daily usage charts.
- Total spend and purchase stats.
Use the usage view to spot which apps are consistently exceeding quota β those are candidates for a plan upgrade or for reducing telemetry volume (sampling, filtering noisy spans/logs, lowering replay sample rate).
Refunds
Top-up credits are non-refundable, but they never expire and back your whole account β so unused credits are simply available for future overage.
Next Steps
- Observability quotas β what counts toward RUM/OTLP quotas
- Plans & Quotas β upgrade for more included volume
- Billing Overview β subscriptions vs. top-ups
- Invoices & Portal β receipts and payment history