Skip to content
DevUtils Online

DevOps

devops-exercises vs oneuptime

devops-exercises leads by 4.6 · narrow

B

oneuptime

67.3

7,826 stars · license n/a

devops-exercises versus oneuptime is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. devops-exercises is written mainly in Python; oneuptime is written mainly in TypeScript. The composite score is 71.9 for devops-exercises and 67.3 for oneuptime.

devops-exercises has 86,874 GitHub stars to oneuptime's 7,826, a gap of 79,048 (11.10×). Forks are 20,674 for devops-exercises and 495 for oneuptime. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 62.

Push history: devops-exercises was last pushed on 27 December 2025 (325 days ago), and oneuptime was last pushed on 17 November 2026 (0 days ago). Open issues stand at 59 for devops-exercises (0.001 per star) and 1,124 for oneuptime (0.144 per star). Issue-health scores are 96 and 34; activity scores are 36 and 100.

devops-exercises 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. 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 30 for devops-exercises and 30 for oneuptime. This is a procurement signal, not legal advice.

Neither devops-exercises nor oneuptime is marked self-hostable in this catalog (86,874 and 7,826 stars). Deploy scores stay at 35 and 35. Treat both as hosted products until their own docs say you can run them. Pricing labels on file: devops-exercises is unpriced in this catalog, oneuptime is unpriced in this catalog.

The lead is split. devops-exercises is furthest ahead on issue health (96 to 34), while oneuptime is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.

devops-exercises finishes ahead at 71.9 against oneuptime at 67.3, a 4.6 point narrow 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.

devops-exercises versus oneuptime metrics
Signal devops-exercises oneuptime
GitHub stars 86,874 7,826
Forks 20,674 495
Open issues 59 1,124
Adoption 100 79
Activity 36 100
Community 100 62
Issue health 96 34
License 30 30
Self-hosting 35 35
Composite 71.9 67.3

devops-exercises

Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, devops-exercises or oneuptime?

devops-exercises has more GitHub stars: 86,874 versus 7,826 for oneuptime. The gap is 79,048 stars.

Which was updated more recently, devops-exercises or oneuptime?

oneuptime was pushed more recently: 17 November 2026 versus 27 December 2025 for devops-exercises. That is 325 days apart.

Can I self-host both devops-exercises and oneuptime?

Neither devops-exercises nor oneuptime is marked self-hostable in this catalog.

Which license is easier to embed in a commercial product, devops-exercises or oneuptime?

devops-exercises 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. 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.

Who wins the devops-exercises vs oneuptime score?

devops-exercises scores 71.9 and oneuptime scores 67.3. This page calls that a narrow lead for devops-exercises.

Related comparisons