A
oneuptime
68.5
7,826 stars · license n/a
DevOps
Prometheus leads by 29.4 · decisive
A
68.5
7,826 stars · license n/a
B · leads
97.9
67,671 stars · Apache-2.0
oneuptime versus Prometheus is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. oneuptime is written mainly in TypeScript; Prometheus is written mainly in Go. The composite score is 68.5 for oneuptime and 97.9 for Prometheus.
Prometheus has 67,671 GitHub stars to oneuptime's 7,826, a gap of 59,845 (8.65×). Forks are 495 for oneuptime and 11,035 for Prometheus. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 67 versus 100.
Push history: oneuptime was last pushed on 17 November 2026 (0 days ago), and Prometheus was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,124 for oneuptime (0.144 per star) and 1,106 for Prometheus (0.016 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
oneuptime 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. 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. License scores in this pair are 30 for oneuptime and 96 for Prometheus. This is a procurement signal, not legal advice.
Only Prometheus is marked self-hostable here (67,671 stars, deploy score 100). oneuptime is not (7,826 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: oneuptime is unpriced in this catalog, Prometheus is open source.
Prometheus is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is recent activity at 0 points (100 vs 100).
Prometheus finishes ahead at 97.9 against oneuptime at 68.5, a 29.4 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 | oneuptime | Prometheus |
|---|---|---|
| GitHub stars | 7,826 | 67,671 |
| Forks | 495 | 11,035 |
| Open issues | 1,124 | 1,106 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 67 | 100 |
| Issue health | 34 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 68.5 | 97.9 |
Complete open-source monitoring and observability platform.
Prometheus is the CNCF metrics system: pull-based scraping, a time-series database, and PromQL. It is the usual baseline for Kubernetes monitoring.
Prometheus has more GitHub stars: 67,671 versus 7,826 for oneuptime. The gap is 59,845 stars.
Both were last pushed on 17 November 2026.
Only Prometheus is marked self-hostable. oneuptime is not.
oneuptime 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Prometheus scores 97.9 and oneuptime scores 68.5. This page calls that a decisive lead for Prometheus.