Lago front

Lago front is the open-source web front end for Lago, a self-hosted billing platform.

  • Business & Finance
  • Tools & Utilities
Lago front is the open-source web front end for Lago, a self-hosted billing platform. It provides a dashboard for managing customers, products, pricing, subscriptions, invoices, and payment runs. It is for teams that want to run their own usage- and subscription-based billing stack while keeping full control over their financial data.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
100last commit 4 days ago
Popular
44163 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

GitHub stars
163
Open issues
49
Last commit
2026-11-17
Latest release
v1.57.0
License
AGPL-3.0
Activity
steady

Checked 4 days ago - source: GitHub (getlago/lago-front)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start with the right service profile Before running Docker Compose, choose a profile that matches your setup, such as all, all-no-pg, or all-no-db. This prevents missing required services or accidentally creating extra databases and keys. source
  • Download and fill in the light config Download the light docker-compose.yml and .env example, then edit your .env before starting. The .env holds settings for the reverse proxy and SSL support, so missing values can stop the app from running correctly. source
  • Enable SSL only after certificates are ready If you want HTTPS, set LAGO_DISABLE_SSL=false in the .env file inside the storage folder used for settings. This turns on SSL support, but you still need to configure your certificates and traffic termination separately. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I run isolated Lago front instances during development?

The lago-worktree script creates isolated frontend instances using git worktrees. Each worktree gets its own branch, Docker container, and port, while services such as the database, Redis, Redpanda, and PDF service are shared with the main stack.

What does the Make Tests development skill do?

It detects modified component files from a pull request or branch, adds data-test attributes, and creates or migrates tests following project testing conventions.

Where should I look for persistent storage, SMTP, TLS, object storage, Redis, and database settings in self-hosted Lago?

Use the self-hosted deployment guide, which covers persistent storage, SMTP, TLS, object storage, Redis, database configuration, and upgrades.

How can I discover all available Lago documentation pages?

Fetch the llms.txt documentation index and use it to discover all available pages before exploring further.

Answers sourced from github.com, github.com, www.getlago.com

Community

Collected 48 days ago - public community threads