Self-host Organizr with Levelrail
A unified homepage and tabbed dashboard for linking every self-hosted app behind one interface.
- Authorcausefx
- LicenceGPL-3.0
- Memory128 MiB
- Archarm64
- Services1
How to self-host Organizr
-
Pull the images
One image is pulled on your server.
Show images
organizr/organizr:latest
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Organizr requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (organizr/organizr:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Organizr. 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 Organizr docs page.
Deploy Organizr your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Organizr from the CLI
levelrail-cli templates deploy organizr --name my-organizr Deploy Organizr with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/organizr/deploy Organizr configuration
Organizr services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| organizr | organizr/organizr:latest | 80 | organizr_data -> /config |
Organizr environment variables
| Variable | Service | Value |
|---|---|---|
| branch | organizr | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: organizr_data -> /config
Organizr FAQ
How much memory does Organizr need?
The catalog lists about 128 MiB of memory for Organizr.
Does Organizr run on arm64?
For Organizr, an arm64 image is published; amd64 is image published.
What licence is Organizr under?
Organizr is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Organizr need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Organizr use?
Organizr listens on port 80 inside the stack.
Where does Organizr keep its data?
In a named volume: organizr_data mounted at /config.
Can I deploy Organizr 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 Organizr, 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 organizr/organizr:latest is what you deploy there.