Skip to content
DevUtils Online

DevOps

act vs tsuru

act leads by 10.4 · clear

A · leads

act

99.1

72,721 stars · MIT

B

tsuru

88.7

5,330 stars · BSD-3-Clause

act versus tsuru 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 88.7 for tsuru.

act has 72,721 GitHub stars to tsuru's 5,330, a gap of 67,391 (13.64×). Forks are 2,126 for act and 554 for tsuru. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 82.

Push history: act was last pushed on 16 November 2026 (1 day ago), and tsuru was last pushed on 14 November 2026 (3 days ago). Open issues stand at 318 for act (0.004 per star) and 24 for tsuru (0.005 per star). Issue-health scores are 96 and 96; 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. tsuru is listed as BSD-3-Clause, 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. License scores in this pair are 96 for act and 96 for tsuru. This is a procurement signal, not legal advice.

In DevOps, both act (72,721 stars) and tsuru (5,330 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, tsuru is open source.

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

act finishes ahead at 99.1 against tsuru at 88.7, a 10.4 point clear 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 tsuru metrics
Signal act tsuru
GitHub stars 72,721 5,330
Forks 2,126 554
Open issues 318 24
Adoption 100 77
Activity 100 100
Community 100 82
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 99.1 88.7

Questions this page answers

Which has more GitHub stars, act or tsuru?

act has more GitHub stars: 72,721 versus 5,330 for tsuru. The gap is 67,391 stars.

Which was updated more recently, act or tsuru?

act was pushed more recently: 16 November 2026 versus 14 November 2026 for tsuru. That is 2 days apart.

Can I self-host both act and tsuru?

Yes. This catalog marks both act and tsuru 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 tsuru?

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. tsuru is listed as BSD-3-Clause, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the act vs tsuru score?

act scores 99.1 and tsuru scores 88.7. This page calls that a clear lead for act.

Related comparisons