Lago reviews 2026

The usage-based billing landscape has shifted materially in 2026, with major acquisitions changing how SaaS, AI, and infrastructure companies evaluate billing vendors. Lago is an open-source billing platform that has raised $22 million in funding, including backing from FirstMark and Y Combinator. It offers self-hosted and managed deployment options for teams that value code transparency and infrastructure control. For companies evaluating billing infrastructure, understanding how Lago compares with Orb's usage-based billing engine can clarify differences in pricing flexibility, operational ownership, finance workflows, and long-term scalability.

Key takeaways

• Lago's open-source core is distributed under AGPLv3 and supports self-hosted deployment, giving teams direct control over where the billing system runs and how the code is operated.
• Lago has traction with AI and infrastructure companies, including Mistral.ai, Together.ai, and Groq.
• Lago's product portfolio includes wallets, subscriptions, multidimensional pricing, multiple payment providers, usage projections, and event fee estimation for applicable pay-in-advance charges.
• Lago provides projected usage and billing estimates plus event fee estimates for applicable pay-in-advance charges. Orb's Simulations add a dedicated workflow to test pricing changes against historical usage before deployment and compare pricing scenarios side by side.
• Lago supports combined-dimension pricing through billable metric filters and pricing group keys. Orb's dimensional pricing supports pricing across multiple usage dimensions within a single pricing configuration.
• Lago supports Stripe, Adyen, GoCardless, community integrations, and custom payment provider integrations. Orb, now part of Adyen, states that customers can continue using their preferred payment-processing partner.
• On its standard ingestion path, Orb combines usage metering, pricing, subscriptions, invoicing, accounts receivable workflows, reporting, and finance integrations in a managed platform built around stored raw usage events.

Understanding modern billing needs: beyond traditional invoicing software

Why basic invoicing falls short for usage-based models

Traditional invoicing software handles straightforward scenarios well: fixed subscription amounts, predictable billing cycles, and simple line items. Modern software companies face a different reality. AI platforms bill for tokens, API calls, and compute time. Infrastructure providers charge across dimensions such as region, instance type, and environment. Developer tools combine seat-based pricing with consumption metrics.

This complexity introduces requirements that basic invoicing systems may not be designed to handle on their own:

• Usage metering across high-volume product activity
• Hybrid pricing models combining subscriptions with usage components
• Mid-cycle adjustments for plan changes, upgrades, and credits
• Revenue recognition workflows designed to support ASC 606 accounting and reconciliation requirements
• Auditability that connects usage, pricing logic, invoices, and downstream finance records

The billing platform a company chooses can materially affect how much engineering work is required to change pricing and how much reconciliation finance teams perform each close.

The shift toward revenue design

Modern software companies increasingly treat pricing as a cross-functional operating system rather than a static number on a pricing page. Product teams choose value metrics, Sales introduces negotiated terms, Finance needs accurate and explainable revenue, and Engineering has to connect product activity to billing execution.

Orb describes this operating model as revenue design: coordinating pricing, billing, and revenue workflows so teams can evolve monetization without creating disconnected logic across product code, spreadsheets, and finance systems.

Decoding subscription billing: what to look for in subscription management software

Core capabilities for recurring revenue

Effective subscription management requires more than automated invoice generation. Common capabilities include:

• Prepaid credits and wallets with expiration handling and drawdown tracking
• Mid-cycle plan changes with configurable proration and invoice treatment
• Dunning management for failed payment recovery
• Customer lifecycle automation from trial conversion to renewal
• Entitlements and plan controls that connect commercial terms to product access

Lago supports wallet-based credits and subscription management, with additional billing and finance capabilities available through its broader product packaging. Its open-source model can be appealing to teams that want direct code access and deployment control.

Managing subscription complexity at scale

As customer counts and contract variations grow, subscription complexity compounds. Capabilities that become increasingly relevant include:

• Customer hierarchies for multi-organization accounts
• Bulk operations for changes across customer cohorts
• Audit trails for compliance and operational review
• Versioned pricing for grandfathered and newly launched commercial terms
• Commitments and credits that reflect enterprise contracts

Orb's finance workflows add accounts receivable automation and accounting period controls, while its NetSuite integration connects billing records to ERP workflows.

Lago vs. Orb: advanced usage-based billing for B2B SaaS

Architectural differences that matter

Lago uses event-based metering, API and JSON configuration, and SQL custom expressions for billable metric calculations. Orb's standard ingestion path uses a query-based architecture that stores raw usage events immutably and computes invoices as deterministic query outputs.

That difference affects how each platform approaches pricing evolution and billing analysis:

