Deploy Lago (working)
[2026-11-04] Lago v1.56. BREAKING for old deploys (see README).
lago-clock
Just deployed
lago-api
Just deployed
/app/storage
Just deployed
/var/lib/postgresql/data
lago-worker
Just deployed
Redis
Just deployed
/data
lago-front
Just deployed
Deploy and Host Lago on Railway
Original Lago template made by another user was not working so I made this one. It will spin a postgres db, a redis db and both the frontend and api images necessary to run lago in the simplest manner. After deployed, you can access the service through the frontend url (after creating an account).
About Hosting Lago
This template deploys everything needed to run Lago on Railway.
Common Use Cases
- Usage-based and subscription billing with metered events
- Invoicing, coupons, prepaid credits and webhooks for your SaaS
- An open source alternative to Stripe Billing / Chargebee
Dependencies for Lago Hosting
- A Postgres database with the pg_partman extension (getlago/postgres-partman, deployed by this template)
- A Redis instance (deployed by this template)
- lago-api, lago-worker, lago-clock and lago-front services (all deployed by this template)
Deployment Dependencies
Why Deploy Lago on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Lago on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Update 2026-10-27
- Updated getlago/api and getlago/front from v0.49.1-beta to v1.55.0.
- BREAKING: Lago v1.x requires the pg_partman Postgres extension - the DB service now uses getlago/postgres-partman:15.0-alpine. Existing v0.49 deploys cannot simply swap images: deploy fresh and migrate data, or follow Lago's upgrade path version by version.
- Encryption env vars renamed to their LAGO_ENCRYPTION_* names; LAGO_RSA_PRIVATE_KEY must be a base64-encoded PEM key. The template ships a default - CHANGE IT for production: openssl genrsa 2048 | base64 -w0
- Added lago-worker (Sidekiq) and lago-clock services, required for billing jobs.
- Redis switched from bitnami to redis:8.2.1; DB/Redis moved to private networking.
Update 2026-11-04
- Bumped Lago images to v1.56.0. The hardened front image now listens on port 8080, the template's front PORT is updated to match; Redis bumped to 8.2.3.
Template Content
lago-clock
getlago/api:v1.56.0lago-api
getlago/api:v1.56.0lago-worker
getlago/api:v1.56.0Redis
redis:8.2.3lago-front
getlago/front:v1.56.0