head to head · open source
jaeger vs opensre
jaeger has 23,368 GitHub stars, 3,222 forks, 547 open issues and last shipped 2 days ago. opensre has 12,696 stars, 1,864 forks, 67 open issues and last shipped yesterday. jaeger leads on adoption by 84% (23,368 vs 12,696 stars). jaeger is written in Go under Apache-2.0; opensre is written in Python under Apache-2.0. jaeger has attracted 14% as many forks as stars, opensre 15%. opensre 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 | opensre | |
|---|---|---|
| GitHub stars | ★ 23K | ★ 13K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Go | Python |
| Last push | 2026-11-03 | 2026-11-04 |
| Forks | ⑂ 3.2K | ⑂ 1.9K |
| 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 opensre if
- You want the opensre feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Python
- You evaluated both and opensre 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 opensre
OpenSRE v0.1: Build Your Own AI SRE Agents The open source framework for AI SRE agents, and the training and evaluation environment they need to improve. Connect the 60+ tools you already run, define your own workflows, and answer production questions on your own infrastructure. Quickstart · Docs · FAQ · Security 🚧 Public Alpha: Core workflows are usable for early exploration, though not yet fully stable. The project is in active development, and APIs and integrations may evolve Table of Contents Why OpenSRE? Install Quick Start Deployment How OpenSRE Works Capabilities & integrations Contributing & development…
read the full opensre 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 opensre more popular?
jaeger has 23,368 GitHub stars and opensre has 12,696. jaeger has the larger community by that measure.
Are jaeger and opensre free?
Both are open source. jaeger is licensed under Apache-2.0 and opensre under Apache-2.0. Neither carries a licence fee.
What is the difference between jaeger and opensre?
jaeger is written in Go and opensre in Python. 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 opensre?
Choose jaeger if you want the larger community (23,368 stars) or its Apache-2.0 licence terms. Choose opensre if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.