LoginSign Up
← Back to all sparks
L

Lago

FINANCE
Velocity0.0

Lago is layering AI agents and enterprise gates onto an already-deep usage-based billing engine.

usage-based billingwallet primitivesai agentsenterprise governancee-invoicingopen source
◆Current state
Lago is an open-source usage-based billing platform that has matured well past metering and into the full operational stack — entitlements, wallets, credit notes, e-invoicing, and analytics. Recent quarters have added an AI agent and MCP server for natural-language billing operations, ML-backed revenue forecasts, and the enterprise scaffolding (custom roles, security logs, audit-tracked communications) that procurement teams ask for. The wallet subsystem in particular is becoming a product of its own, with multiple wallets per customer, transaction limits, alerts, and full traceability of credit flows.
◆Where it's heading
Lago is positioning itself as the billing backbone for AI-native and credit-economy products — pricing units, prepaid wallet primitives, and an MCP server are not generic SaaS billing features. In parallel it's pulling forward enterprise governance: roles, security logs, e-invoicing, granular API endpoints. The combination reads as a deliberate move upmarket, with the AI-billing angle as the wedge for new logos and the governance work as the ceiling-raiser for existing ones.
◆Prediction
Expect more agentic surface (additional AI agent personas beyond the Billing Assistant, or MCP server hardening with action-confirmation flows), and continued e-invoicing jurisdiction coverage following the France template — Italy, Belgium, or another Peppol-aligned market would be the natural next stop.

◆Recent moves

  1. 2mo ago

    ​Wallet traceability — Follow every credit from top-up to deduction

    Wallets now expose full audit trails of how credits flow — every top-up linked to the transactions it funded, every deduction back to its source. Aimed at teams running prepaid credit systems where reconciliation and disputes are a recurring drain. A predictable depth move on top of the multi-wallet primitive shipped last December.

    View source ↗
  2. 3mo ago

    Credit alerts, security logs, and granular charge APIs

    A bundled month: threshold-based credit alerts via webhook, an enterprise-grade security log surface, and a new set of granular API endpoints for managing charges without re-sending entire plan payloads. All three sit on the same arc — making the existing primitives (wallets, identity, plans) more operable at scale.

    View source ↗
  3. 4mo ago

    Multi-payment-method customers and a Superset-based analytics rebuild

    Three substantial adds: multiple payment methods per customer (assigned independently to subscriptions, invoices, top-ups), a complete analytics rebuild on Apache Superset replacing the old fixed dashboards, and webhook event filtering. The analytics rewrite is the headline change — composable dashboards and exportable data widen the audience well beyond engineers.

    View source ↗
  4. 5mo ago

    Fixed charges and custom roles land in the core platform

    ⚡ SPARK

    Two enterprise-grade primitives land together: fixed charges (recurring non-usage fees natively in plans, replacing one-off-invoice workarounds) and custom roles with granular permissions. Together they remove two of the most common reasons buyers escalated to enterprise plans on competing tools.

    View source ↗
  5. 6mo ago

    MCP server, Billing Assistant agent, and multiple wallets per customer

    ⚡ SPARK

    Lago ships an MCP server and a conversational Billing Assistant in the same release, alongside multiple-wallets-per-customer. The AI surface isn't a bolt-on demo — it's pitched as the way agents and LLMs talk to enterprise billing data, with safeguards on destructive actions baked in.

    View source ↗
  6. 7mo ago

    E-invoicing for France with reusable templates for new jurisdictions

    First jurisdiction of e-invoicing support goes live for France — hybrid PDF/A-3 with embedded UN/CEFACT XML plus a pure UBL EN 16931 file. Transmission still goes through customer-operated portal upload, but the document-format work is the hard part and is now reusable across similar jurisdictions.

    View source ↗