head to head · open source
cilium vs codeburn
cilium has 25,774 GitHub stars, 4,211 forks, 1,085 open issues and last shipped yesterday. codeburn has 11,682 stars, 909 forks, 45 open issues and last shipped yesterday. cilium leads on adoption by 121% (25,774 vs 11,682 stars). cilium is written in Go under Apache-2.0; codeburn is written in TypeScript under MIT. cilium has attracted 16% 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.
← all 20902 open source comparisons
Side by side
| cilium | codeburn | |
|---|---|---|
| GitHub stars | ★ 26K | ★ 12K |
| License | Apache-2.0 | MIT |
| Written in | Go | TypeScript |
| Last push | 2026-11-04 | 2026-11-04 |
| Forks | ⑂ 4.2K | ⑂ 909 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick cilium if
- You weight community size — 26K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
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
About cilium
.. raw:: html Cilium is a networking, observability, and security solution with an eBPF based dataplane. It provides a simple flat Layer 3 network with the ability to span multiple clusters in either a native routing or overlay mode. It is L7 protocol aware and can enforce network policies on L3 L7 using an identity based security model that is decoupled from network addressing. Cilium implements distributed load balancing for traffic between pods and to external services, and is able to fully replace kube proxy, using efficient hash tables in eBPF, allowing for almost unlimited scale. It also supports advanced…
read the full cilium 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 cilium or codeburn more popular?
cilium has 25,774 GitHub stars and codeburn has 11,682. cilium has the larger community by that measure.
Are cilium and codeburn free?
Both are open source. cilium is licensed under Apache-2.0 and codeburn under MIT. Neither carries a licence fee.
What is the difference between cilium and codeburn?
cilium is written in Go 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, cilium or codeburn?
Choose cilium if you want the larger community (25,774 stars) or its Apache-2.0 licence terms. Choose codeburn if its feature set, stack or MIT licence fits better. Both are self-hostable.