head to head · open source
codeburn vs calico
codeburn has 11,114 GitHub stars, 843 forks, 29 open issues and last shipped today. calico has 7,363 stars, 1,607 forks, 279 open issues and last shipped today. codeburn leads on adoption by 51% (11,114 vs 7,363 stars). codeburn is written in TypeScript under MIT; calico is written in Go under Apache-2.0. codeburn has attracted 8% as many forks as stars, calico 22%. calico 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
| codeburn | calico | |
|---|---|---|
| GitHub stars | ★ 11K | ★ 7.4K |
| License | MIT | Apache-2.0 |
| Written in | TypeScript | Go |
| Last push | 2026-09-20 | 2026-09-20 |
| Forks | ⑂ 843 | ⑂ 1.6K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick codeburn if
- You weight community size — 11K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick calico if
- You want the calico 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 calico fits your workflow better
About codeburn
CodeBurn is a free, open source, local first tool that tracks AI coding token usage and cost across 41 tools and agents, including Claude Code, Cursor, Codex, Gemini, and Grok. It is written in TypeScript, licensed under MIT, and lives in the developer tools and observability ecosystem as a command line utility with optional desktop surfaces. Every surface reads the session files that the supported tools already write to disk, so CodeBurn acts as one source of truth rather than a separate collection layer.
read the full codeburn overview →
About calico
Calico is an open source, Apache 2.0 licensed cloud native networking and network security project for Kubernetes clusters, maintained by Tigera and aimed at platform engineers, cluster operators and network teams who need container networking, network policy enforcement and encryption across on premises, cloud and bare metal environments.
read the full calico 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 codeburn or calico more popular?
codeburn has 11,114 GitHub stars and calico has 7,363. codeburn has the larger community by that measure.
Are codeburn and calico free?
Both are open source. codeburn is licensed under MIT and calico under Apache-2.0. Neither carries a licence fee.
What is the difference between codeburn and calico?
codeburn is written in TypeScript and calico 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, codeburn or calico?
Choose codeburn if you want the larger community (11,114 stars) or its MIT licence terms. Choose calico if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.