A
fission
87.8
8,950 stars · Apache-2.0
DevOps
Prometheus leads by 10.1 · clear
A
87.8
8,950 stars · Apache-2.0
B · leads
97.9
67,671 stars · Apache-2.0
fission versus Prometheus 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 87.8 for fission and 97.9 for Prometheus.
Prometheus has 67,671 GitHub stars to fission's 8,950, a gap of 58,721 (7.56×). Forks are 794 for fission and 11,035 for Prometheus. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 72 versus 100.
Push history: fission 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 51 for fission (0.006 per star) and 1,106 for Prometheus (0.016 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both fission and Prometheus 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 fission (8,950 stars) and Prometheus (67,671 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: fission is open source, Prometheus is open source.
Prometheus is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 28 points (72 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Prometheus finishes ahead at 97.9 against fission at 87.8, a 10.1 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 | fission | Prometheus |
|---|---|---|
| GitHub stars | 8,950 | 67,671 |
| Forks | 794 | 11,035 |
| Open issues | 51 | 1,106 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 72 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.8 | 97.9 |
Fast and Simple Serverless Functions for Kubernetes
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 8,950 for fission. The gap is 58,721 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both fission and Prometheus as self-hostable. Confirm each project's deploy docs before you plan a migration.
fission 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. 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 fission scores 87.8. This page calls that a clear lead for Prometheus.