One bill. No asterisks.

Every byte of telemetry your organisation sends us, measured uncompressed after decompression at the ingest endpoint: logs, traces and spans, metrics, exceptions, session replay segments and profiles. It is a single meter across all of your projects, so you never have to guess which product line a payload will be billed under. Dashboard queries, alert evaluations and synthetic monitor runs are not metered.

Nothing you have to pay for. At 80% of your monthly ingest allowance we email the organisation owner. At 100% ingest is paused: the endpoint answers HTTP 503 with a Retry-After header, which OTLP exporters and the TracePath SDKs treat as a retry, and the rest of the product keeps working on the data already stored. Ingest resumes at the start of the next calendar month, or the moment you upgrade. Project, seat and monitor limits behave the same way: the action that would cross the limit is refused with a message naming the limit, rather than silently costing you money.

Yes. Upgrades take effect immediately and the new limits apply on the next request. Downgrades and cancellations take effect at the end of the period you have already paid for, so you keep the plan you bought until it runs out. Everything is self-serve from the billing settings in the app, through the Stripe customer portal.

Subscriptions are billed in advance and you can cancel at any time, which stops the next renewal and leaves your current period running to its end. If something went wrong on our side, or you were charged by mistake, email [email protected] and we will sort it out. The full terms are on the Terms of Use page.

Yes, and nothing about the instrumentation ties you to us. You send data over plain OTLP, which is the same protocol every other OpenTelemetry-compatible backend speaks, so switching is a change of endpoint rather than a rewrite — and you can fan the same data out to a second backend at any time. Dashboards export as JSON, and your stored telemetry is readable through the documented query API with a personal access token. There is no one-click bulk export yet: email [email protected] while your account is active and we will produce an export within 30 days, at no charge.

TracePath Cloud runs on infrastructure hosted in the European Union, currently at Hetzner in Helsinki, Finland. The complete, current list of the providers we rely on is published on the subprocessors page, and we update it before we add one. Data residency outside the EU, or a dedicated deployment in a region of your choosing, is available on Enterprise.

Payments are handled by Stripe, so your card details never touch our servers. Cards are accepted everywhere; Stripe also offers additional local payment methods at checkout in the countries where it supports them. Invoices and receipts are available from the Stripe customer portal, linked from your billing settings. Enterprise customers can be invoiced on payment terms instead.

There is something better: a Free plan that does not expire and does not ask for a card. It carries the entire product, just at a smaller volume and a shorter retention window. Start there, point a real service at it, and upgrade when the 5 GB or the 7-day window stops being enough.

No. Every price on this page is net of tax. Customers in Poland are charged 23% Polish VAT. Business customers elsewhere in the EU who supply a valid EU VAT ID are invoiced under the reverse charge mechanism, with no VAT added. Customers outside the EU are invoiced without EU VAT.

A seat is a person with a login in your organisation, whatever their role, including read-only members. A project is one instrumented application or service with its own ingest token, its own dashboards and its own issue feed. Most teams use one project per deployable service, plus one per environment where the environments need to stay apart.