Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

lago

lago: A programmable system between product usage and revenue.

What problem it solves

Product usage must be translated into pricing, entitlements, invoices, payments, and revenue without rebuilding billing whenever pricing changes. Lago addresses this by providing metering, pricing, credit, entitlement, invoicing, and payment orchestration primitives through APIs, SDKs, webhooks, an MCP server, and a web interface.

Key features

  • Usage metering — Ingest product usage as events and aggregate it into billable metrics with filters, dimensions, custom aggregations, batch ingestion, and transaction-based idempotency.

    Source: README

  • Pricing and entitlements — Model usage-based, recurring, prepaid, percentage, graduated, package, volume, minimum-commitment, and hybrid charges. Control access with entitlements, allowances, wallets, credit grants, top-ups, and usage alerts.

    Source: README

  • Invoicing and payment orchestration — Create invoices and credit notes, support taxes, multiple currencies and entities, and coordinate payment providers with retries, dunning, and payment-status synchronization.

    Source: README

  • Agent-accessible interfaces — Expose billing capabilities through a REST API, SDKs, a CLI, an MCP server, and Agent SDKs. These interfaces let applications, internal tools, and agents work with the same billing primitives.

    Source: README

  • Direct and embedded billing — Use the same engine to monetize a product directly or let platforms offer metering and billing to their customers through APIs and white-label interfaces.

    Source: README

Quick start

Copied verbatim from the project's README.

git clone --depth 1 https://github.com/getlago/lago.git
cd lago

echo "LAGO_RSA_PRIVATE_KEY=\"$(openssl genrsa 2048 | openssl base64 -A)\"" >> .env
docker compose up -d
./examples/agentic-ai-demo/run.sh

Who it may suit

Inference: may suit teams building usage-based products, AI applications, compute services, subscriptions, or platforms that need to meter and bill their own customers. It may also suit platforms that want to provide embedded metering and billing capabilities.

Topics to discuss

  • Which usage-based pricing models should be added to the platform next?

  • How should agent-facing billing tools enforce confirmation and access controls?

  • What deployment and observability practices should the community standardize for self-hosted installations?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/getlago/lago#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/getlago/lago

Comments

…