Lago
Depot OSS pick for AI usage metering when you refuse to marry Stripe's meter model. Still collect cash with…
Depot OSS pick for AI usage metering when you refuse to marry Stripe's meter model. Still collect cash with Stripe/Adyen. Strengths: OSS / self-host exit ramp; Purpose-built usage billing primitives; Vendor-neutral vs Stripe-only meters.
Lock-in risk: higher = more lock-in (worse). Overall already inverts this dimension.
Depot OSS pick for AI usage metering when you refuse to marry Stripe's meter model. Still collect cash with Stripe/Adyen.
Strengths
- · OSS / self-host exit ramp
- · Purpose-built usage billing primitives
- · Vendor-neutral vs Stripe-only meters
Weaknesses
- · AGPL compliance diligence required
- · Cloud pricing less transparent than Stripe
- · You own more billing ops than Stripe Billing
Pricing notes
As of 2026-09-14: AGPLv3 OSS metering/billing — self-host free (infra+eng). Lago Cloud remains package/sales-led; docs FAQ does not publish a Cloud seat/event table. Third parties historically cite low-hundreds $/mo starters — unverified. Event-based usage + prepaid credits patterns common for AI APIs.
Sourced pricing
Contract status unavailable · no_sourced_price. Single normalized $/1M: null. Machine list: /api/pricing?provider=lago
No sourced SKU row. Notes above stay prose.
Community signals
Insight claims only — never mutate official scores. Outside reports: 0; seed examples: 0.
No insights yet. Submit a production claim →
All insights for this provider →