head to head · open source
huginn vs perses
huginn has 50,269 GitHub stars, 4,339 forks, 698 open issues and last shipped yesterday. perses has 2,514 stars, 266 forks, 277 open issues and last shipped yesterday. huginn leads on adoption by 1,900% (50,269 vs 2,514 stars). huginn is written in Ruby under MIT; perses is written in Go under Apache-2.0. huginn has attracted 9% as many forks as stars, perses 11%. perses was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (monitoring), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| huginn | perses | |
|---|---|---|
| GitHub stars | ★ 50K | ★ 2.5K |
| License | MIT | Apache-2.0 |
| Written in | Ruby | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 4.3K | ⑂ 266 |
| 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
pick perses if
- You want the perses feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and perses fits your workflow better
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 perses
Perses Overview Perses is first and foremost a dashboard tool that you can use to display a variety of observability data. It currently supports Prometheus metrics, Tempo traces, Loki for logs, Pyroscope for profiling, bringing together all four observability pillars in one place. As the project continues to evolve, it will expand support for additional tools to give users even more flexibility and insight. Perses is a Cloud Native Computing Foundation sandbox project. Beyond its core usage, Perses aims to achieve several broader goals: Open specification for dashboards . Perses is also an initiative to define a…
read the full perses 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 perses more popular?
huginn has 50,269 GitHub stars and perses has 2,514. huginn has the larger community by that measure.
Are huginn and perses free?
Both are open source. huginn is licensed under MIT and perses under Apache-2.0. Neither carries a licence fee.
What is the difference between huginn and perses?
huginn is written in Ruby and perses in Go. 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 perses?
Choose huginn if you want the larger community (50,269 stars) or its MIT licence terms. Choose perses if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.