Skip to content
DevUtils Online

Analytics

cube vs OpenSearch

OpenSearch leads by 10.5 · clear

A

cube

81.0

21,239 stars · license n/a

B · leads

OpenSearch

91.5

14,016 stars · Apache-2.0

cube versus OpenSearch 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; OpenSearch is written mainly in Java. The composite score is 81.0 for cube and 91.5 for OpenSearch.

cube has 21,239 GitHub stars to OpenSearch's 14,016, a gap of 7,223 (1.52×). Forks are 2,197 for cube and 3,088 for OpenSearch. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 96 versus 100.

Push history: cube was last pushed on 17 November 2026 (0 days ago), and OpenSearch was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,189 for cube (0.056 per star) and 3,385 for OpenSearch (0.242 per star). Issue-health scores are 52 and 34; 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. OpenSearch 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. License scores in this pair are 30 for cube and 96 for OpenSearch. This is a procurement signal, not legal advice.

Only OpenSearch is marked self-hostable here (14,016 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, OpenSearch is open source.

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

OpenSearch finishes ahead at 91.5 against cube at 81.0, a 10.5 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 OpenSearch metrics
Signal cube OpenSearch
GitHub stars 21,239 14,016
Forks 2,197 3,088
Open issues 1,189 3,385
Adoption 100 96
Activity 100 100
Community 96 100
Issue health 52 34
License 30 96
Self-hosting 35 100
Composite 81.0 91.5

Questions this page answers

Which has more GitHub stars, cube or OpenSearch?

cube has more GitHub stars: 21,239 versus 14,016 for OpenSearch. The gap is 7,223 stars.

Which was updated more recently, cube or OpenSearch?

Both were last pushed on 17 November 2026.

Can I self-host both cube and OpenSearch?

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

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

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

Who wins the cube vs OpenSearch score?

OpenSearch scores 91.5 and cube scores 81.0. This page calls that a clear lead for OpenSearch.

Related comparisons