← Templates · Applications
LA
Lago
Community5 services
Lago, the open-source billing engine — usage-based metering, invoicing and subscriptions for your own product.
| Runs | 5 services |
|---|---|
| Stack | lagolago-workerlago-frontlago-dblago-redis |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 5 services in this stack together — lago, lago-worker, lago-front, lago-db, lago-redis — wired to reach each other over the private network, on a server you already pay for.
Deploying Lago is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Usage-based billing and metering for a SaaS product
- Running your own invoicing and subscription engine instead of a per-seat billing SaaS
Good to know
- Postgres and Redis are wired up automatically across api, worker and front
- PDF invoice generation is disabled (LAGO_DISABLE_PDF_GENERATION) since the compose's Gotenberg service isn't included here
- LAGO_RSA_PRIVATE_KEY needs a real RSA private key — Railyard's secret masking only generates random hex, so replace the generated placeholder with a real key (e.g. openssl genrsa 2048) before the api container will boot