compare
Coroot vs Parca
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Coroot | Parca |
|---|---|---|
| Language | Go | TypeScript |
| Licence | Apache-2.0 | Apache-2.0 |
| Stars | 8k | 5k |
| Latest | v1.27.1 | v0.29.1 |
| Last push | 2026-10-06 | 2026-09-29 |
| Release cadence | about 5 days between releases | about 26 days between releases |
| Active contributors | 6 commit authors on the default branch in the last 90 days | 6 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Datadog. Alternatives to Datadog →
PartialCorooteBPF-based service maps, metrics, logs, traces and profiles, with no code changes needed.
PartialParcaContinuous profiling only, with an eBPF agent that needs no code changes.
Coroot
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
Coroot
✓ signed The latest release, v1.27.1, carries a signature GitHub verified.
Loading the security report
Parca
✓ signed The latest release, v0.29.1, carries a signature GitHub verified.
Loading the security report