head to head · open source
CloudQuery vs helix-foundry
CloudQuery has 6,545 GitHub stars, 567 forks, 166 open issues and last shipped yesterday. helix-foundry has 1,683 stars, 257 forks, 8 open issues and last shipped yesterday. CloudQuery leads on adoption by 289% (6,545 vs 1,683 stars). CloudQuery is written in Go under MPL-2.0; helix-foundry is written in TypeScript under Apache-2.0. CloudQuery has attracted 9% as many forks as stars, helix-foundry 15%. helix-foundry was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (data-integration), 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 | helix-foundry | |
|---|---|---|
| GitHub stars | ★ 6.5K | ★ 1.7K |
| License | MPL-2.0 | Apache-2.0 |
| Written in | Go | TypeScript |
| Last push | 2026-10-28 | 2026-10-28 |
| Forks | ⑂ 567 | ⑂ 257 |
| 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 helix-foundry if
- You want the helix-foundry feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches TypeScript
- You evaluated both and helix-foundry fits your workflow better
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 helix-foundry
Helix Foundry Connect your company's data, let an agent draft an ontology over it, and load it into HelixDB as one connected graph you can explore and ask questions of. Connect PostgreSQL, MySQL, Amazon S3, Stripe, PostHog, WorkOS, GitHub, Linear, Granola and Cal.com, and upload documents (Markdown, text, PDF) and table files (CSV, TSV, JSON, JSON Lines, Parquet). An agent drafts the ontology: types, links, the tables and documents each comes from, and rules. You review it, edit it and make a version current. A load writes the version into HelixDB. Explore it as a graph or as records, follow every value back to…
read the full helix-foundry 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 helix-foundry more popular?
CloudQuery has 6,545 GitHub stars and helix-foundry has 1,683. CloudQuery has the larger community by that measure.
Are CloudQuery and helix-foundry free?
Both are open source. CloudQuery is licensed under MPL-2.0 and helix-foundry under Apache-2.0. Neither carries a licence fee.
What is the difference between CloudQuery and helix-foundry?
CloudQuery is written in Go and helix-foundry in TypeScript. 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 helix-foundry?
Choose CloudQuery if you want the larger community (6,545 stars) or its MPL-2.0 licence terms. Choose helix-foundry if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.