head to head · open source
CloudQuery vs OpenContracts
CloudQuery has 6,550 GitHub stars, 567 forks, 166 open issues and last shipped 2 days ago. OpenContracts has 1,534 stars, 199 forks, 11 open issues and last shipped 3 days ago. CloudQuery leads on adoption by 327% (6,550 vs 1,534 stars). CloudQuery is written in Go under MPL-2.0; OpenContracts is written in Python under MIT. CloudQuery has attracted 9% as many forks as stars, OpenContracts 13%. CloudQuery was the more recently maintained of the two, and both are self-hostable with no licence fee.
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 | OpenContracts | |
|---|---|---|
| GitHub stars | ★ 6.5K | ★ 1.5K |
| License | MPL-2.0 | MIT |
| Written in | Go | Python |
| Last push | 2026-11-03 | 2026-11-02 |
| Forks | ⑂ 567 | ⑂ 199 |
| 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 OpenContracts if
- You want the OpenContracts feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and OpenContracts 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 OpenContracts
OpenContracts (Demo) Open source document intelligence you can build on. Point OpenContracts at a repository of documents and get a programmable citation graph — human annotation, structured extraction, AI agents, and a built in MCP server, all behind one API. Self hosted, MIT licensed, and built for teams working at scale. Same graph, three surfaces: a GraphQL + REST API for your apps, a Model Context Protocol server for your agents, and a React UI for your team. From documents to a citation graph — in about a minute Create a corpus, drop in your documents, and click Set up . That one click installs the…
read the full OpenContracts 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 OpenContracts more popular?
CloudQuery has 6,550 GitHub stars and OpenContracts has 1,534. CloudQuery has the larger community by that measure.
Are CloudQuery and OpenContracts free?
Both are open source. CloudQuery is licensed under MPL-2.0 and OpenContracts under MIT. Neither carries a licence fee.
What is the difference between CloudQuery and OpenContracts?
CloudQuery is written in Go and OpenContracts in Python. 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 OpenContracts?
Choose CloudQuery if you want the larger community (6,550 stars) or its MPL-2.0 licence terms. Choose OpenContracts if its feature set, stack or MIT licence fits better. Both are self-hostable.