CloudQuery CLI: Query your infra on your infra.
For stronger security, or as a layer in your own cloud asset inventory, CloudQuery CLI is open source, self-hosted, and ships with 80+ cloud and SaaS connectors.Open sourceApache-licensed80+ data connectors
Eliminate cloud data sprawl, without the DIY scripts.
Most teams end up gluing together a different exporter for every provider. CloudQuery CLI syncs, standardizes, and unifies data across your entire stack.
THE OLD WAY
DIY scripts & exporters
Glued together, per provider
WITH CLOUDQUERY CLI
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
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
From install to first sync in three steps
CloudQuery CLI runs wherever you run everything else.
Install the CLI
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.
Five reasons infrastructure teams run CloudQuery CLI
Trying to determine if CloudQuery CLI is right for your team? Here are the ways our enterprise customers use CLI.
01
Self-hosted, open source: run it entirely on infrastructure you control
No data leaves your network unless you decide it should. For teams under strict data-residency or compliance requirements, self-hosting isn't a nice-to-have, it's the only way.
02
Give your AI agents a data source they can query directly
Expose your synced data to agents, so that drift-detection bots and internal tooling can ask questions in the same language your team does.
03
Define every source and destination in version-controlled YAML
Sync configuration lives in your repo, reviewed in pull requests and deployed through the CI/CD pipeline you already trust. No UI clicks to reproduce, no drift between environments.
04
SDK extensibility: build any connector, customized to your internal tooling
Our Go, Python, JS, or Java SDK gets you to a working custom source or destination, without waiting on our roadmap.
05
One tool for every cloud and SaaS source you already run
AWS, GCP, Azure, GitHub, Okta, and 80+ integrations in total, all synced the same way, into the database you already operate.
Why CloudQuery CLI beats the competition
The single source of truth for your entire multicloud estate.
One source of truth for your entire cloud, not a fraction of it
One normalized inventory that covers 200+ AWS tables, hundreds of GCP resource types, and every major cloud and SaaS provider. You get the whole estate, not the slice a single-purpose tool happens to cover.
✓
Query everything in plain SQL
Your cloud data lives in normalized, documented relational tables. You query it with standard SQL, so there is no proprietary language for your team to learn or get locked into.
✓
Your data, your database, your infrastructure
Run it self-hosted on infrastructure you control and keep your data in your own database. No black box, no lock-in.
✓
Built to scale to hundreds of accounts
Incremental sync is built in, so scans across hundreds of cloud accounts finish in minutes instead of slowing down as your estate grows.
✓
Built for incredible speed
CloudQuery's syncing algorithm enables teams to sync data from hundreds of cloud provider accounts in minutes.
Ask anything. Get answers instantly.
Query your cloud with natural language or SQL.
|
I'll find all running EC2 instances that are missing the Backup tag. Here's the query:
SELECT instance_id, instance_type, region, tags
FROM aws_ec2_instances
WHERE tags['Backup'] = ''
AND state = 'running'
ORDER BY launch_time DESC;CLI or Platform: Which fits your team?
Same data at the core, two ways to run it. Many teams start with one and adopt the other later.
SELF-HOSTED
CloudQuery CLI
Config-as-code, full control
MANAGED
CloudQuery Platform
Fully managed, no infra
HOW IT WORKS
Where it runs
Your own infrastructure
Hosted by CloudQuery
Setup & config
Version-controlled YAML
Point-and-click web UI
Data storage
Syncs into your own database
Managed, normalized inventory
Licensing
Open source · Apache-2.0
Commercial subscription
CAPABILITIES
80+ proprietary connectors
Cloud Provider & Engineering Tools Connectors
All
Query in your own warehouse
Native SQL access
Query in-platform
Extensible via SDK & MCP server
SDK + MCP server
Managed, no SDK
AI Assistant for your cloud
Via MCP server
Built-in
Normalized inventory + saved searches
Bring your own
Included
Security, compliance & cost insights
Build your own
Included
Policies, automations, alerts & reports
Build your own
Included
BEST FOR
Teams who want full control of where data lives
Teams who want inventory, policies & querying out of the box
Pricing
The CLI 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:
Rows tailored to your needs
Cloud asset inventory stored in your database
MCP server
50+ cloud, security, and FinOps sources
DIY dashboards and querying
CLI frequently asked questions
Yes. The CLI 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. The CLI 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.
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.