Billing

Prices and what each plan includes are on the pricing page, rendered from the same table billing charges by. This page is how billing behaves.

What is metered

Spans admitted by the engine, summed across all of an organization’s projects. Every minute, Traza Cloud reads each cell’s per-tenant counters and adds what changed. A batch refused at the cap is not counted. Members, projects, reads, exports, replays and MCP calls are never metered.

The period is your subscription period on a paid plan, and the calendar month in UTC on Free. Spans metered between the end of a paid period and Stripe confirming its renewal count in the new period. If the engine restarts and loses a few seconds of counts, nothing is counted twice.

At the cap

With overage off, the default, the included spans are a hard cap. When the organization reaches it:

• ingest pauses: the engine answers new batches with 429 and Retry-After, and OTLP exporters back off and retry;
• reads, exports, replays, evidence packs and erasure keep working;
• nothing is deleted early.

At 80% of the cap a quota.warning alert fires, and at the cap quota.capped, to any destination with a rule for them. Because metering runs every minute, ingest can pass the cap by up to a minute of traffic before the pause takes effect. Ingest resumes when the period resets, when you upgrade, or when you turn overage on.

Overage and the spend cap

On Pro and Team, an owner can turn on overage from the console’s Billing page. Spans past the included amount are then billed per span at the plan’s overage rate, reported to Stripe hourly; each hour’s report carries a unique identifier, so a retry never bills twice.

Set a spend cap to bound it: the most you will pay for overage in a period. Ingest pauses when the cap’s worth of overage spans is used. Without a spend cap, the allowance is ten times the plan’s included spans on top of them.

Changes to overage and the spend cap apply from the moment you make them: spans already ingested are billed under the settings they were ingested with.

Changing plans

Upgrades go through Stripe Checkout and take effect when Stripe confirms the subscription. An organization has one checkout open at a time, so it can never end up paying for two subscriptions. Switching between Pro and Team is prorated; a downgrade from Team to Pro takes effect at the end of the period. Payment methods, invoices and cancellation are in the Stripe billing portal, linked from the Billing page.

Retention follows the plan you are on. After a downgrade to a plan with shorter retention, spans older than the new window expire, so export first if you need them.

Failed payments

When a payment fails, the organization is marked past due and billing.payment_failed alerts fire. After a seven-day grace period, ingest is paused until the invoice is paid. Reads and exports keep working throughout.

Never

No per-seat pricing. No export or egress fees. No deletion at the cap.