• Pricing evaluation: Orb can apply pricing changes against historical raw usage events. Lago supports pricing and dimensional changes for open, pre-invoice usage and provides correction workflows for finalized billing records.
• Metric flexibility: Orb supports full SQL for defining billable metrics, including CASE statements, subqueries, and aggregations. Lago supports SQL custom expressions alongside JSON, API, filters, and pricing group configuration.
• Usage visibility: Lago provides event monitoring and current, projected, and past usage views. Orb enables tracing invoice charges back to underlying usage data for audit lineage.
• Pricing iteration: Lago provides projections, fee estimates for applicable pay-in-advance charges, invoice previews, and analytics. Orb adds a dedicated simulation workflow over historical usage data.

Deployment model considerations

Lago offers self-hosted open-source and Premium deployments, Lago Cloud, and enterprise hybrid hosting options such as cloud-prem or VPC. Orb is a managed billing platform.

Lago self-hosted:

• AGPLv3 open-source core
• Direct control over hosting environment and deployment topology
• Infrastructure and application operations owned by the deploying team
• Ability to inspect and extend the codebase

Orb managed:

• Custom pricing based primarily on billings and event volume, with a platform fee on Advanced and Enterprise
• Managed infrastructure for the billing platform
• 99.99% SLAs available for enterprise use
• Managed scaling, reliability, and platform operations

The deployment choice often comes down to operating model. Lago gives teams the option to own the infrastructure and code path directly. Orb centralizes that responsibility in a managed service while providing an end-to-end revenue workflow.

Feature comparison on pricing sophistication

Capability

Lago

Orb

SQL-based metrics

SQL custom expressions plus JSON, API, filters, and pricing group configuration

Full SQL flexibility

Pricing simulation

Projected usage and fee estimates for applicable pay-in-advance charges, with invoice previews in premium

Historical pricing simulations with side-by-side scenario modeling

Multidimensional pricing

Combined-dimension filters and multiple pricing group keys

Native multidimensional pricing

Event ingestion

Supports API, batch, and streaming ingestion options

250,000+ events per second stress-tested, with Hosted Rollups used by Orb's largest customers to sustain several million events per second in production

Revenue recognition

Native Revenue Recognition Alpha, premium add-on

ASC 606-aligned reporting

Optimizing revenue: how to choose billing software

Evaluation criteria for modern billing platforms

Selecting billing infrastructure requires assessing several dimensions at the same time.

Technical requirements:

• Event ingestion volume and latency requirements
• Metric complexity, from simple counts to advanced aggregations
• Integration requirements across ERP, CRM, tax, data, and payment systems

Operational requirements:

• Deployment model, including managed and self-hosted options
• Compliance certifications and access controls
• Support and SLA expectations
• Ownership of scaling, upgrades, and reliability engineering

Strategic requirements:

• Pricing experimentation capabilities
• Multidimensional pricing support
• Contract flexibility across self-serve and enterprise motions
• Auditability across raw usage events, invoices, and finance records

Assessing scalability and reliability

Billing systems need to absorb product usage reliably because billing accuracy affects revenue, collections, and customer trust.

Orb's Enterprise platform is stress-tested at 250,000+ events per second. For substantially higher workloads, Orb's largest customers use Hosted Rollups to sustain several million events per second in production.

Lago supports multiple ingestion paths and gives self-hosted teams direct control over capacity planning and infrastructure configuration.

The relevant distinction is operational ownership. Lago can fit teams that want control over deployment and scaling decisions. Orb provides managed infrastructure alongside billing, pricing, invoicing, and finance workflows.

Streamlining finance operations with advanced revenue management software

Beyond invoicing: full revenue lifecycle management

Modern billing platforms increasingly extend beyond invoice generation to the broader revenue lifecycle:

• Accounts receivable automation with aging reports and collection workflows
• Revenue recognition with recognized, deferred, and unbilled revenue views
• ERP integration that creates accounting records and reduces manual journal work
• Audit readiness with change tracking and traceable billing data

Orb's NetSuite integration creates standard transaction records, including invoices, credit memos, customer deposits, and sales orders, rather than summary imports. This improves traceability and reduces manual reconciliation while allowing existing NetSuite ARM logic to remain intact.

Automating collections and dunning

Failed payments create collection work and can delay cash conversion. Effective dunning commonly includes:

• Configurable retry schedules
• Escalation workflows with customer communication
• Payment method update flows
• Service policies for persistent payment failure

Orb's collections automation supports configurable collection workflows. Orb's payment documentation covers Stripe for payment processing, including credit card and ACH collection, while Orb states that customers can continue using their preferred payment-processing partner.

Open-source billing: when self-hosting fits

