compare
Parca vs Uptrace
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Parca | Uptrace |
|---|---|---|
| Language | TypeScript | Go |
| Licence | Apache-2.0 | AGPL-3.0 |
| Stars | 5k | 4.3k |
| Latest | v0.29.1 | v2.1.0-beta.8 |
| Last push | 2026-09-29 | 2026-08-13 |
| Release cadence | about 26 days between releases | about 20 days between releases |
| Active contributors | 6 commit authors on the default branch in the last 90 days | 0 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Datadog. Alternatives to Datadog →
PartialParcaContinuous profiling only, with an eBPF agent that needs no code changes.
PartialUptraceAPM, logs and metrics from OpenTelemetry data, without Datadog's agents and integrations.
Parca
- v0.29.12026-09-28Fix relable configs validation scheme not being set.
- v0.29.02026-09-23ui: Fix the mis-highlighting in flamegraphs
- v0.28.02026-05-07Add support for OpenTelemetry eBPF Profiler profile type
- v0.27.12026-03-20.github: Fix authentication for release container pushing
- v0.27.02026-03-20Update otlp support
Uptrace
- v2.1.0-beta.82026-08-13
- v2.1.0-beta.72026-06-05
- v2.1.0-beta.62026-05-25
- v2.0.32026-05-13
- v2.1.0-beta.52026-04-14
Parca
✓ signed The latest release, v0.29.1, carries a signature GitHub verified.
Loading the security report
Uptrace
✓ signed The latest release, v2.1.0-beta.8, carries a signature GitHub verified.
Loading the security report