Lago
A metering and usage-based billing platform that turns API calls, tokens or compute into prices, credits, invoices and payments.
Lago at a glance
What is Lago?
Lago records product usage events and converts them into charges based on the pricing you define: per token, per API call, per compute hour or any other unit. It handles subscriptions, credits, entitlements, invoices, payments and revenue analytics. You can use it for your own product, or embed it to bill your customers' customers. It offers a REST API with SDKs, a CLI and an MCP server for AI assistants, plus a demo that prices a sample AI workload locally.
Good fit if
- You sell an API or AI product with usage-based pricing and want billing logic you control.
- You want to avoid revenue-share fees of a hosted billing vendor.
Look elsewhere if
- You need to route payments across many processors rather than calculate bills: HyperSwitch.
Before you adopt it
Lago is AGPL-3.0, and the repository contains no paid parts; the company also offers Lago Cloud. Work is shared among about a dozen developers. The Docker Compose stack runs PostgreSQL and Redis among several services. Review financial changes before running them, as the README itself advises for agent-driven work.
Drafted with AI from the project's README and repository data, then checked against that data on 31 October 2026. Report a correction
How to run Lago yourself
- Docker
- Dockerfile or compose file in the repository
- Compose file
- docker-compose.yml: 8 services (postgres, redis)
- Setup effort
- 4 of 5, judged from the compose file
- Kubernetes
- No Helm chart in the repository
- Desktop and mobile
- No app builds in GitHub releases
- Interface languages
- English only
Install instructions: getlago.com or the README on GitHub.
Lago health: is it still maintained?
75 of 100, actively developed
Read from GitHub on 5 November 2026. How the score works
Lago license: is it open source?
Lago uses AGPL-3.0, an open-source license approved by the OSI.
- February 2022First published on GitHub.
- TodayAGPL-3.0.
Lago for developers
Written in
- Go 84%
- Shell 10%
- Dockerfile 6%
- Procfile <1%
Getting involved
Language shares are GitHub’s count of the code in the repository.
Alternatives to Lago
- HyperSwitchOpen source, composable payments platform | PCI compliant | SaaS and Self-host options | Enables… 84 health · Apache-2.0 · 45.7k stars
- LangfuseOpen source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform. 81 health · MIT · 37k stars
- GotifyA simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui) 77 health · MIT · 16.2k stars
- OpikDebug, evaluate, and monitor your LLM applications, RAG systems, and agentic workflows with comprehensive… 91 health · Apache-2.0 · 23.2k stars
- CoderSecure environments for developers and their agents 81 health · AGPL-3.0 · 17.3k stars
Questions about Lago
Is Lago open source?
Yes. Lago is published under AGPL-3.0, an OSI-approved open-source license.
Is Lago still maintained?
Its health score is 75 of 100 (actively developed). It had 72 commits in the last 90 days, the latest on 4 November 2026, and its latest release came out on 2 November 2026.
How do I run Lago?
You can run it with Docker. The README on GitHub has the exact steps.
What is Lago written in?
Lago is written mainly in Go (84% of the code), with Shell (10%) and Dockerfile (6%), by GitHub’s count of the repository.
What are the alternatives to Lago?
Close alternatives in the Developer tools category include HyperSwitch, Langfuse, Gotify.