Skip to content
DevUtils Online

DevOps

apisix vs goreplay

apisix leads by 31.0 · decisive

A · leads

apisix

95.8

17,333 stars · Apache-2.0

B

goreplay

64.8

19,326 stars · license n/a

apisix versus goreplay is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. apisix is written mainly in Lua; goreplay is written mainly in Go. The composite score is 95.8 for apisix and 64.8 for goreplay.

goreplay has 19,326 GitHub stars to apisix's 17,333, a gap of 1,993 (1.11×). Forks are 3,004 for apisix and 102 for goreplay. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 58.

Push history: apisix was last pushed on 13 November 2026 (4 days ago), and goreplay was last pushed on 27 January 2026 (294 days ago). Open issues stand at 230 for apisix (0.013 per star) and 341 for goreplay (0.018 per star). Issue-health scores are 84 and 84; activity scores are 92 and 36.

apisix 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. 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 apisix and 30 for goreplay. This is a procurement signal, not legal advice.

Only apisix is marked self-hostable here (17,333 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: apisix is open source, goreplay is unpriced in this catalog.

The lead is split. apisix is furthest ahead on license flexibility (96 to 30), while goreplay is furthest ahead on adoption (100 to 99). Choose the dimension a rollout cannot compromise on.

apisix finishes ahead at 95.8 against goreplay at 64.8, a 31.0 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

apisix versus goreplay metrics
Signal apisix goreplay
GitHub stars 17,333 19,326
Forks 3,004 102
Open issues 230 341
Adoption 99 100
Activity 92 36
Community 100 58
Issue health 84 84
License 96 30
Self-hosting 100 35
Composite 95.8 64.8

goreplay

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, apisix or goreplay?

goreplay has more GitHub stars: 19,326 versus 17,333 for apisix. The gap is 1,993 stars.

Which was updated more recently, apisix or goreplay?

apisix was pushed more recently: 13 November 2026 versus 27 January 2026 for goreplay. That is 290 days apart.

Can I self-host both apisix and goreplay?

Only apisix is marked self-hostable. goreplay is not.

Which license is easier to embed in a commercial product, apisix or goreplay?

apisix 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. 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.

Who wins the apisix vs goreplay score?

apisix scores 95.8 and goreplay scores 64.8. This page calls that a decisive lead for apisix.

Related comparisons