Skip to content
DevUtils Online

Analytics

lago vs openreplay

lago leads by 2.9 · narrow

A · leads

lago

92.9

10,891 stars · AGPL-3.0

lago versus openreplay is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lago is written mainly in Go; openreplay is written mainly in TypeScript. The composite score is 92.9 for lago and 90.0 for openreplay.

openreplay has 13,157 GitHub stars to lago's 10,891, a gap of 2,266 (1.21×). Forks are 798 for lago and 891 for openreplay. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 98 versus 100.

Push history: lago was last pushed on 17 November 2026 (0 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 17 for lago (0.002 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

lago is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. openreplay 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 52 for lago and 30 for openreplay. This is a procurement signal, not legal advice.

In Analytics, both lago (10,891 stars) and openreplay (13,157 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: lago is open source, openreplay is unpriced in this catalog.

The lead is split. lago is furthest ahead on license flexibility (52 to 30), while openreplay is furthest ahead on adoption (100 to 98). Choose the dimension a rollout cannot compromise on.

lago finishes ahead at 92.9 against openreplay at 90.0, a 2.9 point narrow 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.

lago versus openreplay metrics
Signal lago openreplay
GitHub stars 10,891 13,157
Forks 798 891
Open issues 17 193
Adoption 98 100
Activity 100 100
Community 98 100
Issue health 96 84
License 52 30
Self-hosting 100 100
Composite 92.9 90.0

lago

Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics

Project site · GitHub · Full profile

openreplay

Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, lago or openreplay?

openreplay has more GitHub stars: 13,157 versus 10,891 for lago. The gap is 2,266 stars.

Which was updated more recently, lago or openreplay?

Both were last pushed on 17 November 2026.

Can I self-host both lago and openreplay?

Yes. This catalog marks both lago and openreplay as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, lago or openreplay?

lago is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. openreplay 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 lago vs openreplay score?

lago scores 92.9 and openreplay scores 90.0. This page calls that a narrow lead for lago.

Related comparisons