02 Applications we run for you
Huginn
Agents that watch things and act — MIT, community-run, and written in the same Rails your tracker already runs.
- Role
- Monitoring agents
- Licence
- MIT
- Since
- 2013
- Upstream
- Project site ↗
Huginn is a system of agents that monitor and act on your behalf. Named after one of Odin’s two ravens — the one whose name means thought, who flies out each day and reports back what he has seen.
That is a fair description of what it does: agents watch sources, pass events between each other, and act when something matches.
Why it is on this list
Three reasons, in order.
It is MIT and genuinely community-run — no company behind it, so no licence that can be changed and no enterprise tier to be pushed toward. On a site that argues durability comes from governance rather than from licence text, Huginn is the clean case: nobody owns it, so nobody can take it away.
It is Rails, which is the same stack as Redmine and as most of what we build. One deployment story, one set of skills, one Ruby version policy across the estate. For us that is a real operational saving rather than a stylistic preference.
And its model fits the watching problems better than a flow canvas does. Where Node-RED is event-driven glue — something arrives, do this — Huginn is built around agents that go and look: poll a feed, scrape a page, run a query on a schedule, and emit an event when the result changes. Both patterns exist in every organisation; they are not the same tool.
Where we use it
Watching things that have no webhook: a supplier’s status page, a regulatory publication, a certificate expiry, a price, a competitor’s changelog, a directory that should have received a file by 09:00 and did not. Events flow into Redmine as issues or into email, and the agents are configured as JSON that we keep in your repository.
The honest limit
The interface shows every one of its years, and development is steady rather than fast. The agent library is smaller than Node-RED’s node ecosystem, and a few agents assume services that have changed since they were written.
It also needs someone who can operate a Rails application — a real responsibility, though one we are already carrying if you run Redmine.
For most clients the answer is Node-RED for glue and Huginn only if the watching problem is the actual problem. We would rather run one tool than two, and will say so.