Deploy and Host Authentik on Railway

Authentik can be seamlessly integrated into existing environments to support new protocols. authentik is also a great solution for implementing sign-up, recovery, and other similar features in your application, saving you the hassle of dealing with them.

About Hosting Authentik

This template deploys the required docker images for it to work. For initial configuration, visit your server url at {URL}/if/flow/initial-setup/

Common Use Cases

SSO for your apps and infrastructure with OIDC, SAML, LDAP and proxy auth
Sign-up, recovery and MFA flows without building them yourself
Protecting internal tools behind a single identity provider

Dependencies for Authentik Hosting

A Postgres database (deployed by this template; authentik 2025.10+ needs nothing else)
An authentik server service and a worker service (both deployed by this template)

Deployment Dependencies

Why Deploy Authentik 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 Authentik 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

Pinned authentik 2026.8.5 (was floating latest).
BREAKING (upstream, authentik 2025.10): Redis was removed from authentik's stack - everything runs on PostgreSQL now. The Redis service in this template is no longer used and can be deleted from new deploys. Existing deploys that update their image past 2025.10 can delete their Redis service and AUTHENTIK_REDIS__* variables.
DB connection now uses Railway private networking.
Postgres pinned to 17.