head to head · open source
akto vs code-on-incus
akto has 1,542 GitHub stars, 293 forks, 347 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. akto leads on adoption by 99% (1,542 vs 775 stars). akto is written in Java under MIT; code-on-incus is written in Go under MIT. akto has attracted 19% as many forks as stars, code-on-incus 9%. akto 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
| akto | code-on-incus | |
|---|---|---|
| GitHub stars | ★ 1.5K | ★ 775 |
| License | MIT | MIT |
| Written in | Java | Go |
| Last push | 2026-11-03 | 2026-11-03 |
| Forks | ⑂ 293 | ⑂ 67 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick akto if
- You weight community size — 1.5K stars and counting
- You want the MIT license terms
- Your stack matches Java
- 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 akto
Akto.io API Security Contributors What is Akto? How it works • Getting Started • API Inventory • API testing • Add Test • Join Discord community • Akto is an instant, open source API security platform that takes only 60 secs to get started. Akto is used by security teams to maintain a continuous inventory of APIs, test APIs for vulnerabilities and find runtime issues. Akto offers coverage for all OWASP top 10 and HackerOne Top 10 categories including BOLA, authentication, SSRF, XSS, security configurations, etc. Akto's powerful testing engine runs variety of business logic tests by reading traffic data to…
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 akto or code-on-incus more popular?
akto has 1,542 GitHub stars and code-on-incus has 775. akto has the larger community by that measure.
Are akto and code-on-incus free?
Both are open source. akto is licensed under MIT and code-on-incus under MIT. Neither carries a licence fee.
What is the difference between akto and code-on-incus?
akto is written in Java 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, akto or code-on-incus?
Choose akto if you want the larger community (1,542 stars) or its MIT licence terms. Choose code-on-incus if its feature set, stack or MIT licence fits better. Both are self-hostable.