Deploy Umami Analytics with PostgreSQL & 2FA
Website analytics with Postgres and generated app and 2FA encryption keys.
Postgres
Just deployed
Umami
Just deployed
Deploy and Host Umami Analytics with PostgreSQL & 2FA on Railway
Website analytics with Postgres and generated app and 2FA encryption keys.
About Hosting Umami Analytics with PostgreSQL & 2FA
Deploying this template creates Postgres, Umami in your Railway project. The application receives an HTTPS domain automatically. Database and Redis services, when included, use private networking and generated credentials. Persistent data is stored on the included volumes or object storage, so application redeploys do not discard it.
Why Deploy Umami Analytics with PostgreSQL & 2FA on Railway
- Official Umami container plus a private PostgreSQL database.
- Generated application secret and dedicated 64-character hex key for 2FA.
- Automatic HTTPS domain and a heartbeat health check.
Common Use Cases
- Measure website visits and traffic sources.
- Compare campaigns and custom conversion events.
- Give a team control of its own analytics database.
Dependencies for Umami Analytics with PostgreSQL & 2FA
- A Railway account and a plan with capacity for 2 service(s).
- Included services: Postgres, Umami.
- 1 persistent volume(s), provisioned by this template.
- External integrations, mail delivery and your own business data are configured after installation as needed.
First launch
- Wait for the application and database to become ready.
- Open the generated domain. The upstream initial login is admin / umami; change that password immediately.
- Enable two-factor authentication in your profile.
- Add your website and install the tracking script shown by Umami.
Operations
PostgreSQL holds the analytics and account data. Back it up and retain both APP_SECRET and TWO_FACTOR_ENCRYPTION_KEY before upgrades. A tracking installation on your website is still required; deploying this template does not add analytics to other sites automatically.
Images are pinned to verified upstream image digests captured on 2026-10-17. Review upstream release notes, back up persistent data and update the image deliberately when upgrading. Railway charges the deployer for running services, storage and network usage.
Support and upstream
For Railway template wiring or deployment issues, use the discussion/support link on this template page. Include service names and redacted logs; omit passwords and tokens. Application documentation:
Template Content
Postgres
postgres