Self-host Fenrus with Levelrail
Self-hosted dashboard that groups your apps as tiles with live status widgets, themes and per user pages.
- Authorrevenz
- LicenceMIT
- Memory256 MiB
- Services1
How to self-host Fenrus
-
Pull the images
One image is pulled on your server.
Show images
revenz/fenrus:26.10@sha256:7728749bb98c3b0862c853ebf9f741d7e43fddcd84a1ddb8ac73d03ae9741f99
-
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
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.
After the first start
- Open the address, create your account on first visit, then add groups and app tiles.
Fenrus requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive 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 Fenrus. 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 Fenrus docs page.
Deploy Fenrus your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Fenrus from the CLI
levelrail-cli templates deploy fenrus --name my-fenrus Deploy Fenrus with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/fenrus/deploy Fenrus configuration
Fenrus services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| fenrus | revenz/fenrus:26.10@sha256:7728749bb98c3b0862c853ebf9f741d7e43fddcd84a1ddb8ac73d03ae9741f99 | 3000 | data -> /app/data |
Fenrus environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: data -> /app/data
Fenrus FAQ
How much memory does Fenrus need?
The catalog lists about 256 MiB of memory for Fenrus.
Does Fenrus run on arm64?
For Fenrus, arm64 support is not confirmed; amd64 is unknown.
What licence is Fenrus under?
Fenrus is licensed under MIT, which is permissive, with few conditions on reuse.
Does Fenrus need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Fenrus use?
Fenrus listens on port 3000 inside the stack.
Where does Fenrus keep its data?
In a named volume: data mounted at /app/data.
Can I deploy Fenrus 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 Fenrus, 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 revenz/fenrus:26.10@sha256:7728749bb98c3b0862c853ebf9f741d7e43fddcd84a1ddb8ac73d03ae9741f99 is what you deploy there.