Pick the volume you send each month.

By default usage stops there and nothing is billed. Ingestion answers 429 with a Retry-After header: at the start of the next monthly window when the month's allowance is used up, or at the next UTC midnight when a runaway spike reaches the daily safety ceiling. The official SDKs handle it gracefully; your application never blocks or crashes because of a quota. Everything already ingested stays searchable.

Overage is off unless you turn it on. A workspace admin can opt in under Billing with one switch that covers every resource the plan sells, and one monthly spend cap shared by all of them; once the cap is reached, usage stops at the allowance again, and a cap of $0 keeps paid overage off entirely. Opting in applies from that moment on, never to usage that already happened. Each resource is billed at the rate in the comparison table, only on exactly measured quantities, and overage below $1 is carried to your next invoice rather than charged on its own. On the Free plan nothing is ever billed; every allowance is a hard stop.

Every paid plan includes a 14-day free trial: one trial per account, and you're never charged during it, overage included. Signup itself needs no card. You start the trial under Billing, and that is when we ask for a payment method: it is stored, not charged, and the page tells you the exact date billing starts, the amount and the billing cycle. You're billed only when the trial ends and converts to a paid subscription. Cancel before then on the same page and you drop back to Free with your data intact (within Free limits).

Yes. Upgrades apply immediately (billed for the new period on the spot); downgrades and cancellations take effect at the end of the period you've already paid for. You can also pause a subscription and resume later. No lock-in, no cancellation calls.

Yearly billing is ten months' price for twelve months of service: two months free. Allowances still reset every month on annual billing: one base charge a year, twelve monthly usage windows. You can switch cycles when changing plans; the new cycle starts with the new period.

Log and trace ingest is measured on the uncompressed size of what your SDKs and OpenTelemetry exporters send, before we index it, pooled across the month. Product-analytics events are counted separately, by the size of each event's JSON payload. Queries, dashboards and alerts are not counted. The daily ceiling exists only to stop a runaway spike from using the whole month in an afternoon; it is never charged. Your usage page shows every resource, what is left, and where the month is heading.

Paid plans include a monthly allowance of alert emails, SMS and voice calls (Free includes emails), shown in the table, with no setup: alerts just work. Past the allowance a send is billed at the per-message rate in the table if you opted into overage, or drawn from prepaid credits at the same rate, topped up in $5, $10, or $25 packs. Connect your own Twilio account instead and SMS and calls are billed by Twilio at your rates, with nothing added by us. Webhook and custom-script notifications are not metered.

Traces that contain an error are kept for your plan's full retention, exactly like logs. Error-free traces are kept for up to 30 days, and never longer than your plan's retention, since healthy request waterfalls lose their value sooner than failures do. You can shorten that per workspace. Daily latency and throughput summaries are kept much longer, so day-over-day comparisons keep working after the raw traces are gone.

No. A resource is only sold once it can be measured exactly for your workspace. Anything we cannot yet measure per request, such as the extra compute of a heavy query, is shown on your usage page for information and is not charged. New resources start in a measure-only stage, then show an estimate, and only then bill, each announced ahead of time.

Yes: open-source maintainers, students, and educators can get Team features free or heavily discounted. Contact us with a link to your project or institution.

Enterprise SSO is available on Enterprise plans; contact us and we will enable it for your workspace. A workspace connects its own OpenID Connect identity provider, Microsoft Entra ID is supported, and the workspace can then require it, after which password sign-in is refused. Google Workspace and other OpenID Connect providers are available on request. SSO is not part of the Free, Pro, Team or Business plans. SAML and SCIM provisioning are not available yet. How Enterprise SSO works.