Skip to content
DevUtils Online

Analytics

amplify-js vs lago

amplify-js leads by 2.2 · narrow

A · leads

amplify-js

94.2

9,556 stars · Apache-2.0

B

lago

92.0

10,891 stars · AGPL-3.0

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

lago has 10,891 GitHub stars to amplify-js's 9,556, a gap of 1,335 (1.14×). Forks are 2,171 for amplify-js and 798 for lago. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 87.

Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and lago was last pushed on 17 November 2026 (0 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 17 for lago (0.002 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.

amplify-js 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. 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. License scores in this pair are 96 for amplify-js and 52 for lago. This is a procurement signal, not legal advice.

In Analytics, both amplify-js (9,556 stars) and lago (10,891 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: amplify-js is open source, lago is open source.

The lead is split. amplify-js is furthest ahead on license flexibility (96 to 52), while lago is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.

amplify-js finishes ahead at 94.2 against lago at 92.0, a 2.2 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.

amplify-js versus lago metrics
Signal amplify-js lago
GitHub stars 9,556 10,891
Forks 2,171 798
Open issues 518 17
Adoption 99 100
Activity 100 100
Community 100 87
Issue health 52 96
License 96 52
Self-hosting 100 100
Composite 94.2 92.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

Questions this page answers

Which has more GitHub stars, amplify-js or lago?

lago has more GitHub stars: 10,891 versus 9,556 for amplify-js. The gap is 1,335 stars.

Which was updated more recently, amplify-js or lago?

Both were last pushed on 16 November 2026.

Can I self-host both amplify-js and lago?

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

Which license is easier to embed in a commercial product, amplify-js or lago?

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

Who wins the amplify-js vs lago score?

amplify-js scores 94.2 and lago scores 92.0. This page calls that a narrow lead for amplify-js.

Related comparisons