Stripe Billing V2 vs Lago vs Orb: Usage-Based Billing in 2026

Two years ago, picking a billing platform for usage-based pricing meant choosing between Stripe and building something yourself. That is no longer the case. The market has split into three distinct camps: Stripe Billing V2 for teams that want everything in one ecosystem, Lago for companies that want open-source control and cost savings at scale, and Orb for engineering teams that need maximum pricing flexibility with a developer-first API.

Each of these platforms has matured significantly through 2025 and into 2026. Stripe shipped its Meters API and real-time usage tracking. Lago reached production stability and crossed 10,000 GitHub stars. Orb expanded its SQL-based pricing engine and landed high-profile AI companies as customers. They are all legitimate options now, but they make very different tradeoffs.

The wrong choice will cost you months of engineering time. We have helped dozens of startups implement usage-based pricing, and the most expensive mistake we see is picking a platform based on a feature checklist instead of understanding how each one actually works under load, with real pricing models, and with a real finance team trying to close the books. This comparison is built from that implementation experience, not from reading marketing pages.

Stripe Billing V2 is not a cosmetic update. The Meters API fundamentally changes how Stripe handles consumption data, and the improvements to webhooks and real-time usage visibility address the two biggest complaints teams had with the original billing system.

The Meters API

You define a meter (for example, "api_calls" or "tokens_processed"), then send usage events with a customer identifier, numeric value, and timestamp. Stripe aggregates these events per billing period and applies your pricing rules at invoice time. Events can be sent individually or in batches of up to 1,000, with deduplication handled through idempotency keys. The pipeline supports tiered, graduated, volume, and package pricing out of the box, and you can combine usage charges with flat subscription fees on a single invoice.

The real-time improvements matter. Previously, usage data in Stripe lagged by 15 to 30 minutes, making it nearly impossible to show customers their current consumption. V2 brings that lag down to single-digit minutes for most use cases. The webhook system is also more reliable, with configurable retry policies and better event ordering guarantees. These are incremental improvements, but they add up to a billing system that finally feels production-ready for metered workloads.

The Ecosystem Advantage

Stripe's real strength is not the metering engine itself. It is everything around it. Payment processing in 135+ currencies, Stripe Tax for automated sales tax and VAT, Revenue Recognition for ASC 606 compliance, Radar for fraud detection, the customer portal, dunning, and financial reporting are all native. No integration layer, no webhook syncing, no reconciliation headaches between two vendors.

Pricing and Limits

Stripe Billing V2 charges 0.5% to 0.8% of billed revenue for metered usage, on top of standard processing fees (2.9% + $0.30 per charge in the US). On a $10,000 monthly usage invoice, expect to pay $50 to $80 for the billing engine plus roughly $290.30 in processing. Total cost: about 3.4% to 3.7%. The limitations are also real. There is no native prepaid credit system. Complex pricing logic that goes beyond the supported models requires custom application code. And the pricing model configuration, while improved, still cannot match the expressiveness of purpose-built billing engines like Orb. If you need per-customer rate cards, SQL-based event transformations, or pricing that varies based on event metadata fields, you will be writing that logic yourself.

Lago is the wildcard in this comparison. It is open-source (MIT license), self-hostable, and built from scratch as an event-driven billing engine. For companies that want full control over their billing infrastructure, or that process enough volume to make vendor fees a significant line item, Lago presents a fundamentally different value proposition than Stripe or Orb.

How Lago Works

Lago's architecture is straightforward: you send usage events to Lago's ingestion API, define billable metrics (count, sum, max, unique count, or custom aggregations), attach those metrics to pricing plans, and Lago generates invoices at the end of each billing period. The system supports per-unit, graduated, package, percentage, and volume-based pricing models. Plans can combine flat fees with multiple usage-based charges, and you can apply coupons, credits, and add-ons at the subscription level.

The event pipeline is built on a message queue architecture (Kafka or Redis Streams, depending on your deployment), which means ingestion throughput scales horizontally. Self-hosted deployments can handle tens of millions of events per day without significant infrastructure costs, because you are running the compute and storage yourself. There are no per-event fees, no percentage-of-revenue fees, and no metering surcharges. Your cost is the infrastructure to run it.

Self-Hosted vs. Cloud

Lago offers two deployment models. The self-hosted version is free and includes the full billing engine, API, and admin UI. You run it on your own infrastructure (Docker Compose for development, Kubernetes for production) and maintain it like any other internal service. The cloud version (Lago Cloud) is a managed deployment with SLA guarantees, starting at roughly $500/month for growth-stage companies and scaling with billing volume.

The self-hosted option is genuinely compelling for companies with strong DevOps capabilities. At $5M+ ARR with usage-based billing, the percentage-of-revenue fees from Stripe or Orb can easily reach $25,000 to $50,000 per year. A self-hosted Lago deployment running on a modest Kubernetes cluster costs a fraction of that. The tradeoff is operational responsibility: you own upgrades, monitoring, database backups, and scaling. If your team already manages production Kubernetes workloads, this is a reasonable ask. If you do not have dedicated infrastructure engineers, the cloud version or a different platform may be the better call.

