Huginn hosting

Agents that watch the web and act when something changes.

AutomationMITfrom $5.99/mo
In short

Huginn hosting at AIHostBox means a dedicated, single-tenant Huginn instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $5.99 per month and the admin account, the data and any API keys are yours.

Website watchersRSSEmail agentsEvent chains

Huginn is a long-running, MIT-licensed Ruby on Rails project, started by Andrew Cantino and kept going by community contributors, for building agents that watch and act on your behalf. Each agent does one small job: a WebsiteAgent scrapes a page with CSS or XPath selectors, an RssAgent reads a feed, a TriggerAgent matches a pattern, an EmailDigestAgent bundles results. Agents pass JSON events to each other, Liquid templates reshape them, and groups of agents are saved as scenarios you can export and share.

It differs from newer workflow builders in its unit of work. Instead of a flow that runs once per trigger, Huginn keeps dozens of agents polling on their own schedules and storing the events they produce, closer to a personal IFTTT that remembers history. That is why it needs a server: the scheduler and background workers must run continuously for checks to fire on time. The codebase now also includes an OpenAI LLM agent that can call any OpenAI-compatible endpoint, Ollama included.

Huginn hosting plans

StarterPersonal use & small teams
2 GB RAM · 1 vCPU · NVMe
$5.99/mo
Order
PlusBusy workflows & communities
4 GB RAM · 2 vCPU · NVMe
$9.99/mo
Order
ProHeavy pipelines & many users
8 GB RAM · 3 vCPU · NVMe
$16.99/mo
Order

Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.

How we run Huginn

The official Huginn container from ghcr.io/huginn/huginn (Rails web server, scheduler and delayed_job workers) connected to a separate PostgreSQL database with DATABASE_ADAPTER=postgresql.

What we configure for you

  • APP_SECRET_TOKEN generated fresh instead of the example value
  • DOMAIN set to your hostname with FORCE_SSL=true
  • INVITATION_CODE so only people you invite can register
  • SMTP_SERVER, SMTP_USER_NAME and EMAIL_FROM_ADDRESS so email and digest agents can send
  • TIMEZONE so schedules fire at your local hours
  • OPENAI_API_KEY and OPENAI_BASE_URL if you use the LLM agents

Which plan fits

Starter (2 GB, 1 vCPU) runs a personal set of watchers comfortably, typically dozens of agents checking every few minutes to hourly. Plus (4 GB, 2 vCPU) suits heavier scraping, several users or agents that fire frequently. Pro (8 GB, 3 vCPU) is for large event volumes where the database and workers both need headroom.

The honest limits

Huginn is volunteer-maintained and moves slowly; some agents target services whose APIs have changed or closed, so check an agent still works before building on it. The WebsiteAgent does not execute JavaScript, so script-heavy pages need an external rendering service.

What people run Huginn for

Change detection

Know when a competitor’s pricing page changes.

Personal feeds

Compose sources into one digest.

LLM step in a monitoring chain

Summarise or classify new items with the OpenAI LLM agent against a hosted model or your own Ollama.

Webhook glue

Receive events with a WebhookAgent and forward reshaped JSON with a PostAgent.

Licence and version policy

ItemPosition
Upstream licenceMIT
Sold as managed hostingYes
TenancySingle tenant — one customer per instance
PatchingCritical advisories within 24 hours, high severity within 72

Our full position on licences, including the applications we decline to sell, is on the licensing page.

Works well with Huginn

More Automation we host

Questions

Huginn hosting: your questions

Can Huginn use an LLM?
Yes. The OpenAI LLM agent, alongside speech and image generation agents, reads OPENAI_API_KEY and OPENAI_BASE_URL, so it works with OpenAI or any compatible API. Point the base URL at an Ollama instance’s /v1 endpoint to keep prompts on hardware you control; keys can also be set per agent.
Which database does Huginn use here?
Huginn supports MySQL and PostgreSQL through DATABASE_ADAPTER. We run it on PostgreSQL in its own container, so agents, events and credentials survive image upgrades and are covered by the nightly off-box backup as an ordinary database.
Can I import scenarios from another Huginn install?
Yes. Export a scenario as JSON from your existing instance and import it here; the agents, their options and the links between them come across. Event history does not travel with a scenario, and any credentials your agents reference need adding again under the same names.
How do I stop strangers signing up?
Huginn gates registration with INVITATION_CODE. We set a random code only you know, create the admin account from SEED_USERNAME and SEED_PASSWORD at first start, and can switch on REQUIRE_CONFIRMED_EMAIL once SMTP is configured.
Are shell command agents allowed?
The ShellCommandAgent and other agents that can touch the host are disabled by default (ENABLE_INSECURE_AGENTS=false), and we keep it that way on a network-facing instance. Use the JavaScript agent, or a webhook to an external service, for logic the built-in agents cannot express.

Run Huginn without running a server

A dedicated Huginn instance, deployed and maintained by us. Month to month, cancel whenever.