Skip to content
DevUtils Online

DevOps

goreplay vs lens

lens leads by 11.2 · clear

A

goreplay

65.0

19,326 stars · license n/a

B · leads

lens

76.2

23,248 stars · MIT

goreplay versus lens is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. goreplay is written mainly in Go; lens is written mainly in an unspecified language. The composite score is 65.0 for goreplay and 76.2 for lens.

lens has 23,248 GitHub stars to goreplay's 19,326, a gap of 3,922 (1.20×). Forks are 102 for goreplay and 1,466 for lens. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 64 versus 100.

Push history: goreplay was last pushed on 27 January 2026 (294 days ago), and lens was last pushed on 11 February 2025 (644 days ago). Open issues stand at 341 for goreplay (0.018 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 84 and 52; activity scores are 36 and 16.

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. lens 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. License scores in this pair are 30 for goreplay and 96 for lens. This is a procurement signal, not legal advice.

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

The lead is split. goreplay is furthest ahead on issue health (84 to 52), while lens is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

lens finishes ahead at 76.2 against goreplay at 65.0, a 11.2 point clear 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.

goreplay versus lens metrics
Signal goreplay lens
GitHub stars 19,326 23,248
Forks 102 1,466
Open issues 341 1,165
Adoption 98 100
Activity 36 16
Community 64 100
Issue health 84 52
License 30 96
Self-hosting 35 100
Composite 65.0 76.2

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, goreplay or lens?

lens has more GitHub stars: 23,248 versus 19,326 for goreplay. The gap is 3,922 stars.

Which was updated more recently, goreplay or lens?

goreplay was pushed more recently: 27 January 2026 versus 11 February 2025 for lens. That is 350 days apart.

Can I self-host both goreplay and lens?

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

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

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. lens 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the goreplay vs lens score?

lens scores 76.2 and goreplay scores 65.0. This page calls that a clear lead for lens.

Related comparisons