Lago

Lago sells open-source billing for usage, subscription, and hybrid pricing to AI, SaaS, fintech, and infrastructure companies. Teams run Lago Cloud or deploy the same AGPLv3 code on their own infrastructure (High). Lago raised $22 million, a $15 million Series A led by FirstMark and a $7 million seed led by SignalFire (High). Revenue and customer count are not published. The bottom line is that Lago is the open-source choice for teams that want to own their billing data and metering.

Lago says it processes up to 1,000,000 billing events per second (High, self-reported). It is not a payment processor and keeps billing independent of the processor a customer chooses. The GitHub repository shipped version 1.56.0 on November 2, 2026.

What does it sell?

Lago combines metering, subscriptions, prepaid credits, entitlements, invoicing, payment orchestration, and revenue analytics through one API (High). Lago Premium is available on Cloud and self-hosted, with pricing only on request. Dunning, tax integrations, progressive billing, and CRM and accounting integrations are add-ons on demand. Lago Embedded lets platforms run billing for their own customers.

The open-source edition is free to run, but the team operates it. Premium adds RBAC, SSO through Okta, audit logs, and support with business-hours incident management.

What does it ship for AI agents?

Shipped: an MIT-licensed MCP server reads and writes invoices, usage, customers, payments, credit notes, and coupons (High). It inherits the permissions of its Lago API key. Agent SDKs for Python and JavaScript meter token and model-cost events from OpenAI, Anthropic, Mistral, Gemini, and AWS Bedrock clients. The Finance Assistant answers read-only questions, and the Billing Assistant runs operations with confirmation for destructive actions.

Absent: a pricing assistant. Lago’s March 2026 post lists it as on the roadmap (High). The Billing Assistant is premium and available on request.

What does a buyer need to check?

The MCP server writes billing data. Lago itself warns teams to treat agent credentials as privileged, review tool calls, and keep human confirmation around sensitive changes. Buyers must scope API keys before connecting any agent.

Self-hosting moves the work in-house. AGPLv3 terms apply to the core, and the team owns uptime, upgrades, and security. Collections depth is limited to dunning, which is an add-on.

What to watch

• A new funding round after the 2024 raise. Shows first on the Lago blog.
• The pricing assistant leaving the roadmap. Shows first in Lago’s GitHub releases.
• Logos moving from Orb or Metronome. Shows first in Lago case studies.