Evaluating open-source and premium options

Lago's open-source core is distributed under AGPLv3 and can be self-hosted without a software license fee. Lago also offers premium capabilities in cloud and self-hosted configurations.

This model can be attractive when a team prioritizes:

• Direct code visibility
• Deployment on its own infrastructure
• Control over infrastructure topology and data location
• The ability to extend the codebase for internal requirements

Lago's premium packaging adds capabilities beyond the open-source core, including additional enterprise billing, finance, and integration workflows.

Operational considerations for self-hosting

Self-hosting changes who owns the operating layer. Typical responsibilities include:

• Infrastructure: database, cache, compute, storage, and networking
• Engineering: initial deployment, upgrades, and application maintenance
• Operations: monitoring, alerting, incident response, and capacity planning
• Security: patching, access control, and environment governance

The total operating model depends on infrastructure scale, staffing, compliance needs, and the degree of control a company wants. Managed platforms such as Orb shift those platform operations to the vendor while keeping pricing, billing, and finance workflows within the same managed system.

Empowering pricing teams: the role of price evolution tools

Simulating pricing changes before rollout

Pricing changes affect revenue, customer experience, and margin. Modeling proposed changes against real usage can help teams understand the impact before a new price reaches production.

Orb's pricing simulations enable teams to:

• Model revenue impact across customer segments
• Compare pricing scenarios side by side
• Identify customers affected by proposed changes
• Forecast revenue and customer impact before rollout

Lago provides projected usage for the current billing period and fee estimates for applicable pay-in-advance charges, while invoice previews are available in its premium offering. Orb's Simulations add a dedicated historical pricing workflow that can test proposed pricing against stored usage before deployment.

Reducing engineering dependency for pricing iteration

Pricing complexity compounds over time as companies add products, value metrics, credits, commitments, regional rules, and enterprise contract exceptions. In homegrown or tightly coupled systems, each new variation can become another engineering project.

Modern billing platforms move more of that pricing execution into configuration. Orb's price evolution capabilities are designed so product and finance teams can iterate on monetization while the billing system continues to operate from a consistent source of usage and pricing data.

Building customer trust: usage transparency and experience kits

Customer-facing usage visibility

Usage-based billing works best when customers can understand what is driving their charges. Useful customer-facing capabilities include:

• Usage dashboards with dimensional breakdowns
• Audit trails that connect activity to invoice charges
• Spend alerts before budget thresholds are reached
• Self-service access to historical invoices and usage data

Orb's Experience Kit provides customer-facing billing components, and spend controls help customers manage consumption proactively.

Enabling self-service activation

Self-service billing is particularly valuable for product-led and hybrid go-to-market motions. Common flows include:

• Viewing pricing and expected costs
• Selecting plans and completing checkout
• Upgrading or downgrading without sales involvement
• Adding credits or prepaid commitments

These capabilities can reduce transaction friction for self-serve customers while preserving a path to negotiated enterprise contracts.

Specialized billing: tailored solutions for AI/ML and cloud platforms

Unique requirements for AI companies

AI companies often require high pricing precision because token, inference, and compute rates can be fractions of a cent. Pricing may vary by model, input type, output type, region, or infrastructure class. Credit-based commercial models can add prepaid balances, expirations, drawdowns, and overage behavior.

Lago has traction in this market, including customers such as Mistral.ai, Together.ai, and Groq. Orb serves AI and infrastructure companies including Pinecone and supports multidimensional pricing for complex usage models.

Multidimensional pricing for cloud infrastructure

Cloud infrastructure providers often price across several dimensions such as region, cloud, model, instance type, and environment.

Orb's dimensional price groups support pricing across multiple usage dimensions, such as region, instance type, and environment, using a single pricing configuration for dimension combinations. See dimensional price groups.

Lago also supports combined-dimension pricing through billable metric filters and supports multiple pricing group keys for dimensional rate configuration. Both approaches let a single usage metric carry several pricing dimensions without defining a separate product for every combination.

Enterprise-grade billing: scalability, compliance, and integrations

Compliance requirements for enterprise deployment

Many enterprise buyers require a demonstrated security and compliance posture. Lago and Orb maintain SOC 2 Type II certification.

Common enterprise requirements include:

• Audit logging with change tracking
• Role-based access controls for pricing and invoice modifications
• Data encryption in transit and at rest
• Accounting period controls for closed financial periods
• Operational SLAs for business-critical billing infrastructure

Integration ecosystem comparison

Billing platforms need to connect product usage with finance and payment systems.

Lago integrations:

