head to head · open source

jaeger vs openGemini

jaeger has 23,368 GitHub stars, 3,222 forks, 547 open issues and last shipped 2 days ago. openGemini has 1,178 stars, 176 forks, 117 open issues and last shipped yesterday. jaeger leads on adoption by 1,884% (23,368 vs 1,178 stars). jaeger is written in Go under Apache-2.0; openGemini is written in Go under Apache-2.0. jaeger has attracted 14% as many forks as stars, openGemini 15%. openGemini 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.

jaeger ★ 23K openGemini ★ 1.2K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

jaeger openGemini
GitHub stars ★ 23K ★ 1.2K
License Apache-2.0 Apache-2.0
Written in Go Go
Last push 2026-11-03 2026-11-04
Forks ⑂ 3.2K ⑂ 176
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

full jaeger profile →

pick openGemini if

  • You want the openGemini 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 openGemini fits your workflow better

full openGemini profile →

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 openGemini

README English 简体中文 Official Website Docs Contribution Guide RoadMap Performance About openGemini openGemini is a cloud native distributed time series database, focusing on the storage and analysis of massive telemetry data. If you have used openGemini, please let us know and click submit Usage Information openGemini is an sandbox project of the Cloud Native Computing Foundation (CNCF). Please consider joining the CNCF if you are an organization that wants to take an active role in supporting the growth and evolution of the cloud native ecosystem. Why openGemini Compared with other time series database…

read the full openGemini 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 openGemini more popular?

jaeger has 23,368 GitHub stars and openGemini has 1,178. jaeger has the larger community by that measure.

Are jaeger and openGemini free?

Both are open source. jaeger is licensed under Apache-2.0 and openGemini under Apache-2.0. Neither carries a licence fee.

What is the difference between jaeger and openGemini?

jaeger is written in Go and openGemini 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, jaeger or openGemini?

Choose jaeger if you want the larger community (23,368 stars) or its Apache-2.0 licence terms. Choose openGemini if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.