Self-host Tinyauth with Levelrail
A small login screen and forward-auth server that protects other apps behind your reverse proxy with username and password or OAuth. Runs on SQLite in one container. Users are set with a bcrypt hash in the install form.
- Authortinyauthapp
- LicenceAGPL-3.0
- Memory64 MiB
- Archarm64
- Services1
Needs setup: set TINYAUTH_AUTH_USERS before the first start.
How to self-host Tinyauth
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/tinyauthapp/tinyauth:v5.2.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
3 settings are preset, you provide 1 value.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the app address and sign in with the user you set in the install form.
Tinyauth requirements
- Memory
- About 64 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- 1 to fill in
- License
- AGPL-3.0, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Tinyauth. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Tinyauth docs page.
Deploy Tinyauth your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Tinyauth from the CLI
levelrail-cli templates install tinyauth --name my-tinyauth --env TINYAUTH_USERS=VALUE Deploy Tinyauth with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/tinyauth/install \
-d '{
"name": "my-tinyauth",
"env": { "TINYAUTH_USERS": "VALUE" }
}' Tinyauth configuration
Tinyauth services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| tinyauth | ghcr.io/tinyauthapp/tinyauth:v5.2.0 | 3000 | data -> /data |
Tinyauth environment variables
| Variable | Service | Value |
|---|---|---|
| TINYAUTH_ANALYTICS_ENABLED | tinyauth | Preset by the template |
| TINYAUTH_APPURL | tinyauth | Preset by the template |
| TINYAUTH_AUTH_SECURECOOKIE | tinyauth | Preset by the template |
| TINYAUTH_AUTH_USERS | tinyauth | You must set this |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: data -> /data
Tinyauth FAQ
How much memory does Tinyauth need?
The catalog lists about 64 MiB of memory for Tinyauth.
Does Tinyauth run on arm64?
For Tinyauth, an arm64 image is published; amd64 is image published.
What licence is Tinyauth under?
Tinyauth is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Tinyauth need configuration before it starts?
Yes. Tinyauth has required settings: TINYAUTH_AUTH_USERS.
Which ports does Tinyauth use?
Tinyauth listens on port 3000 inside the stack.
Where does Tinyauth keep its data?
In a named volume: data mounted at /data.
Can I deploy Tinyauth on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Tinyauth, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/tinyauthapp/tinyauth:v5.2.0 is what you deploy there.