head to head · open source

huginn vs codeburn

huginn has 50,269 GitHub stars, 4,339 forks, 698 open issues and last shipped yesterday. codeburn has 11,664 stars, 903 forks, 45 open issues and last shipped yesterday. huginn leads on adoption by 331% (50,269 vs 11,664 stars). huginn is written in Ruby under MIT; codeburn is written in TypeScript under MIT. huginn has attracted 9% as many forks as stars, codeburn 8%. codeburn was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

huginn ★ 50K codeburn ★ 12K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

huginn codeburn
GitHub stars ★ 50K ★ 12K
License MIT MIT
Written in Ruby TypeScript
Last push 2026-11-02 2026-11-02
Forks ⑂ 4.3K ⑂ 903
Self-hosting Yes Yes
Data ownership Your server Your server

pick huginn if

  • You weight community size — 50K stars and counting
  • You want the MIT license terms
  • Your stack matches Ruby
  • You value the larger contributor base for long-term maintenance

full huginn profile →

pick codeburn if

  • You want the codeburn feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches TypeScript
  • You evaluated both and codeburn fits your workflow better

full codeburn profile →

About huginn

What is Huginn? Huginn is a system for building agents that perform automated tasks for you online. They can read the web, watch for events, and take actions on your behalf. Huginn's Agents create and consume events, propagating them along a directed graph. Think of it as a hackable version of IFTTT or Zapier on your own server. You always know who has your data. You do. Here are some of the things that you can do with Huginn: Track the weather and get an email when it's going to rain (or snow) tomorrow ("Don't forget your umbrella!") List terms that you care about and receive email when their occurrence on…

read the full huginn overview →

About codeburn

See where your AI spend goes. If CodeBurn shows you something your bill never did, star the repo so other developers find it, and consider sponsoring to keep 41 integrations honest. npx codeburn To keep it: npm install g codeburn or brew install codeburn . Needs Node.js 22.13+. Desktop app 0.9.25. The macOS builds are signed with a Developer ID and notarized by Apple. The problem Your bill gives you a month total. It does not break that down by project, by model or by task, and it does not show which part of it was wasted. Claude Code, Codex, Cursor and the rest each write a session file every time you use them…

read the full codeburn overview →

More in Infrastructure & Operations

Related comparisons

More Monitoring & Observability projects

Compare either of these against the rest of the Monitoring & Observability field.

Frequently asked questions

Is huginn or codeburn more popular?

huginn has 50,269 GitHub stars and codeburn has 11,664. huginn has the larger community by that measure.

Are huginn and codeburn free?

Both are open source. huginn is licensed under MIT and codeburn under MIT. Neither carries a licence fee.

What is the difference between huginn and codeburn?

huginn is written in Ruby and codeburn in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, huginn or codeburn?

Choose huginn if you want the larger community (50,269 stars) or its MIT licence terms. Choose codeburn if its feature set, stack or MIT licence fits better. Both are self-hostable.