A · leads
Prometheus
97.9
67,671 stars · Apache-2.0
DevOps
Prometheus leads by 8.4 · clear
A · leads
97.9
67,671 stars · Apache-2.0
B
89.5
7,992 stars · Apache-2.0
Prometheus versus terratest 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 97.9 for Prometheus and 89.5 for terratest.
Prometheus has 67,671 GitHub stars to terratest's 7,992, a gap of 59,679 (8.47×). Forks are 11,035 for Prometheus and 1,365 for terratest. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 78.
Push history: Prometheus was last pushed on 17 November 2026 (0 days ago), and terratest was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,106 for Prometheus (0.016 per star) and 3 for terratest (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both Prometheus and terratest are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both Prometheus (67,671 stars) and terratest (7,992 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: Prometheus is open source, terratest is open source.
The lead is split. Prometheus is furthest ahead on fork community (100 to 78), while terratest is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Prometheus finishes ahead at 97.9 against terratest at 89.5, a 8.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 | Prometheus | terratest |
|---|---|---|
| GitHub stars | 67,671 | 7,992 |
| Forks | 11,035 | 1,365 |
| Open issues | 1,106 | 3 |
| Adoption | 100 | 81 |
| Activity | 100 | 100 |
| Community | 100 | 78 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 89.5 |
Prometheus is the CNCF metrics system: pull-based scraping, a time-series database, and PromQL. It is the usual baseline for Kubernetes monitoring.
Terratest is a Go library that makes it easier to write automated tests for your infrastructure code.
Prometheus has more GitHub stars: 67,671 versus 7,992 for terratest. The gap is 59,679 stars.
Prometheus was pushed more recently: 17 November 2026 versus 16 November 2026 for terratest. That is 1 days apart.
Yes. This catalog marks both Prometheus and terratest as self-hostable. Confirm each project's deploy docs before you plan a migration.
Prometheus 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. terratest 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.
Prometheus scores 97.9 and terratest scores 89.5. This page calls that a clear lead for Prometheus.