Langfuse moved off homegrown billing onto Stripe Billing while keeping an in-house ClickHouse meter
Langfuse's Stripe case study discloses that it started with an internal billing system based on a simple per-event flat rate, then migrated to Stripe Billing (usage-based), Stripe Checkout, and Stripe Tax for the rails. It keeps the metering in-house: it posts hourly event counts from its own ClickHouse/OLAP data store to Stripe's metered-usage API, handling up to 200M events/month per account — the operational mirror of its "unit = trace + observation + score" price metric. A "Senior Backend Engineer (IAM and Billing)" req (open in the 2026-04-17 ATS snapshot, since closed) staffed that billing platform; growth analytics run on a bought PostHog/BigQuery/dbt/Metabase stack.