Install cloudquery with Homebrew, chocolatey

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• cloudquery

Project history

CloudQuery's official SDK announcement says the project was released at the end of the prior year to give developers, SREs, and security engineers an open-source way to gain deep visibility into cloud infrastructure using SQL. The same post explains that the early project grew quickly enough to motivate a provider SDK and plugin architecture.

By its Series A announcement, CloudQuery described itself as an open-source ELT platform focused on cloud infrastructure, with plugin-based architecture and broad resource coverage across major cloud and infrastructure providers. Later official docs describe the CLI as orchestrating source, transformer, and destination integrations over gRPC, with configuration in YAML and syncs triggered by cloudquery sync.

Adoption history

CloudQuery moved from developer CLI into a broader cloud-governance product while keeping the package-manager-friendly CLI central. Official materials report rapid early GitHub growth, later funding, enterprise customer traction, and a CloudQuery Platform built around cloud asset inventory, security, compliance, FinOps, and automation workflows.

How it is used

Users create YAML source and destination configuration, then run cloudquery sync to extract cloud or SaaS metadata and load it into systems such as PostgreSQL, BigQuery, Snowflake, S3, or other supported destinations. The docs emphasize that the CLI runs in the user's environment, with source integrations fetching external API data and destinations writing it to the configured store.

Why package nerds care

CloudQuery is significant in package-manager culture because it packages a plugin-orchestrating data plane as a CLI: Homebrew users get a single cloudquery command that can download and run integrations, while the actual data pipeline is declared in versioned YAML. It also illustrates the modern split between an open-source CLI, a plugin registry, premium integrations, and a hosted platform.

Timeline

• 2020: CloudQuery was released near the end of the year, according to the official SDK announcement.
• 2021: CloudQuery announced its SDK after growing more than 1.3K GitHub stars in under five months.
• 2022: CloudQuery announced Series A funding and described the project as an open-source ELT platform for cloud infrastructure.
• 2023: CloudQuery documented mandatory login/API-key changes for some CLI use cases.
• 2025: CloudQuery introduced a new platform built around cloud governance and 70+ official sources.
• 2026: Current docs describe the CLI's integration architecture, YAML configuration, and cloudquery sync workflow.

Related projects

• CloudQuery is related to ELT and connector frameworks, cloud asset inventory systems, security posture and compliance tools, and infrastructure query tools. Official docs also point to its own Integration SDK, source integrations such as AWS, GCP, Azure, GitHub, and Okta, and destination integrations such as PostgreSQL, BigQuery, Snowflake, and S3.

Sources

• https://github.com/cloudquery/cloudquery
• https://www.cloudquery.io/blog/introducing-cloudquery-sdk
• https://www.cloudquery.io/blog/cloudquery-raises-15m-series-a
• https://www.cloudquery.io/blog/introducing-the-cloudquery-platform
• https://www.cloudquery.io/docs/cli
• https://www.cloudquery.io/docs/cli/core-concepts/architecture
• https://www.cloudquery.io/docs/cli/core-concepts/configuration