Skip to content
DevUtils Online

Analytics

cube vs lago

lago leads by 8.1 · clear

A

cube

81.6

21,239 stars · license n/a

B · leads

lago

89.7

10,891 stars · AGPL-3.0

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

cube has 21,239 GitHub stars to lago's 10,891, a gap of 10,348 (1.95×). Forks are 2,197 for cube and 798 for lago. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 87.

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

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

Only lago is marked self-hostable here (10,891 stars, deploy score 100). cube is not (21,239 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cube is unpriced in this catalog, lago is open source.

The lead is split. cube is furthest ahead on fork community (100 to 87), while lago is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.

lago finishes ahead at 89.7 against cube at 81.6, a 8.1 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.

cube versus lago metrics
Signal cube lago
GitHub stars 21,239 10,891
Forks 2,197 798
Open issues 1,189 17
Adoption 100 93
Activity 100 100
Community 100 87
Issue health 52 96
License 30 52
Self-hosting 35 100
Composite 81.6 89.7

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, cube or lago?

cube has more GitHub stars: 21,239 versus 10,891 for lago. The gap is 10,348 stars.

Which was updated more recently, cube or lago?

Both were last pushed on 17 November 2026.

Can I self-host both cube and lago?

Only lago is marked self-hostable. cube is not.

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

cube 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. 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 cube vs lago score?

lago scores 89.7 and cube scores 81.6. This page calls that a clear lead for lago.

Related comparisons