Skip to content
appsgit

Lago

Metering and usage-based billing.

github.com/getlago/lago

GitHub stats

GitHub stars
10,657
Forks
767
Open issues
17
Commits, last 12 months
174
Last commit
Oct 1, 2026
Latest release
v1.53.0Sep 8, 2026
Created
Feb 28, 2022

Data from the GitHub API, refreshed daily.

About Lago

Metering and usage-based billing. Lago is open source under the AGPL-3.0 license and written mainly in Go, so you can read the code, run it on your own hardware and keep full control of your data.

The project has 10,657 stars and 767 forks on GitHub, with 174 commits over the last year. It ships a Docker image, which makes it a good fit for a small VPS or a home server running Docker Compose.

Topics

  • billing
  • fintech
  • invoices
  • payments
  • usage-based-billing
  • subscriptions
  • metering
  • pricing
  • analytics
  • open-source

Repository preview

Lago repository previewgetlago/lagoOpen repository

FAQ

Lago FAQ

Still curious? Email info@appsgit.com.

What is Lago?

Lago is a free, open-source app you can host on your own server, listed in our Finance & Budgeting category. Metering and usage-based billing. The source code lives at github.com/getlago/lago, where it has 10,657 stars.

Is Lago free and open source?

Yes. Lago is open-source software released under the AGPL-3.0 license, so you can self-host it at no cost. You only pay for the server it runs on, and some projects also offer an optional paid cloud plan.

Can I run Lago with Docker?

Yes. Lago provides a Docker image, so you can run it on any Linux server with Docker and Docker Compose installed. The project README lists the image name and the environment variables to set.

What are the best alternatives to Lago?

Popular open-source alternatives to Lago include HyperSwitch, Actual and Firefly III.

Is Lago actively maintained?

The most recent commit to Lago was on Oct 1, 2026 with 174 commits in the past twelve months. The latest release is v1.53.0, published Sep 8, 2026. Check the open issues on GitHub to gauge how quickly maintainers respond.