head to head · open source
beelzebub vs code-on-incus
beelzebub has 2,230 GitHub stars, 220 forks, 5 open issues and last shipped 2 days ago. code-on-incus has 775 stars, 67 forks, 24 open issues and last shipped 2 days ago. beelzebub leads on adoption by 188% (2,230 vs 775 stars). beelzebub is written in Go under GPL-3.0; code-on-incus is written in Go under MIT. beelzebub has attracted 10% as many forks as stars, code-on-incus 9%. code-on-incus 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.
← all 20902 open source comparisons
Side by side
| beelzebub | code-on-incus | |
|---|---|---|
| GitHub stars | ★ 2.2K | ★ 775 |
| License | GPL-3.0 | MIT |
| Written in | Go | Go |
| Last push | 2026-11-03 | 2026-11-03 |
| Forks | ⑂ 220 | ⑂ 67 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick beelzebub if
- You weight community size — 2.2K stars and counting
- You want the GPL-3.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick code-on-incus if
- You want the code-on-incus feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and code-on-incus fits your workflow better
About beelzebub
Beelzebub Open source deception framework. Deploy realistic decoys. Observe attacker behavior. Turn interactions into security evidence. Explore Beelzebub Platform · Documentation · Quick start Beelzebub gives security teams a configurable way to study activity directed at decoy services. Define the environment an attacker encounters, choose how it responds, and capture the interaction for investigation. Run the framework independently or connect it to Beelzebub Platform. Why Beelzebub Deploy decoys that fit your environment. Define services, routes, and response rules in YAML. Use static handlers for…
read the full beelzebub overview →
About code-on-incus
code on incus ( coi ) Give every AI coding agent its own machine with active defense. coi runs your AI coding tool (Claude Code, Codex, opencode, pi, omp) inside its own isolated Linux system a full OS container with root access, systemd, Docker, and the freedom to install anything. The agent works like it would on a real server but it can't touch your host, can't see your credentials, and if it does something dangerous, coi pauses or kills the container on its own. One command drops you into a coding session. Your project is mounted, file permissions just work, and your SSH keys, tokens, and environment…
read the full code-on-incus overview →
More in AI & Machine Learning
Related comparisons
More AI Security & Privacy projects
Compare either of these against the rest of the AI Security & Privacy field.
Frequently asked questions
Is beelzebub or code-on-incus more popular?
beelzebub has 2,230 GitHub stars and code-on-incus has 775. beelzebub has the larger community by that measure.
Are beelzebub and code-on-incus free?
Both are open source. beelzebub is licensed under GPL-3.0 and code-on-incus under MIT. Neither carries a licence fee.
What is the difference between beelzebub and code-on-incus?
beelzebub is written in Go and code-on-incus 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, beelzebub or code-on-incus?
Choose beelzebub if you want the larger community (2,230 stars) or its GPL-3.0 licence terms. Choose code-on-incus if its feature set, stack or MIT licence fits better. Both are self-hostable.