Deploy LLDAP
LLDAP 0.6: light LDAP server for user management, with a web UI.
lldap
Just deployed
/data
Deploy and Host LLDAP on Railway
LLDAP is a light LDAP server built for managing users and groups, not for general-purpose directory use. It comes with a friendly web interface and a GraphQL API, and many self-hosted apps can log users in against it, including Nextcloud, Gitea, Jellyfin, Authelia, Grafana and Keycloak.
About Hosting LLDAP
This template runs the official lldap/lldap:v0.6.3 image as one service with SQLite on a Railway volume. The web interface is public and protected by the admin password generated for this deployment. The LDAP port 3890 stays on Railway's private network, because plain LDAP sends passwords unencrypted: apps in the same project connect to lldap.railway.internal:3890 over IPv4 or IPv6. JWT and key-seed secrets are generated and stable, so logins and stored passwords survive redeploys. The base DN defaults to dc=example,dc=com; change it before the first boot if you need another. LLDAP uses very little memory and fits the Hobby plan.
Common Use Cases
- One set of users and groups for many self-hosted apps
- LDAP backend for Authelia, Authentik or Keycloak
- Letting non-technical people manage accounts in a simple web UI
Dependencies for LLDAP Hosting
lldap/lldap:v0.6.3(official image)- A Railway volume at
/datafor the SQLite database
Deployment Dependencies
Implementation Details
| Service | Source | Networking | Storage |
|---|---|---|---|
| lldap | lldap/lldap:v0.6.3 | public domain on 17170 (web), private 3890 (LDAP) | volume at /data |
| Variable | Default | Purpose |
|---|---|---|
LLDAP_LDAP_USER_PASS | generated | Password of the admin user |
LLDAP_LDAP_BASE_DN | dc=example,dc=com | Directory base DN |
LLDAP_JWT_SECRET | generated | Signs web sessions |
LLDAP_KEY_SEED | generated | Seed for the password-hashing key |
LLDAP_HTTP_URL | https://${{RAILWAY_PUBLIC_DOMAIN}} | Public URL of the web UI |
Notes:
- Apps bind with
uid=admin,ou=people,dc=example,dc=comor a dedicated user in thelldap_strict_readonlygroup. - To reach LDAP from outside Railway, add a TCP proxy for port 3890 only if you accept unencrypted binds, or set up LDAPS.
This is a community-maintained deployment package and does not imply affiliation with or endorsement by the LLDAP project.
Why Deploy LLDAP 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 LLDAP 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.
Template Content
lldap
lldap/lldap:v0.6.3
