Single sign-on and two-factor portal. The admin user is created at first boot from a generated password (visible in the service environment settings, never on a process command line); more users go in /data/users.yml. Sessions are scoped to this portal’s own host, so widen the cookie domain in /config/configuration.yml before protecting other apps. One-time codes are written to /data/notification.txt.
This page describes the Levelrail template for Authelia (Security). It deploys the services below as one Docker Compose app on your own server. Project site: https://www.authelia.com/configuration/prologue/introduction/.
Recommended memory: about 256 MiB.
Services, ports and volumes
Environment variables
Passwords and keys marked as generated are created for you when the app is deployed and stored as secrets. Values are not shown here.
Security and requirements
Level: Standard.
What this template needs:
- Passwords and keys are generated at deploy time (
authelia): ADMIN_PASSWORD, AUTHELIA_IDENTITY_VALIDATION_RESET_PASSWORD_JWT_SECRET, AUTHELIA_SESSION_SECRET, AUTHELIA_STORAGE_ENCRYPTION_KEY.
- Stores data in named volumes (
authelia): config, data.
What Levelrail adds around it:
- Automatic HTTPS and an ingress shield in front of every domain.
- Secrets are generated, stored encrypted and masked in logs and the UI.
- Named volumes can be backed up and restored.
- Deploys are gated on the health check before traffic switches.
- One-step rollback to the previous revision.
- Exposure report shows what is reachable from outside.
- Host firewall rules managed for published ports.
Deploy Authelia with Levelrail
In the dashboard, open Apps, choose New app, then Browse templates, and select Authelia. Review the Compose body and deploy.
With the CLI:
See the service template catalog for how templates work, and Getting started if you have not installed Levelrail yet.
More Security templates
All templates are listed in the self-host gallery. Last modified on October 30, 2026