Odigos is not staying in the narrow lane of zero-code tracing. ToolVitals sees 15 release events in 30 days, 30 GitHub releases in 90 days, and a 100 shipping score. The latest public signals point to a bigger bet: make Odigos the place teams inspect production behavior, not just the tool that wires OpenTelemetry into services.
The website now leads with a blunt promise: ask production anything. It frames Odigos around seeing what code does in production across services and signals, with no redeploy. The GitHub repository still describes the core as distributed tracing without code changes, using OpenTelemetry and eBPF. That gap is the interesting part. The repo pitch is instrumentation. The website pitch is production investigation.
The May 6 announcement makes that shift concrete. Continuous profiling is now built into Odigos starting with v1.25.0 and above, with CPU profiles collected and visualized directly in Odigos. The post says the built-in path uses an in-memory model, so teams can start without adding a separate profiling database, while OTLP Profiles export is available for historical retention and longer analysis.
The release train backs up the story. The v1.25.0-rc4 notes include profiling in the sources drawer and dynamic control over OpenTelemetry resource detection. The earlier v1.25.0-rc0 notes include tail-sampling rules, an ExtractAttributeProcessor for span attributes, OpenTelemetry eBPF instrumentation support, UI cleanup, and several operational fixes. This is not one shiny launch bolted onto a quiet repo. It is a broad release candidate cycle around signals, sampling, runtime detection, and workload handling.
Odigos is OSI-approved open source under Apache-2.0 according to the ToolVitals openness payload. ToolVitals tracks 3,659 GitHub stars, an 86 health score, and a 90 ToolVitals score. That is strong for a monitoring tool that is still expanding its surface area.
What ToolVitals can and cannot infer
ToolVitals can say Odigos is active. It can see release frequency, stars, public release notes, website availability, SSL, and score movement. For this snapshot, the strongest evidence is shipping cadence: 15 release events in 30 days and 30 releases in 90 days.
ToolVitals cannot tell you whether Odigos will fit your production constraints. It does not measure trace correctness, profiler overhead in your workload, UI quality, enterprise support, user satisfaction, or revenue. The continuous profiling post claims low overhead and no extra storage to get started, but ToolVitals does not independently benchmark that claim. Treat it as product positioning until you test it on your own services.
ToolVitals also does not have 30-day commit or active contributor counts in this payload. That matters. The GitHub page shows a very recent main-branch commit, but the ToolVitals metrics here should not be stretched into a contributor-depth story. The safer read is this: public releases are frequent, and the product direction is easy to verify from first-party sources.
How it compares
Among nearby monitoring tools in this payload, VictoriaMetrics is larger by stars with 17,046 versus Odigos at 3,659. VictoriaMetrics also has a 100 shipping score, but only 9 release events in 30 days versus Odigos at 15. That does not make Odigos more mature. It does mean Odigos is moving faster in release-event terms right now.
OneUptime sits closer in size, with 7,052 stars, a 95 shipping score, and 7 release events in 30 days. Odigos has fewer stars but a higher shipping score and more than twice the 30-day release-event count. In a monitoring category full of mature incumbents, that cadence is the signal.
Recommendation
If your team runs Kubernetes services and wants OpenTelemetry instrumentation without touching application code, evaluate Odigos now. The reason is specific: the project is combining zero-code tracing, eBPF-based instrumentation, tail sampling, and built-in continuous profiling under one active release stream.
Do not adopt it because the score is high. Adopt it only if a short pilot proves the instrumentation and profiling behavior match your production risk budget. But if you are already fighting blind spots across traces and CPU profiles, Odigos deserves a real test, not a bookmark.