# Self-host Fenrus

> Self-hosted dashboard that groups your apps as tiles with live status widgets, themes and per user pages.

- Page: https://levelrail.com/templates/fenrus/
- JSON: https://levelrail.com/templates/fenrus.json
- Category: Dashboard
- Licence: MIT (Permissive license)
- Source: https://github.com/revenz/Fenrus
- Upstream docs: https://github.com/revenz/Fenrus#readme

## Requirements
- Memory: about 256 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: 7728749bb98c3b0862c853ebf9f741d7e43fddcd84a1ddb8ac73d03ae9741f99

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| fenrus | revenz/fenrus:26.10@sha256 | 7728749bb98c3b0862c853ebf9f741d7e43fddcd84a1ddb8ac73d03ae9741f99 | 3000 | data -> /app/data |

## Deploy

### CLI

```bash
levelrail-cli templates deploy fenrus --name my-fenrus
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/fenrus/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## First run
1. Open the address, create your account on first visit, then add groups and app tiles.

## Questions

### 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.

Self-host Fenrus, Fenrus docker compose file, deploy Fenrus on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
