A
90DaysOfDevOps
71.9
30,916 stars · license n/a
DevOps
bytebase leads by 7.4 · clear
A
71.9
30,916 stars · license n/a
B · leads
79.3
14,721 stars · license n/a
90DaysOfDevOps versus bytebase 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; bytebase is written mainly in TypeScript. The composite score is 71.9 for 90DaysOfDevOps and 79.3 for bytebase.
90DaysOfDevOps has 30,916 GitHub stars to bytebase's 14,721, a gap of 16,195 (2.10×). Forks are 6,812 for 90DaysOfDevOps and 1,013 for bytebase. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 78.
Push history: 90DaysOfDevOps was last pushed on 24 June 2026 (146 days ago), and bytebase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 12 for 90DaysOfDevOps (0.000 per star) and 173 for bytebase (0.012 per star). Issue-health scores are 96 and 84; 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. bytebase 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 90DaysOfDevOps and 30 for bytebase. This is a procurement signal, not legal advice.
Neither 90DaysOfDevOps nor bytebase is marked self-hostable in this catalog (30,916 and 14,721 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: 90DaysOfDevOps is unpriced in this catalog, bytebase is unpriced in this catalog.
The lead is split. 90DaysOfDevOps is furthest ahead on fork community (100 to 78), while bytebase is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
bytebase finishes ahead at 79.3 against 90DaysOfDevOps at 71.9, a 7.4 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 | 90DaysOfDevOps | bytebase |
|---|---|---|
| GitHub stars | 30,916 | 14,721 |
| Forks | 6,812 | 1,013 |
| Open issues | 12 | 173 |
| Adoption | 100 | 93 |
| Activity | 36 | 100 |
| Community | 100 | 78 |
| Issue health | 96 | 84 |
| License | 30 | 30 |
| Self-hosting | 35 | 35 |
| Composite | 71.9 | 79.3 |
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.
Database governance built for humans and agents — controlling changes and access across every major database.
90DaysOfDevOps has more GitHub stars: 30,916 versus 14,721 for bytebase. The gap is 16,195 stars.
bytebase was pushed more recently: 17 November 2026 versus 24 June 2026 for 90DaysOfDevOps. That is 146 days apart.
Neither 90DaysOfDevOps nor bytebase is marked self-hostable in this catalog.
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. bytebase 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.
bytebase scores 79.3 and 90DaysOfDevOps scores 71.9. This page calls that a clear lead for bytebase.