head to head · open source
iFixAi vs code-on-incus
iFixAi has 43,018 GitHub stars, 1,780 forks, 2 open issues and last shipped yesterday. code-on-incus has 771 stars, 67 forks, 24 open issues and last shipped yesterday. iFixAi leads on adoption by 5,480% (43,018 vs 771 stars). iFixAi is written in Python under Apache-2.0; code-on-incus is written in Go under MIT. iFixAi has attracted 4% 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
| iFixAi | code-on-incus | |
|---|---|---|
| GitHub stars | ★ 43K | ★ 771 |
| License | Apache-2.0 | MIT |
| Written in | Python | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 1.8K | ⑂ 67 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick iFixAi if
- You weight community size — 43K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Python
- 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 iFixAi
iFixAi English · 简体中文 · 日本語 · 한국어 Independent Auditing of AI Agents Catch your agent's mistakes and blind spots before the shit hits the fan. Quick start • Three ways to run • Test your agent • Scoring • Docs • Contributing One ifixai run , end to end: guided setup picks the system, judge, and suite; the run verifies the connection and saves your config; 32 inspections execute across five pillars; and the result lands as an A–F grade with a scored core pillar scorecard. What it is The existing Eval, Red teaming, and Observability Tools are evaluating the agent mainly based on tech capability (token efficiency…
read the full iFixAi 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 iFixAi or code-on-incus more popular?
iFixAi has 43,018 GitHub stars and code-on-incus has 771. iFixAi has the larger community by that measure.
Are iFixAi and code-on-incus free?
Both are open source. iFixAi is licensed under Apache-2.0 and code-on-incus under MIT. Neither carries a licence fee.
What is the difference between iFixAi and code-on-incus?
iFixAi is written in Python 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, iFixAi or code-on-incus?
Choose iFixAi if you want the larger community (43,018 stars) or its Apache-2.0 licence terms. Choose code-on-incus if its feature set, stack or MIT licence fits better. Both are self-hostable.