A
90DaysOfDevOps
71.9
30,916 stars · license n/a
DevOps
opensre leads by 22.3 · decisive
A
71.9
30,916 stars · license n/a
B · leads
94.2
12,838 stars · Apache-2.0
90DaysOfDevOps versus opensre is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. 90DaysOfDevOps is written mainly in Shell; opensre is written mainly in Python. The composite score is 71.9 for 90DaysOfDevOps and 94.2 for opensre.
90DaysOfDevOps has 30,916 GitHub stars to opensre's 12,838, a gap of 18,078 (2.41×). Forks are 6,812 for 90DaysOfDevOps and 1,884 for opensre. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 85.
Push history: 90DaysOfDevOps was last pushed on 24 June 2026 (146 days ago), and opensre was last pushed on 17 November 2026 (0 days ago). Open issues stand at 12 for 90DaysOfDevOps (0.000 per star) and 11 for opensre (0.001 per star). Issue-health scores are 96 and 96; activity scores are 36 and 100.
90DaysOfDevOps 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. opensre is listed as Apache-2.0, 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 30 for 90DaysOfDevOps and 96 for opensre. This is a procurement signal, not legal advice.
Only opensre is marked self-hostable here (12,838 stars, deploy score 100). 90DaysOfDevOps is not (30,916 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: 90DaysOfDevOps is unpriced in this catalog, opensre is open source.
The lead is split. 90DaysOfDevOps is furthest ahead on fork community (100 to 85), while opensre is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
opensre finishes ahead at 94.2 against 90DaysOfDevOps at 71.9, a 22.3 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 | 90DaysOfDevOps | opensre |
|---|---|---|
| GitHub stars | 30,916 | 12,838 |
| Forks | 6,812 | 1,884 |
| Open issues | 12 | 11 |
| Adoption | 100 | 92 |
| Activity | 36 | 100 |
| Community | 100 | 85 |
| Issue health | 96 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 71.9 | 94.2 |
This repository started out as a learning in public project for myself and has now become a structured learning map for many in the community. We have 3 years under our belt covering all things DevOps, including Principles, Processes, Tooling and Use Cases surrounding this vast topic.
The open-source agent for CI/CD reliability.
90DaysOfDevOps has more GitHub stars: 30,916 versus 12,838 for opensre. The gap is 18,078 stars.
opensre was pushed more recently: 17 November 2026 versus 24 June 2026 for 90DaysOfDevOps. That is 146 days apart.
Only opensre is marked self-hostable. 90DaysOfDevOps is not.
90DaysOfDevOps 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. opensre is listed as Apache-2.0, 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.
opensre scores 94.2 and 90DaysOfDevOps scores 71.9. This page calls that a decisive lead for opensre.