# Self-host Huginn

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

- Page: https://levelrail.com/templates/huginn/
- JSON: https://levelrail.com/templates/huginn.json
- Category: Applications
- Licence: MIT (Permissive license)
- Source: https://github.com/huginn/huginn
- Upstream docs: https://github.com/huginn/huginn/wiki

## Requirements
- Memory: about 1 GiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: v2026.11.01

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| huginn | huginn/huginn | v2026.11.01 | 3000 | mysql -> /var/lib/mysql |

## Environment

| Service | Variable | Kind |
| --- | --- | --- |
| huginn | APP_SECRET_TOKEN | generated |
| huginn | DOMAIN | preset |
| huginn | FORCE_SSL | preset |

## Deploy

### CLI

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

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/huginn/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. Sign in with the default admin account and change its password right away (see the Huginn docs for the default user).

## Questions

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

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