A
gatus
94.1
12,813 stars · Apache-2.0
DevOps
sops leads by 1.7 · narrow
A
94.1
12,813 stars · Apache-2.0
B · leads
95.8
23,737 stars · MPL-2.0
gatus versus sops is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 94.1 for gatus and 95.8 for sops.
sops has 23,737 GitHub stars to gatus's 12,813, a gap of 10,924 (1.85×). Forks are 918 for gatus and 1,119 for sops. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 97 versus 100.
Push history: gatus was last pushed on 16 November 2026 (1 day ago), and sops was last pushed on 16 November 2026 (1 day ago). Open issues stand at 446 for gatus (0.035 per star) and 473 for sops (0.020 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
gatus 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. 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 96 for gatus and 78 for sops. This is a procurement signal, not legal advice.
In DevOps, both gatus (12,813 stars) and sops (23,737 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: gatus is open source, sops is open source.
The lead is split. gatus is furthest ahead on license flexibility (96 to 78), while sops is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
sops finishes ahead at 95.8 against gatus at 94.1, a 1.7 point narrow 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 | gatus | sops |
|---|---|---|
| GitHub stars | 12,813 | 23,737 |
| Forks | 918 | 1,119 |
| Open issues | 446 | 473 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 94.1 | 95.8 |
Automated developer-oriented status page with alerting and incident support
Simple and flexible tool for managing secrets
sops has more GitHub stars: 23,737 versus 12,813 for gatus. The gap is 10,924 stars.
Both were last pushed on 16 November 2026.
Yes. This catalog marks both gatus and sops as self-hostable. Confirm each project's deploy docs before you plan a migration.
gatus 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. 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 95.8 and gatus scores 94.1. This page calls that a narrow lead for sops.