head to head · open source
jaeger vs codeburn
jaeger has 23,375 GitHub stars, 3,223 forks, 547 open issues and last shipped yesterday. codeburn has 11,682 stars, 909 forks, 45 open issues and last shipped yesterday. jaeger leads on adoption by 100% (23,375 vs 11,682 stars). jaeger is written in Go under Apache-2.0; codeburn is written in TypeScript under MIT. jaeger has attracted 14% 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. The two share 1 topic tag (observability), so they are genuine substitutes rather than adjacent tools.
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
| jaeger | codeburn | |
|---|---|---|
| GitHub stars | ★ 23K | ★ 12K |
| License | Apache-2.0 | MIT |
| Written in | Go | TypeScript |
| Last push | 2026-11-04 | 2026-11-04 |
| Forks | ⑂ 3.2K | ⑂ 909 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick jaeger if
- You weight community size — 23K 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 jaeger
[![Slack chat][slack img]]( get in touch) [![Unit Tests][ci img]][ci] [![Coverage Status][cov img]][cov] [![Project+Community stats][community badge]][community stats] [![FOSSA Status][fossa img]][fossa] [![OpenSSF Scorecard][openssf img]][openssf] [![OpenSSF Best Practices][openssf bp img]][openssf bp] [![CLOMonitor][clomonitor img]][clomonitor] [![Artifact Hub][artifacthub img]][artifacthub] Jaeger a Distributed Tracing System 💥💥💥 Jaeger v2 is out! Read the blog post and try it out. Quick Start Get Jaeger running in seconds with Docker: For production deployments and more options, see the Getting Started…
read the full jaeger 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 jaeger or codeburn more popular?
jaeger has 23,375 GitHub stars and codeburn has 11,682. jaeger has the larger community by that measure.
Are jaeger and codeburn free?
Both are open source. jaeger is licensed under Apache-2.0 and codeburn under MIT. Neither carries a licence fee.
What is the difference between jaeger and codeburn?
jaeger 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, jaeger or codeburn?
Choose jaeger if you want the larger community (23,375 stars) or its Apache-2.0 licence terms. Choose codeburn if its feature set, stack or MIT licence fits better. Both are self-hostable.