Self-host Logto on a VPS
Modern, developer-first customer identity: sign-in experiences, social login, and OIDC without the plumbing.
levelrail-cli templates deploy logto --name my-logtoSpecification
- Status
- Listed
- Category
- Security
- Services
- db, logto
- Ports
- 3001, 3002
- Volumes
- 1
- Memory
- about 1 GiB
- arm64
- image published
- amd64
- image published
- Settings to fill in
- none
- License
- Copyleft license, MPL-2.0
About Logto
Modern, developer-first customer identity: sign-in experiences, social login, and OIDC without the plumbing. Runs 2 containers (db, logto), with logto listening on port 3001 and keeps its data in named volumes.
What it deploys
Logto runs as 2 services in a single Compose app, listening on ports 3001, 3002, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| db | postgres | 16-alpine | none | logto_db_data -> /var/lib/postgresql/data |
| logto | svhd/logto | 1.43.0 | 3001, 3002 | none |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
- Host ports. It publishes ports 3001, 3002 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
You do not have to fill in anything. 2 secrets are generated at deploy and stored encrypted. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| db | POSTGRES_DB | Preset by the template |
| db | POSTGRES_PASSWORD | Generated at deploy |
| db | POSTGRES_USER | Preset by the template |
| logto | ADMIN_ENDPOINT | Preset by the template |
| logto | DB_URL | Generated at deploy |
| logto | ENDPOINT | Preset by the template |
| logto | TRUST_PROXY_HEADER | Preset by the template |
Install Logto on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get logto -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy logto --name my-logto
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Logto.
Docs and upstream
More in Security
- lldapA lightweight LDAP server with a friendly web UI, built for homelab and small-team authentication.
- Keycloak (Postgres)Keycloak backed by Postgres instead of its default embedded database, for a real multi-instance setup.
- KeycloakAn open-source identity and access management server with SSO, OAuth2, and SAML support.
- InfisicalAn open-source secrets manager to centralize API keys, database credentials, and app config.
- OAuth2 ProxyReverse proxy that puts an OAuth2 or OIDC login in front of any upstream. The install form carries oauth2-proxy.cfg as an editable file with a generated cookie secret, so it starts without extra flags.
- One-Time SecretShare a password or API key through a link that self-destructs after the first view, backed by Redis.