head to head · open source
Cube vs CloudQuery
Cube has 21,147 GitHub stars, 2,179 forks, 1,185 open issues and last shipped yesterday. CloudQuery has 6,551 stars, 567 forks, 166 open issues and last shipped yesterday. Cube leads on adoption by 223% (21,147 vs 6,551 stars). Cube is written in Rust under a custom or non-standard licence; CloudQuery is written in Go under MPL-2.0. Cube has attracted 10% as many forks as stars, CloudQuery 9%. Cube was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (bigquery), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Cube | CloudQuery | |
|---|---|---|
| GitHub stars | ★ 21K | ★ 6.6K |
| License | Custom / other | MPL-2.0 |
| Written in | Rust | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 2.2K | ⑂ 567 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Cube if
- You weight community size — 21K stars and counting
- You want the Custom / other license terms
- Your stack matches Rust
- You value the larger contributor base for long-term maintenance
pick CloudQuery if
- You want the CloudQuery feature set and don't need the biggest community
- You prefer the MPL-2.0 license terms
- Your stack matches Go
- You evaluated both and CloudQuery fits your workflow better
About Cube
Website • Docs • Examples • Blog • Slack • X Cube Core is the open source semantic layer. Define metrics, dimensions, joins, and access rules once in code, then expose them through SQL, REST, and GraphQL APIs to anything downstream — BI tools, custom applications, or AI agents. Cube Core is headless: it doesn't ship a UI, so you can build the analytics experience that fits your product. Cube Core works with all SQL data sources, including cloud data warehouses like Snowflake, Databricks, and BigQuery; query engines like Presto and Amazon Athena; and application databases like Postgres. It has a built in…
About CloudQuery
CloudOps, without the chaos CloudQuery is a cloud asset inventory built for platform teams. Sync your cloud infrastructure metadata into your data warehouse, powering insights and automation. Unify data and provide context across AWS, Azure, GCP, and 70+ cloud and SaaS sources such as Wiz, Finout, and GitHub. Installation Check out the quickstart guide for install guides for Linux and Windows and for step by step instructions on completing your first sync with CloudQuery. Why CloudQuery? Specialized plugin coverage Support for cloud infrastructure, security, and FinOps sources with normalization, rate limit…
read the full CloudQuery overview →
More in Data & Analytics
Related comparisons
More Data Engineering & Integration projects
Compare either of these against the rest of the Data Engineering & Integration field.
Frequently asked questions
Is Cube or CloudQuery more popular?
Cube has 21,147 GitHub stars and CloudQuery has 6,551. Cube has the larger community by that measure.
Are Cube and CloudQuery free?
Both are open source. Cube has no licence declared in this registry, and CloudQuery is licensed under MPL-2.0. Both are free to self-host.
What is the difference between Cube and CloudQuery?
Cube is written in Rust and CloudQuery in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Cube or CloudQuery?
Choose Cube if you want the larger community (21,147 stars) or its Custom / other licence terms. Choose CloudQuery if its feature set, stack or MPL-2.0 licence fits better. Both are self-hostable.