A
devops-exercises
71.9
86,874 stars · license n/a
DevOps
sops leads by 15.9 · decisive
A
71.9
86,874 stars · license n/a
B · leads
87.8
23,737 stars · MPL-2.0
devops-exercises versus sops 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; sops is written mainly in Go. The composite score is 71.9 for devops-exercises and 87.8 for sops.
devops-exercises has 86,874 GitHub stars to sops's 23,737, a gap of 63,137 (3.66×). Forks are 20,674 for devops-exercises and 1,119 for sops. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 71.
Push history: devops-exercises was last pushed on 27 December 2025 (325 days ago), and sops was last pushed on 16 November 2026 (1 day ago). Open issues stand at 59 for devops-exercises (0.001 per star) and 473 for sops (0.020 per star). Issue-health scores are 96 and 84; 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. sops is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 30 for devops-exercises and 78 for sops. This is a procurement signal, not legal advice.
Only sops is marked self-hostable here (23,737 stars, deploy score 100). devops-exercises is not (86,874 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: devops-exercises is unpriced in this catalog, sops is open source.
The lead is split. devops-exercises is furthest ahead on fork community (100 to 71), while sops is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
sops finishes ahead at 87.8 against devops-exercises at 71.9, a 15.9 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 | devops-exercises | sops |
|---|---|---|
| GitHub stars | 86,874 | 23,737 |
| Forks | 20,674 | 1,119 |
| Open issues | 59 | 473 |
| Adoption | 100 | 89 |
| Activity | 36 | 100 |
| Community | 100 | 71 |
| Issue health | 96 | 84 |
| License | 30 | 78 |
| Self-hosting | 35 | 100 |
| Composite | 71.9 | 87.8 |
Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions
Simple and flexible tool for managing secrets
devops-exercises has more GitHub stars: 86,874 versus 23,737 for sops. The gap is 63,137 stars.
sops was pushed more recently: 16 November 2026 versus 27 December 2025 for devops-exercises. That is 324 days apart.
Only sops is marked self-hostable. devops-exercises is not.
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. sops is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
sops scores 87.8 and devops-exercises scores 71.9. This page calls that a decisive lead for sops.