• Payment processors: Stripe, Adyen, GoCardless, community providers, and custom payment integrations
• CRM: Salesforce and HubSpot
• Accounting: NetSuite and Xero
• Event ingestion: API, batch, Kafka, Redpanda, Kinesis, and other supported paths

Orb integrations:

• Payment processing: Stripe gateway integration, with processor flexibility
• CRM: Salesforce
• Accounting and invoicing: NetSuite, QuickBooks, Bill.com
• Tax: Six providers, including Avalara, Anrok, and Stripe Tax
• Data warehouses: Snowflake and Redshift managed exports

Lago's breadth is useful for teams that value open deployment and direct integration control. Orb's advantage is that usage metering, pricing, invoicing, accounts receivable workflows, and downstream finance connectivity operate from one managed billing core.

Why Orb stands out for modern usage-based billing

On its standard ingestion path, Orb uses a query-based architecture that stores raw usage events immutably and computes billing from query-defined metrics. This architecture supports pricing evolution, historical analysis, corrections, and audit lineage without requiring the raw usage events to be recreated.

SQL-defined billable metrics support CASE statements, subqueries, AVG, MAX, COUNT DISTINCT, grouping, and computed properties, giving pricing teams a flexible query layer over usage data.

Pricing simulations provide a dedicated workflow to test proposed pricing against historical usage, compare scenarios, and understand customer and revenue impact before changes go live.

Managed high-volume ingestion is stress-tested at 250,000+ events per second. For substantially larger workloads, Orb's largest customers use Hosted Rollups to sustain several million events per second in production while keeping the billing workflow inside Orb.

Proven customer outcomes show how this architecture translates into operating leverage. Vercel decreased the time required to build and launch billing for new products by 80%. Stytch reduced time spent processing bills and invoicing by 75%. Orb reports that Replit has seen 40x revenue growth since using Orb to monetize usage.

Native NetSuite integration creates standard transaction records rather than summary imports, improving traceability and reducing manual reconciliation while allowing existing NetSuite ARM logic to remain intact.

For teams evaluating billing infrastructure, Orb also offers a demo environment for exploring platform capabilities.

Frequently asked questions

How does Lago's open-source license affect long-term costs compared with commercial platforms?

Lago's open-source core is distributed under AGPLv3 and is free to self-host from a software licensing perspective. Lago also offers paid premium capabilities that can run in managed or self-hosted environments. Total cost of ownership for self-hosting includes infrastructure, engineering, upgrades, monitoring, incident response, security operations, and any premium Lago capabilities a team chooses. A managed platform such as Orb packages platform operations with the billing product. The economic comparison therefore depends on event volume, infrastructure footprint, staffing, compliance requirements, and how much operational control a company wants to retain.

What payment processors does Lago support, and how does this compare with Orb after recent acquisitions?

Lago supports Stripe, Adyen, GoCardless, community integrations, and custom payment provider integrations. That multi-provider support is a meaningful Lago advantage for teams that want an open-source billing layer with direct control over payment integrations. Industry ownership changed in 2026. Stripe completed its acquisition of Metronome on January 14, 2026. Adyen's acquisition of Orb closed on July 1, 2026. Orb continues to operate as a stand-alone product and states that customers can continue using their preferred payment-processing partner.

Can Lago handle complex enterprise contract structures with prepaid commits and drawdowns?

Yes. Lago provides wallet-based credit capabilities for prepaid scenarios and has introduced a premium Quotes & Order Forms add-on for negotiated pricing, tiers, commitments, prepaid credits, discounts, pilots, and amendments. Orb supports prepaid credit blocks with expiration and automated drawdown. Scoped Credits add item-level application controls in Early Access. Each credit block can also carry an optional cost basis that determines how much revenue is recognized in Orb Revenue Reporting.

What is the typical implementation timeline for Lago versus Orb?

Implementation time for either platform depends on migration scope, integrations, contract complexity, data history, and deployment model. Lago's migration guidance describes different planning ranges based on customer count and migration complexity, while self-hosted deployments also include infrastructure setup and operating decisions. Orb has published implementation examples across different scopes. Stytch rolled out in two weeks, Vercel in roughly three weeks, Replit in one month with one engineer, and Pinecone completed its transition in three months.

How do Lago and Orb handle billing corrections and retroactive adjustments?

Lago supports pricing and dimensional changes for usage in open billing periods and provides workflows for invoice corrections and adjustments after billing records are finalized. Orb's query-based architecture supports retroactive price evaluation against stored raw usage events. Before invoices are finalized, affected billing can be recalculated as usage or pricing data changes. Finalized invoice corrections follow structured credit note, void, or reissue workflows. This gives teams an event-level source of truth for explaining how revised pricing or usage data flows into billing outcomes.