Skip to content
    Back to AIOps & Observability
    AIOps & ObservabilityStartupAuto Instrumentation

    Odigos

    Automatic distributed tracing for any application without code changes

    Mkt Cap / ValOpen Source
    RevenueEarly Stage
    Zero-code automatic instrumentation for distributed tracing eliminates instrumentation burden across heterogeneous environments.
    Analyst take · Competitive edge

    SWOT Analysis

    Strengths
    • Removes instrumentation overhead; works on existing applications without code changes
    • Open-source; low barrier to adoption for engineering teams evaluating tracing solutions
    • Positioned for Kubernetes and cloud-native architectures where manual instrumentation is painful
    Opportunities
    • Expand into APM capabilities (service dependencies, error tracking, performance analytics)
    • Become de facto standard for auto-instrumentation in OpenTelemetry ecosystem
    • Enterprise support and managed hosting to compete with Datadog/Elastic
    Weaknesses
    • Early-stage project; limited production battle-hardening vs. incumbent tracing platforms
    • Observability ecosystem maturity; storage and visualization still require integrations
    • Unclear commercial sustainability model for open-source foundation
    Threats
    • Datadog, New Relic, Elastic already offer auto-instrumentation; strong incumbents with brand
    • OpenTelemetry standardization may commoditize instrumentation; differentiation pressure

    User Sentiment

    Synthesized from G2, Gartner Peer Insights, and analyst review data.

    What users love
    • No instrumentation code changes required; integrates into existing deployments
    • Open-source approach reduces vendor lock-in concerns
    • Fits cloud-native/Kubernetes-first architectures out of the box
    Common complaints
    • Early-stage; limited documentation and community support relative to established platforms
    • Observability storage and dashboarding require separate tools; not an all-in-one solution
    • Uncertainty about long-term roadmap and sustainability

    Customer Profile

    Who buys this

    Typical segments

    Kubernetes-heavy organizations with multi-language microservicesTeams adopting OpenTelemetry as instrumentation standard

    Typical buyer

    Platform or SRE engineer evaluating lightweight tracing

    Top use cases
    1. 1Distributed tracing in polyglot microservices without SDK overhead
    2. 2Cloud-native application performance visibility
    3. 3Cost-conscious observability for startup/mid-market tech teams

    Future Focus Areas

    1

    Expand to integrated observability—metrics, logs, and traces from single agent

    2

    Build commercial managed offering to compete with vendor-hosted platforms