head to head · open source

OpenObserve vs codeburn

OpenObserve has 22,699 GitHub stars, 1,174 forks, 598 open issues and last shipped yesterday. codeburn has 11,664 stars, 903 forks, 45 open issues and last shipped yesterday. OpenObserve leads on adoption by 95% (22,699 vs 11,664 stars). OpenObserve is written in TypeScript under AGPL-3.0; codeburn is written in TypeScript under MIT. OpenObserve has attracted 5% as many forks as stars, codeburn 8%. OpenObserve 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.

OpenObserve ★ 23K codeburn ★ 12K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

OpenObserve codeburn
GitHub stars ★ 23K ★ 12K
License AGPL-3.0 MIT
Written in TypeScript TypeScript
Last push 2026-11-02 2026-11-02
Forks ⑂ 1.2K ⑂ 903
Self-hosting Yes Yes
Data ownership Your server Your server

pick OpenObserve if

  • You weight community size — 23K stars and counting
  • You want the AGPL-3.0 license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full OpenObserve profile →

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

full codeburn profile →

About OpenObserve

Open source Datadog alternative for logs, metrics, traces, and frontend monitoring. Modern observability platform: 10x easier, 140x lower storage cost, high performance, petabyte scale. Cloud · Documentation · Slack · Quickstart OpenObserve (O2) is a cloud native observability platform for logs, metrics, traces, analytics, Real User Monitoring (RUM), and AI/LLM observability. It's a cost effective alternative to Datadog, Splunk, and Elasticsearch for teams that need full observability without the complexity or cost — with Parquet columnar storage and an S3 native design that cuts storage costs by up to 140x…

read the full OpenObserve 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 OpenObserve or codeburn more popular?

OpenObserve has 22,699 GitHub stars and codeburn has 11,664. OpenObserve has the larger community by that measure.

Are OpenObserve and codeburn free?

Both are open source. OpenObserve is licensed under AGPL-3.0 and codeburn under MIT. Neither carries a licence fee.

What is the difference between OpenObserve and codeburn?

OpenObserve is written in TypeScript 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, OpenObserve or codeburn?

Choose OpenObserve if you want the larger community (22,699 stars) or its AGPL-3.0 licence terms. Choose codeburn if its feature set, stack or MIT licence fits better. Both are self-hostable.