A · leads
floci
97.9
31,872 stars · MIT
DevOps
floci leads by 34.9 · decisive
A · leads
97.9
31,872 stars · MIT
B
63.0
19,326 stars · license n/a
floci versus goreplay is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. floci is written mainly in Java; goreplay is written mainly in Go. The composite score is 97.9 for floci and 63.0 for goreplay.
floci has 31,872 GitHub stars to goreplay's 19,326, a gap of 12,546 (1.65×). Forks are 3,521 for floci and 102 for goreplay. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 57.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and goreplay was last pushed on 27 January 2026 (294 days ago). Open issues stand at 215 for floci (0.007 per star) and 341 for goreplay (0.018 per star). Issue-health scores are 84 and 84; activity scores are 100 and 36.
floci is listed as MIT, 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. goreplay 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. License scores in this pair are 96 for floci and 30 for goreplay. This is a procurement signal, not legal advice.
Only floci is marked self-hostable here (31,872 stars, deploy score 100). goreplay is not (19,326 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: floci is open source, goreplay is unpriced in this catalog.
floci is ahead on every scored dimension that is not level. Level dimensions: issue health. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is issue health at 0 points (84 vs 84).
floci finishes ahead at 97.9 against goreplay at 63.0, a 34.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 | floci | goreplay |
|---|---|---|
| GitHub stars | 31,872 | 19,326 |
| Forks | 3,521 | 102 |
| Open issues | 215 | 341 |
| Adoption | 100 | 95 |
| Activity | 100 | 36 |
| Community | 100 | 57 |
| Issue health | 84 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.9 | 63.0 |
Light, fluffy, and always free - The AWS Local Emulator alternative
GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes.
floci has more GitHub stars: 31,872 versus 19,326 for goreplay. The gap is 12,546 stars.
floci was pushed more recently: 17 November 2026 versus 27 January 2026 for goreplay. That is 294 days apart.
Only floci is marked self-hostable. goreplay is not.
floci is listed as MIT, 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. goreplay 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
floci scores 97.9 and goreplay scores 63.0. This page calls that a decisive lead for floci.