Where Lago Falls Short

Lago is younger than both Stripe and Orb, and that shows in a few areas. The documentation, while improving, has gaps around advanced use cases. The ecosystem of integrations is smaller. There is no native prepaid credit drawdown system as sophisticated as Orb's. Tax calculation requires integration with a third-party provider like Avalara. And the pricing model flexibility, while solid, does not match Orb's SQL-based engine for truly exotic billing logic. Lago is excellent for standard usage-based models, but if your pricing involves multi-dimensional aggregations or conditional rate selection based on event properties, you may hit the edges of what it can express natively.

Orb occupies a specific niche: companies whose pricing models are too complex for Stripe and who do not want to self-host their billing engine. If you are selling AI inference with per-model pricing tiers, or running a data platform with pricing that varies by compute region, data type, and query complexity, Orb is built for exactly that scenario.

The SQL-Based Pricing Engine

Orb's pricing rules are defined using a SQL-like syntax that can transform, filter, and aggregate event data in ways that template-based systems cannot. You can charge per unique user per day, apply different rates based on an API endpoint field in the event metadata, calculate pricing from the 95th percentile of hourly usage rather than total consumption, or apply multipliers for priority-queue requests. This flexibility is why Perplexity, Vercel, and Replit run their billing through Orb. Their pricing models are genuinely novel, and Orb does not force them into rigid templates.

The ingestion pipeline handles billions of events per month. Events are reflected in customer balances within seconds, not minutes, which matters for products that show real-time usage dashboards or enforce hard spending limits. The API is strongly typed, with excellent TypeScript and Python SDKs that feel like they were designed by engineers who actually build billing integrations.

Prepaid Credits Done Right

Orb has the most mature credit system of the three platforms. Prepaid credits, auto-top-up, configurable expiration policies, credit grants from sales deals, and real-time balance tracking are all native features. Threshold alerts at configurable levels (50% remaining, 25% remaining, depleted), hard limits that block usage at zero balance, and graceful overage handling are built in. This is not a trivial feature. We have seen teams spend 6 to 8 weeks building credit systems from scratch only to discover edge cases around refunds, expirations, and concurrent balance updates that add another month of work. Orb handles all of it.

Pricing and Integration

Orb starts at roughly $500/month for its growth tier, scaling with billing volume. Enterprise contracts involve custom pricing based on event volume and feature requirements. Unlike Lago, Orb is exclusively a managed service. There is no self-hosted option. And like Lago, Orb is a billing engine, not a payment processor. You still need Stripe (or another processor) for actual payment collection, which means managing two vendor relationships, two webhook streams, and potential sync issues between Orb's invoice state and your processor's payment state. Orb provides a native Stripe connector that handles most of this, but it is another layer of integration to maintain.

Feature comparison tables look clean on blog posts, but they hide the details that determine whether a platform works for your specific billing scenario. Here is how Stripe Billing V2, Lago, and Orb compare on the dimensions that matter most in production.

Event Ingestion Throughput

Stripe handles events well for most SaaS workloads but imposes a batch limit of 1,000 events per API call, and latency can spike during peak periods. For companies processing thousands to low millions of events per month, Stripe is adequate. Lago's self-hosted architecture scales horizontally. If you throw more workers and Kafka partitions at it, throughput scales proportionally. Companies running Lago on Kubernetes report handling 50 to 100 million events per day without significant issues. Orb is purpose-built for high-volume ingestion and handles billions of events monthly across its customer base, with sub-second event-to-balance reflection times.

Pricing Model Flexibility

Stripe offers tiered, graduated, volume, and package pricing, covering roughly 80% of use cases. Lago adds percentage-based pricing and more granular aggregation options (unique count, max, weighted sum), covering roughly 90% of standard models. Orb's SQL-based engine covers the remaining 10%, the exotic pricing models that AI and data infrastructure companies increasingly need. If your pricing is straightforward (per-API-call with volume tiers), all three work fine. If your pricing involves conditional logic based on event properties, Orb is the clear winner.

Invoicing and Tax

Stripe has native tax calculation through Stripe Tax, supporting automatic sales tax, VAT, and GST across 50+ jurisdictions. This is a significant advantage. Lago requires integration with an external tax provider. Orb also relies on external tax solutions, though it has partnerships that simplify the integration. For companies selling globally, Stripe's built-in tax handling eliminates an entire category of compliance headaches.

Revenue Recognition

Stripe Revenue Recognition is a mature product that maps directly to ASC 606 requirements. For companies heading toward an audit or IPO, this native integration saves significant accounting effort. Lago provides the raw data needed for revenue recognition but does not include a native rev rec engine. Orb offers revenue recognition features oriented toward usage-based models, with event-level auditability and allocation support.

Multi-Currency Support

Stripe supports 135+ currencies natively, because it is a payment processor at its core. Lago supports multi-currency billing and lets you define plan prices in different currencies, though payment collection still requires a processor integration. Orb supports multi-currency invoicing with conversion handled at the processor level. For companies with a global customer base, Stripe's currency coverage is unmatched.

