head to head · open source
CloudQuery vs olake
CloudQuery has 6,521 GitHub stars, 558 forks, 166 open issues and last shipped 3 days ago. olake has 1,453 stars, 252 forks, 178 open issues and last shipped 2 days ago. CloudQuery leads on adoption by 349% (6,521 vs 1,453 stars). CloudQuery is written in Go under MPL-2.0; olake is written in Go under Apache-2.0. CloudQuery has attracted 9% as many forks as stars, olake 17%. olake was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (elt), 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
| CloudQuery | olake | |
|---|---|---|
| GitHub stars | ★ 6.5K | ★ 1.5K |
| License | MPL-2.0 | Apache-2.0 |
| Written in | Go | Go |
| Last push | 2026-09-18 | 2026-09-19 |
| Forks | ⑂ 558 | ⑂ 252 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick CloudQuery if
- You weight community size — 6.5K stars and counting
- You want the MPL-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick olake if
- You want the olake feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and olake fits your workflow better
About CloudQuery
CloudQuery is an open source, Go based cloud asset inventory and ELT tool, licensed under MPL 2.0, that syncs metadata from AWS, Azure, GCP, and more than 70 cloud and SaaS sources into a data warehouse so platform, security, and FinOps teams can query it with SQL.
read the full CloudQuery overview →
About olake
OLake Go is an open source data ingestion engine written in Go and licensed under Apache 2.0. It replicates transactional databases, Apache Kafka, and S3 into Apache Iceberg or plain Parquet, and it provides a web UI and a command line interface for building scalable, real time pipelines. The project sits in the Apache Iceberg and lakehouse ecosystem, where its stated goal is to move data into vendor neutral table formats that can be read by query engines and warehouses.
read the full olake 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 CloudQuery or olake more popular?
CloudQuery has 6,521 GitHub stars and olake has 1,453. CloudQuery has the larger community by that measure.
Are CloudQuery and olake free?
Both are open source. CloudQuery is licensed under MPL-2.0 and olake under Apache-2.0. Neither carries a licence fee.
What is the difference between CloudQuery and olake?
CloudQuery is written in Go and olake 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, CloudQuery or olake?
Choose CloudQuery if you want the larger community (6,521 stars) or its MPL-2.0 licence terms. Choose olake if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.