PricingBILLING NOT YET LIVE
Usage-based, unlimited seats, hard cap available.
Billing is not live yet, so this is not a price list — it is the shape we are committing to in public, before there is any commercial pressure to soften it. The numbers will move within these bounds. The shape will not.
Free
$0forever
- Included
- ~50,000 units per month
- Seats
- Unlimited seats
Enough to instrument a real project rather than a toy one, and the tier most people should stay on. It is the whole top of the funnel, not a trial.
Read the quickstartTeam
$29–49per month, usage-based
- Included
- Higher included volume, then metered
- Seats
- Unlimited seats
One usage axis, a hard-cap option so a runaway agent cannot produce a surprise invoice, and no charge for adding a colleague.
Not yet availableEnterprise
Customannual
- Included
- Volume commitments
- Seats
- Unlimited seats
Security review, data-residency requirements, and the compliance paperwork that comes with a procurement process.
Not yet available
A “unit” is one ingested and processed span. One agent action commonly produces dozens of them, which is exactly why we quote units rather than “traces” — a trace-based number would flatter us and mislead you.
What we are committing to4 RULES
Four rules we would have to break loudly
These are on a public page so that changing them costs us something.
- 01
Never per-seat
An observability tool does not become more valuable because a second engineer opens it. Per-seat pricing is the most frequently cited reason teams say they left their previous vendor, and we are not going to reproduce it. Seats are unlimited on every tier, including free.
- 02
One metered axis, not two
Metering both spans and gigabytes means the cheapest way to reduce your bill is to stop logging full prompts and completions — which removes exactly the context you need to debug a failure. Pricing should never push you toward worse observability.
- 03
A hard cap you control
Agents fail in loops, and a loop on a metered product is a financial event. You will be able to set a ceiling that stops ingestion rather than one that sends an invoice.
- 04
Leaving costs a config change
The wire format is OpenTelemetry. If our pricing stops making sense to you, the same instrumentation points somewhere else. We would rather compete on being worth it.
For contextVERIFIED 2026-08-08
What the alternatives charge
Read off each vendor's own public pricing page on 2026-08-08. We re-check these rather than quote our own research, because competitor pricing drifts and a stale number is worse than no number.
| Vendor | Entry paid tier | Seat policy | Overage |
|---|---|---|---|
| LangSmith | $39 per seat/mo · 10k base traces/mo | Per seat | $1.50 per LCU (compute) + $1.00 per LSU (storage) |
| Arize AX | $50/mo · 50k spans/mo · 10 GB/mo · 30-day retention | Unlimited users on all plans | $0.0008 per additional span + $3 per additional GB |
| Langfuse | $29/mo · 100k units/mo · unlimited users | Unlimited users | $8 per 100k units, graduated down to $6 at volume |
| SouthBase | $29–49/mo (intended) | Unlimited seats | One usage axis, hard cap |
Worth saying plainly: Langfuse Core at $29/mo with unlimited users is a genuinely good offer, and our intended shape is similar to theirs rather than cheaper. The axis we are actually beating is LangSmith's per-seat one.
Judge it on arithmetic
Run a cache-heavy Claude workload through it and check the cost against your Anthropic console. If the number is wrong, none of the above matters.