Billing platform costs look simple on pricing pages but get complicated in production. Here is a realistic cost breakdown at three revenue levels, including the hidden costs that vendor pricing pages do not mention.

At $50K Monthly Billing

Stripe Billing V2 costs roughly $250 to $400/month in billing fees (0.5% to 0.8%), plus $1,480 in payment processing fees (2.9% + $0.30 across estimated transactions). Total: approximately $1,730 to $1,880/month. Lago self-hosted costs $0 in platform fees, plus roughly $200 to $400/month in infrastructure (a small Kubernetes cluster or dedicated VM), plus payment processing through your chosen provider. Total: approximately $1,650 to $1,850/month. Lago Cloud costs roughly $500/month in platform fees plus processing. Total: approximately $1,950/month. Orb costs roughly $500/month minimum plus processing. Total: approximately $1,950/month.

At this level, the cost differences are minor. The decision should be driven by engineering fit and pricing model requirements, not platform costs.

At $500K Monthly Billing

The economics shift. Stripe Billing V2 costs $2,500 to $4,000/month in billing fees alone. Lago self-hosted still costs $0 in platform fees but infrastructure scales to roughly $500 to $800/month. Orb costs scale with revenue, typically landing at $2,000 to $4,000/month. At this volume, self-hosted Lago saves $20,000 to $40,000 per year compared to Stripe or Orb. That is meaningful, but only if your team can absorb the operational overhead.

At $2M Monthly Billing

Stripe billing fees reach $10,000 to $16,000/month. That is $120,000 to $192,000 per year just for the billing layer, on top of payment processing. Lago self-hosted stays at roughly $1,000 to $2,000/month in infrastructure. Orb negotiates enterprise pricing, but expect $5,000 to $10,000/month. At this scale, self-hosted Lago's cost advantage is overwhelming. The $100,000+ annual savings easily funds a dedicated engineer to manage the billing infrastructure. This is why we see companies with strong engineering teams migrate to Lago as they cross $10M ARR: the math becomes impossible to ignore.

The hidden cost in all of these calculations is engineering time. Stripe's ecosystem reduces integration and maintenance work by 40% to 60% compared to Lago or Orb, because you are not managing cross-vendor syncing. If your engineering team is small and stretched thin, that savings in engineering hours may outweigh any platform fee difference.

After building billing integrations across all three platforms, here is our honest recommendation based on company stage, engineering capacity, and pricing complexity.

Choose Stripe Billing V2 When

You are already on Stripe for payments and want the fastest path to usage-based billing. Your pricing model fits standard templates (per-unit, tiered, graduated). Your team is small and you cannot afford to manage multiple billing vendors. You need built-in tax calculation, revenue recognition, and global payment methods without extra integrations. You are pre-revenue through $5M ARR and your pricing model has not yet stabilized. For most early-stage startups, Stripe is the right starting point. The limitations are real, but the speed of integration and operational simplicity outweigh them until your billing needs genuinely outgrow what Stripe can handle.

Choose Lago When

You have strong DevOps and infrastructure capabilities. Cost control matters: you are processing enough volume that percentage-of-revenue fees are a material expense. You want to own your billing data and avoid vendor lock-in. You need a billing engine that runs in your own VPC for compliance or data residency requirements. You are comfortable with open-source software, including occasional rough edges in documentation and smaller community support. Lago is the right choice for engineering-led companies that treat billing as core infrastructure rather than an outsourced service. The self-hosted model gives you control that no managed platform can match, and the cost savings at scale are substantial. If your team already manages Postgres, Redis, and Kubernetes in production, adding Lago to that stack is a natural extension.

Choose Orb When

Your pricing model is genuinely complex: per-model AI inference pricing, multi-dimensional event aggregations, conditional rate selection, or pricing logic that requires SQL-level expressiveness. You need first-class prepaid credit support with real-time balance tracking and threshold alerts. You want the best developer experience in the billing space, with strongly typed SDKs and an API designed for the consumption billing domain. You are building a developer-facing or AI product where pricing innovation is a competitive advantage, not just a back-office concern. Orb is the right choice when your pricing model is too complex for Stripe and you do not want the operational burden of self-hosting Lago. The $500/month starting price is reasonable for the engineering time it saves on exotic billing logic.

The Migration Question

Most companies will not stay on their first billing platform forever. The healthy pattern we see is: start with Stripe for speed, evaluate Lago or Orb when billing maintenance starts consuming serious engineering hours, and migrate when the cost (in platform fees or engineering time) justifies the transition. Migrating billing systems is painful but survivable if you plan for it. The worst outcome is fighting the wrong platform for 18 months because you optimized for where you wanted to be instead of where you are today.

If you are building a product with usage-based pricing and need help choosing the right billing architecture, or if you are ready to implement subscription billing and want to avoid the expensive mistakes we have seen other teams make, book a free strategy call with our engineering team. We have built billing integrations across Stripe, Lago, and Orb, and we can help you pick the right platform for your specific situation.