Self-host Huginn with Levelrail
A tool that builds agents which watch the web and act for you, such as tracking a page, filtering a feed or sending an email when something changes. This image bundles its own MySQL, so it is one container.
- Authorhuginn
- LicenceMIT
- Memory1 GiB
- Services1
How to self-host Huginn
-
Pull the images
One image is pulled on your server.
Show images
huginn/huginn:v2026.11.01
-
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
1 secret is generated and stored encrypted, 2 settings are 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.
After the first start
- Sign in with the default admin account and change its password right away (see the Huginn docs for the default user).
Huginn requirements
- Memory
- About 1 GiB
- 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 Huginn. 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 Huginn docs page.
Deploy Huginn your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Huginn from the CLI
levelrail-cli templates deploy huginn --name my-huginn Deploy Huginn with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/huginn/deploy Huginn configuration
Huginn services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| huginn | huginn/huginn:v2026.11.01 | 3000 | mysql -> /var/lib/mysql |
Huginn environment variables
| Variable | Service | Value |
|---|---|---|
| APP_SECRET_TOKEN | huginn | Generated at deploy |
| DOMAIN | huginn | Preset by the template |
| FORCE_SSL | huginn | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: mysql -> /var/lib/mysql
Huginn FAQ
How much memory does Huginn need?
The catalog lists about 1 GiB of memory for Huginn.
Does Huginn run on arm64?
For Huginn, arm64 support is not confirmed; amd64 is unknown.
What licence is Huginn under?
Huginn is licensed under MIT, which is permissive, with few conditions on reuse.
Does Huginn need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Huginn use?
Huginn listens on port 3000 inside the stack.
Where does Huginn keep its data?
In a named volume: mysql mounted at /var/lib/mysql.
Can I deploy Huginn 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 Huginn, 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 huginn/huginn:v2026.11.01 is what you deploy there.