head to head · open source

CloudQuery vs olake

CloudQuery has 6,550 GitHub stars, 567 forks, 166 open issues and last shipped 2 days ago. olake has 1,576 stars, 273 forks, 178 open issues and last shipped 2 days ago. CloudQuery leads on adoption by 316% (6,550 vs 1,576 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%. CloudQuery 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.

CloudQuery ★ 6.5K olake ★ 1.6K category Data & Analytics

← all 20902 open source comparisons

Side by side

CloudQuery olake
GitHub stars ★ 6.5K ★ 1.6K
License MPL-2.0 Apache-2.0
Written in Go Go
Last push 2026-11-03 2026-11-03
Forks ⑂ 567 ⑂ 273
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

full CloudQuery profile →

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

full olake profile →

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 →

About olake

OLake Go OLake Go is a high performance, open source data ingestion engine for replicating databases, S3, and Kafka into Apache Iceberg (or plain Parquet). Built for scalable, real time pipelines, OLake Go provides a simple web UI and CLI used to ingest into vendor lock in free Iceberg tables supporting all the query engines/warehouses. Read the docs and benchmarks at olake.io/docs . Join our active community on Slack . [!NOTE] 🎉 OLake Fusion is now live! — Automate your Apache Iceberg Table Maintenance. Check it out here → github.com/datazip inc/olake fusion 🎉 OLake Go — Super fast Sync to Apache Iceberg…

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,550 GitHub stars and olake has 1,576. 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,550 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.