The access layer built
for AI scale
CloudQuery is an industry-leading context engine for cloud infrastructure.Open sourceSelf-hosted80+ data connectors
macOS (Homebrew):
brew install cloudquery/tap/cloudqueryLinux, CI, or agents:
curl -fsSL https://cloudquery.io/install.sh | shWindows or Docker? See all install options.
From install to first sync in three steps
CloudQuery runs wherever you run everything else.
Install CloudQuery
A single binary on your machine: Linux, macOS, or Windows.
Define sources in YAML
Point at the cloud providers and SaaS apps you want, and the destination database you already operate.
Run the sync
Once, or on a schedule in your pipeline. Your data lands in Postgres, BigQuery, Snowflake, or S3.
Eliminate cloud data sprawl, without the DIY scripts.
Most teams end up gluing together a different exporter for every provider. CloudQuery syncs, standardizes, and unifies data across your entire stack.
THE OLD WAY
DIY scripts & exporters
Glued together, per provider
WITH CLOUDQUERY
One tool, config-as-code
Self-hosted, version-controlled
Source coverage
A separate script or exporter for every cloud and SaaS source
One tool syncs 80+ sources into the database you already run
Querying
Every tool has its own query language or dashboard filters
Query everything in standard SQL, no proprietary language to learn
Data control
Credentials and data spread across tools you don't fully control
Self-hosted, so data never leaves your network unless you choose
Versioning & review
No version history or single source of truth
Every sync defined in version-controlled YAML, reviewed in pull requests
New sources
Need a new source? Start from scratch
Missing a source? Build it with the SDK
Speed at scale
Scans slow down, or time out, as the account count grows
Incremental sync keeps scans across hundreds of accounts fast
Five reasons CloudQuery is built for AI scale
The same infrastructure data your team already syncs becomes the context layer your agents query.
01
MCP-native: give any agent a live query interface
Point Claude, Copilot, or an internal agent at the CloudQuery MCP server in PostgreSQL or Snowflake Mode, backed by your synced data, and it queries your cloud estate directly with no bespoke integration to build or maintain.
02
One normalized schema instead of 80 raw APIs
AWS, GCP, Azure, GitHub, Okta, and 80+ other sources land in the same relational shape. An agent reasoning over your infrastructure works from one consistent schema, not a different JSON shape per provider.
03
Governed access, even when the requester is a model
Agent queries run against your own self-hosted database, under the same access controls and audit trail as any other query, not a third-party API key with broad, unaudited scope.
04
What agents can query is defined in reviewed config
Every source and destination an agent can reach is declared in version-controlled YAML, reviewed in a pull request and deployed from CI. Widening what your agents can see is a code review, not a console click.
05
Give agents context on the systems only you know about
Built an internal tool an agent needs to see? Scaffold a custom source with the SDK so it joins the same schema as everything else, instead of staying invisible to your agents.
Pricing
CloudQuery is open source. You pay for what you sync.
Free
For small teams getting started.
$0
Forever
Includes
1M rows limitation
Cloud asset inventory stored in your database
MCP server
50+ cloud, security, and FinOps sources
DIY dashboards and querying
Enterprise
For growing teams that need scale and predictability.
Custom
Tailored to your organization
Everything in Free, plus:
1M+ rows
Frequently asked questions
With the install script (curl -fsSL https://cloudquery.io/install.sh | sh) on macOS or Linux, a precompiled binary for Linux, macOS, or Windows, the official Docker image (ghcr.io/cloudquery/cloudquery), or Homebrew on macOS. See the download page for the exact command for your platform.
Yes. CloudQuery is open source and free to run. You only pay for your own infrastructure, plus usage-based billing for the data you sync if you use a paid destination.
Yes. CloudQuery is self-hosted by design: it runs on infrastructure you control and syncs to a destination database you choose, so no data leaves your network unless you configure it to.
Postgres, BigQuery, Snowflake, S3, and other supported destinations. You configure the destination in YAML alongside your sources.
Yes. Connect an MCP server to your synced data so AI agents, drift-detection tools, and internal systems can query it directly. CLI users can run the CloudQuery MCP server in PostgreSQL or Snowflake Mode, no Platform subscription required.
Build it yourself with the Go, Python, JS, or Java SDK, or check the 80+ existing connectors first, since new sources are added regularly based on demand.