Skip to content
DevUtils Online

Analytics

cube vs trino

trino leads by 10.8 · clear

A

cube

80.6

21,239 stars · license n/a

B · leads

trino

91.4

13,520 stars · Apache-2.0

cube versus trino 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; trino is written mainly in Java. The composite score is 80.6 for cube and 91.4 for trino.

cube has 21,239 GitHub stars to trino's 13,520, a gap of 7,719 (1.57×). Forks are 2,197 for cube and 3,880 for trino. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 93 versus 100.

Push history: cube was last pushed on 17 November 2026 (0 days ago), and trino was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,189 for cube (0.056 per star) and 2,758 for trino (0.204 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. trino 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 trino. This is a procurement signal, not legal advice.

Only trino is marked self-hostable here (13,520 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, trino is open source.

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

trino finishes ahead at 91.4 against cube at 80.6, a 10.8 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 trino metrics
Signal cube trino
GitHub stars 21,239 13,520
Forks 2,197 3,880
Open issues 1,189 2,758
Adoption 100 96
Activity 100 100
Community 93 100
Issue health 52 34
License 30 96
Self-hosting 35 100
Composite 80.6 91.4

trino

Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cube or trino?

cube has more GitHub stars: 21,239 versus 13,520 for trino. The gap is 7,719 stars.

Which was updated more recently, cube or trino?

Both were last pushed on 17 November 2026.

Can I self-host both cube and trino?

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

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

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. trino 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 trino score?

trino scores 91.4 and cube scores 80.6. This page calls that a clear lead for trino.

Related comparisons