Skip to content
DevUtils Online

DevOps

act vs pyroscope

act leads by 15.1 · decisive

A · leads

act

99.1

72,721 stars · MIT

act versus pyroscope is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 99.1 for act and 84.0 for pyroscope.

act has 72,721 GitHub stars to pyroscope's 11,723, a gap of 60,998 (6.20×). Forks are 2,126 for act and 838 for pyroscope. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 88.

Push history: act was last pushed on 16 November 2026 (1 day ago), and pyroscope was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 376 for pyroscope (0.032 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.

act is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. pyroscope is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for act and 52 for pyroscope. This is a procurement signal, not legal advice.

In DevOps, both act (72,721 stars) and pyroscope (11,723 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: act is open source, pyroscope is open source.

act is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).

act finishes ahead at 99.1 against pyroscope at 84.0, a 15.1 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

act versus pyroscope metrics
Signal act pyroscope
GitHub stars 72,721 11,723
Forks 2,126 838
Open issues 318 376
Adoption 100 84
Activity 100 100
Community 100 88
Issue health 96 70
License 96 52
Self-hosting 100 100
Composite 99.1 84.0

Questions this page answers

Which has more GitHub stars, act or pyroscope?

act has more GitHub stars: 72,721 versus 11,723 for pyroscope. The gap is 60,998 stars.

Which was updated more recently, act or pyroscope?

pyroscope was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.

Can I self-host both act and pyroscope?

Yes. This catalog marks both act and pyroscope as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, act or pyroscope?

act is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. pyroscope is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the act vs pyroscope score?

act scores 99.1 and pyroscope scores 84.0. This page calls that a decisive lead for act.

Related comparisons