Comparison

Odigos vs Uptrace

On the evidence we track, Uptrace leads this comparison with a composite score of 63/100. Scores are only directly comparable because these tools share a category; the full breakdown and every source is below.

Machine formatsJSONMarkdownGraphQLor send Accept: application/json
Odigos46
Uptrace63
Score
Vioscale score
Odigos46 / 100low · 23%
Uptrace63 / 100medium · 63%
Pricing
Free tier
Odigos
Uptrace
Model
Uptracefreemium
Price level
Odigosfree
Uptracelow
Transparent
Odigos
Uptrace
Integrations
Count
Odigos
Uptrace14
Reliability
Sla pct
Odigos
Uptrace99.9
Status page
Odigos
Uptrace
Adoption
Dependent repos
Odigos0
Uptrace0
Github stars
Odigos3,676
Uptrace4,270
Package downloads weekly
Odigos
Uptrace3,588
Activity
Commits last 30d
Odigos100
Uptrace
Release
Cadence days
Odigos
Uptrace11
History
Odigos20 items
Uptrace20 items
License
Spdx
UptraceAGPL-3.0
Language
Primary
OdigosGo
UptraceGo
Market
Availability

Capabilities

Feature-by-feature on the axes that matter for distributed tracing tools. “-” means undocumented, not absent.

Core
Trace role
OdigosSaaS platform
UptraceSaaS platform
Standards
OpenTelemetry support
Odigos-
UptraceOTel-native
Multi-protocol (Jaeger + Zipkin + OTLP)
Odigos-
Uptrace
Query
Trace search / filter by attributes
Odigos
Uptrace
Service dependency graph
Odigos
Uptrace
High-cardinality attribute exploration
Odigos-
Uptrace
Sampling
Tail-based / dynamic sampling
Odigos-
Uptrace-
Instrumentation
Auto-instrumentation
OdigosAgent-based
UptraceNone
Correlation
Correlate traces with metrics/logs
Odigos
Uptrace
Deployment
Hosting
Odigos-
UptraceCloud + self-hosted
Architecture
Storage backend
Odigos-
UptraceClickHouse with PostgreSQL for metadata

What each one is

The product in its own terms, so the numbers below have context.

Odigos

Observability platform providing automatic instrumentation for metrics, traces, and logs across services and infrastructure. Enables end-to-end tracing without code edits or redeploys.

Independently observed

Uptrace

Leader

Full-featured observability backend built on OpenTelemetry standards and ClickHouse. Provides distributed tracing, metrics, and log management with dramatically lower costs than competing platforms through pay-per-gigabyte billing rather than enterprise licensing models.

Independently observed

Pricing

List pricing as published by each vendor, with the date we read it. Always verify at the source before you buy.

Odigos

Open source
as of verify ↗

Uptrace

Leader
from $0.03/moHybridFree tier

Free tier includes 50 GB/month. Usage: $0.10/GB (scales to $0.016/GB), $0.025/M datapoints for metrics. Volume discounts automatic. No per-seat fees, unlimited users.

  • FreeFree
    • Full platform access
    • 50+ pre-built dashboards
    • Service graph
    • Alerts and notifications
    • Unlimited users, services, and hosts
  • Pay-as-you-goTraces/logs: $0.10/GB (scales to $0.016/GB). Metrics: $0.025/M datapoints. Hard spending cap available.
    • Distributed tracing
    • Metrics monitoring
    • Log aggregation
    • Custom dashboards
    • PromQL queries
    • +1 more
  • On-PremisesContact sales
    • Full feature parity with cloud
    • No feature limits
    • Custom retention policies
    • Dedicated support engineer
    • SOC 2 certification available
    • +1 more
as of verify ↗

Platform & deployment

Where each product runs and how it can be hosted. A dash means undocumented, not unsupported.

Platforms
Web
Odigos
Uptrace
Deployment
Cloud / SaaS
Odigos
Uptrace
Self-hosted
Odigos
Uptrace
On-premise
Odigos
Uptrace
Hybrid
Odigos
Uptrace

Integrations

What each product connects to. Counts come from the vendor's own integration directory where one exists.

Odigos

Not documented yet.

Uptrace

Leader
14 total
  • OpenTelemetry
  • Prometheus
  • Vector
  • FluentBit
  • CloudWatch
  • Grafana
  • GitHub Actions
  • Slack
  • PagerDuty
  • AlertManager
  • WebHook
  • Google Cloud Auth
  • Okta
  • Keycloak
Independently observed

Comparison generated from independently-sourced facts. Every value links to its source and retrieval date. See the method.