A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 28.7 · decisive
A · leads
99.1
72,721 stars · MIT
B
70.4
7,826 stars · license n/a
act versus oneuptime 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; oneuptime is written mainly in TypeScript. The composite score is 99.1 for act and 70.4 for oneuptime.
act has 72,721 GitHub stars to oneuptime's 7,826, a gap of 64,895 (9.29×). Forks are 2,126 for act and 495 for oneuptime. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 81.
Push history: act was last pushed on 16 November 2026 (1 day ago), and oneuptime was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 1,124 for oneuptime (0.144 per star). Issue-health scores are 96 and 34; 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. oneuptime is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for act and 30 for oneuptime. This is a procurement signal, not legal advice.
Only act is marked self-hostable here (72,721 stars, deploy score 100). oneuptime is not (7,826 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: act is open source, oneuptime is unpriced in this catalog.
act is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).
act finishes ahead at 99.1 against oneuptime at 70.4, a 28.7 point decisive 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 | oneuptime |
|---|---|---|
| GitHub stars | 72,721 | 7,826 |
| Forks | 2,126 | 495 |
| Open issues | 318 | 1,124 |
| Adoption | 100 | 80 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 96 | 34 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 99.1 | 70.4 |
Run your GitHub Actions locally 🚀
Complete open-source monitoring and observability platform.
act has more GitHub stars: 72,721 versus 7,826 for oneuptime. The gap is 64,895 stars.
oneuptime was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.
Only act is marked self-hostable. oneuptime is not.
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. oneuptime is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
act scores 99.1 and oneuptime scores 70.4. This page calls that a decisive lead for act.