CloudQuery

CloudQuery is an open-source context engine for bringing cloud infrastructure data into a shared, queryable format. It suits teams that want SQL access to inventory across multiple sources and control over where data is processed. The trade-off is an annual row-count basis that counts repeat syncs, alongside the need to secure the machine holding cloud credentials.

Overview

CloudQuery syncs data from more than 80 sources and maps it into a normalized relational schema. That gives infrastructure teams a common way to query data from services such as AWS, GCP, Azure, GitHub, and Okta instead of handling each source in a different format. Cloud discovery and network asset discovery make it relevant to inventory work, but the product’s SQL-first approach is best suited to teams prepared to use relational data.

Synced data can go to destinations including Postgres, BigQuery, Snowflake, and S3. CloudQuery Platform takes a more integrated route: it writes data to S3, processes it into a built-in ClickHouse database, and uses that database for inventory, SQL Console, policies, and reports. The open-source engine and destination choices give teams control; Platform bundles more of the analysis environment.

Key features

Configurable syncs and integrations

CloudQuery Platform supports more than 70 source integrations, including Kubernetes, Entra ID, GitLab, Datadog, and PagerDuty. Each sync is defined in version-controlled YAML and can be reviewed through pull requests, a practical fit for teams that want infrastructure data changes to follow code review. If a source is unsupported, teams can build an integration with the Go, Python, JavaScript, or Java SDKs, but that requires development work.

SQL and AI access

Standard SQL provides a familiar way to query synced records. CloudQuery also provides an MCP server in PostgreSQL or Snowflake mode, allowing AI agents and internal systems to query synced data without a Platform subscription. That is useful for teams building their own data workflows; it does not remove the need to provision and secure the chosen database.

Deployment and security

CloudQuery can run on infrastructure the user controls, and data stays within the user’s network unless configured otherwise. This suits organizations that need control over data handling, but also makes host security an operational responsibility. CloudQuery recommends read-only integration credentials and securing the machine running the software, which holds cloud infrastructure credentials.

Pricing

CloudQuery uses freemium pricing. Its Free plan costs nothing, billed Forever, and has a 1M rows limitation. It includes cloud asset inventory in your database, an MCP server, 50+ sources, and DIY dashboards and querying. It is a reasonable starting point for smaller workloads, but the row allowance deserves particular attention: each record counts every time it is synced, so frequently refreshed data consumes the annual basis faster than a one-time count of distinct records suggests.

Enterprise has custom pricing, billed Tailored to your organization. It includes everything in Free and supports 1M+ rows, making it the relevant plan for workloads beyond the free limitation. CloudQuery also offers Free, Silver, Gold, and Platinum support plans; Platinum provides 24×7 support with a one-hour business-critical initial response SLA. A free trial is available.

Platforms

CloudQuery supports API, Linux, macOS, self-hosted, web, and Windows environments, with a hybrid deployment model. The CLI is offered for macOS, Windows, and Linux through Homebrew, precompiled binaries, and other installation methods. Self-hosting is a clear option for teams that want to keep data within their network, subject to their own configuration.

Who it's for

CloudQuery is a strong fit for infrastructure and security teams that need to consolidate cloud and service inventory, already use SQL, and want to choose their own destinations or deployment boundaries. Its version-controlled sync configuration also suits teams that review infrastructure changes through pull requests. It is less compelling for organizations seeking a ready-made workflow with minimal database, pipeline, or credential-management responsibility.

Pros and cons

Pro: A normalized relational schema and standard SQL make data from many sources accessible through a consistent query model.

Pro: Users can choose destinations such as Postgres, BigQuery, Snowflake, and S3, or use Platform’s S3-to-ClickHouse workflow.

Pro: Self-hosting and an MCP server without a Platform subscription give teams options for data control and integration.

Con: The Free plan’s 1M-row limitation counts records on every sync, which can constrain frequently refreshed workloads.

Con: Users must protect the machine holding cloud credentials and manage their chosen data pipeline and destination.

Con: Building an unsupported integration requires work with one of the provided SDKs.

Alternatives

For a broader comparison, see IT Asset Discovery Software. Lansweeper is another freemium option with a free trial and a free continuation for up to 100 assets after a 14-day full trial; its free trial also includes unlimited user seats. LOGINventory may suit readers who want a device-capped free tier: its Forever-Free plan covers up to 20 devices at free, with no time limit. OCS Inventory NG is a free alternative with broad platform support, including Android and iOS. Open-AudIT offers a free plan with unlimited devices and community support, or a Professional plan at $399 a year. runZero may fit teams whose needs fall within its Community Edition limits of 100 assets, one organization, 10 recurring tasks, and 30 days of data retention. GLPI offers a Public Cloud plan at €19 a month per IT agent, from one billed agent. rxInventory has a free Basic plan capped at 20 clients.

Verdict

Choose CloudQuery if your team wants a consistent SQL view across infrastructure sources, needs control over destinations or hosting, and can manage the associated pipeline and credentials. Its combination of flexible syncs and relational querying is the central reason to choose it. Look elsewhere if the repeated-sync row basis or the operational responsibility of self-hosting and securing credentials does not suit your workload.