A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 11.1 · clear
A · leads
99.1
72,721 stars · MIT
B
88.0
6,027 stars · MIT
act versus laravel-backup is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. act is written mainly in Go; laravel-backup is written mainly in PHP. The composite score is 99.1 for act and 88.0 for laravel-backup.
act has 72,721 GitHub stars to laravel-backup's 6,027, a gap of 66,694 (12.07×). Forks are 2,126 for act and 785 for laravel-backup. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 87.
Push history: act was last pushed on 16 November 2026 (1 day ago), and laravel-backup was last pushed on 06 November 2026 (11 days ago). Open issues stand at 318 for act (0.004 per star) and 1 for laravel-backup (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.
Both act and laravel-backup are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and laravel-backup (6,027 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, laravel-backup is open source.
act is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is adoption at 22 points (100 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against laravel-backup at 88.0, a 11.1 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | act | laravel-backup |
|---|---|---|
| GitHub stars | 72,721 | 6,027 |
| Forks | 2,126 | 785 |
| Open issues | 318 | 1 |
| Adoption | 100 | 78 |
| Activity | 100 | 92 |
| Community | 100 | 87 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 88.0 |
Run your GitHub Actions locally 🚀
A package to backup your Laravel app
act has more GitHub stars: 72,721 versus 6,027 for laravel-backup. The gap is 66,694 stars.
act was pushed more recently: 16 November 2026 versus 06 November 2026 for laravel-backup. That is 10 days apart.
Yes. This catalog marks both act and laravel-backup as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. laravel-backup 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
act scores 99.1 and laravel-backup scores 88.0. This page calls that a clear lead for act.