pyroscopevsvictoriametrics
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| pyroscope | victoriametrics | |
|---|---|---|
| Score | 73/100 | 78/100 |
| Rank in category | #3 of 9 in Application Performance Monitoring | #3 of 5 in Time Series |
| GitHub stars | 11 722 | 18 115 |
| Stars, last 30 days | +25 | +268 |
| Stable releases, 12 months | 22 | 26 |
| Latest release | v2.3.5 · 3 Nov 2026 | v1.156.0 · 9 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Go | Go |
Which one should you pick?
victoriametrics scores 78/100 against 73/100 for pyroscope, so it is the safer default.
victoriametrics ships more often: 26 stable releases in the past year, against 22 for pyroscope.
If you want the quickest setup, pyroscope is easier to run; victoriametrics needs more configuration.
victoriametrics is growing faster right now (+268 stars in 30 days).
Key differences
- License: pyroscope is AGPL-3.0, victoriametrics is Apache-2.0.
- Platforms only pyroscope lists: macOS.
- Platforms only victoriametrics lists: Ansible, Helm Charts.
- Features only pyroscope lists: Continuous profiling, Durable long-term storage, Flame graph visualization, High Availability and 10 more.
- Features only victoriametrics lists: Alerting via vmalert, Built-in web UI (vmui), Cardinality limiter, Deduplication of scraped samples and 10 more.
pyroscope details →victoriametrics details →
Swap a project
Keep pyroscope, compare it with
Keep victoriametrics, compare it with