300+ Tools CoveredSource Data Updated Weeklydates

Tool intelligence profile

CloudQuery

The unified control plane for cloud operations. Inspect, govern, and automate your entire cloud estate with deep context from infrastructure, security, and FinOps tools.

Visit Site →
Type
ELT Platform
Deployment
Cloud or self-hosted
Last updatedSeptember 21, 2026

Editor's Take

CloudQuery does for infrastructure data what Fivetran does for SaaS data — it extracts configuration and metadata from your cloud providers and loads it into a queryable format. If you have ever wanted to SQL your way through your AWS resources, CloudQuery makes it surprisingly easy.

— Egor Burlakov, Editor

Evaluate CloudQuery

Comparisons

CloudQuery: product and architecture

CloudQuery is an open-source ELT framework that extracts data from cloud APIs, databases, and SaaS applications into data warehouses and data lakes for analysis and governance. In this CloudQuery review, we examine how the platform provides multi-cloud visibility for governance and platform teams, and how it compares to alternatives like Steampipe, Fivetran, and Airbyte.

Overview

CloudQuery (cloudquery.io) is an open-source ELT framework originally focused on cloud infrastructure data but now expanded to cover any API-based data source. The platform extracts data from 70+ cloud and SaaS sources (AWS, GCP, Azure, GitHub, Kubernetes, Cloudflare, Okta, and many more) and loads it into destinations like PostgreSQL, BigQuery, Snowflake, S3, and ClickHouse.

The primary use case is cloud governance and visibility: platform teams extract their cloud resource inventory into a data warehouse, then use SQL to build compliance dashboards, cost analysis reports, and security audits. CloudQuery positions itself as "multi-cloud visibility and automation for governance and platform teams."

CloudQuery is built in Go with a plugin-based architecture — source plugins extract data, destination plugins load it, and the framework handles scheduling, incremental syncs, and schema management. The project has 5,800+ GitHub stars and an active community.

Key Features and Architecture

Plugin-Based Architecture

CloudQuery uses a source/destination plugin model: source plugins extract data from APIs (AWS, GCP, Azure, GitHub, Kubernetes, etc.), and destination plugins load data into warehouses (PostgreSQL, BigQuery, Snowflake, ClickHouse, S3). Plugins are independent binaries, so adding a new source doesn't require modifying the core framework.

70+ Source Plugins

Sources cover cloud providers (AWS with 200+ tables, GCP, Azure, Oracle Cloud), developer tools (GitHub, GitLab, Terraform, Cloudflare), identity (Okta, Auth0), monitoring (Datadog, PagerDuty), and many more. Each source plugin maps API resources to relational tables with consistent schemas.

Incremental Syncs

CloudQuery supports incremental extraction — only fetching resources that changed since the last sync. This reduces API calls, sync time, and costs for large cloud environments with thousands of resources.

SQL-Based Policy and Compliance

Once cloud data is in a warehouse, teams write SQL queries to check compliance policies: "find all S3 buckets without encryption," "list IAM users without MFA," or "show EC2 instances running for more than 90 days." CloudQuery provides pre-built policy packs for CIS benchmarks, SOC 2, and other frameworks.

Transformation with dbt

CloudQuery integrates with dbt for transforming raw cloud data into analytics-ready models. Pre-built dbt packages provide common transformations like cost allocation, security posture scoring, and resource tagging compliance.

Multi-Cloud Normalization

For organizations running across AWS, GCP, and Azure, CloudQuery normalizes resource data into consistent schemas, enabling cross-cloud queries like "show me all compute instances across all clouds sorted by cost."

Ideal Use Cases

Cloud Security and Compliance

Security teams extract cloud resource inventories into a warehouse and run SQL-based compliance checks against CIS benchmarks, SOC 2 controls, or custom policies. This provides continuous compliance monitoring without relying on cloud-provider-specific tools.

Cloud Cost Optimization

FinOps teams extract billing and resource data from multiple cloud providers, combine it in a warehouse, and build cost allocation dashboards, idle resource reports, and rightsizing recommendations using SQL and dbt.

Platform Engineering Visibility

Platform teams managing Kubernetes clusters, Terraform state, and cloud resources across multiple accounts use CloudQuery to build a unified inventory. This enables questions like "which teams are running the most expensive resources?" or "how many clusters are running outdated Kubernetes versions?"

Multi-Cloud Governance

Organizations operating across AWS, GCP, and Azure use CloudQuery's normalized schemas to apply consistent governance policies across all clouds from a single SQL interface.

Strengths & Trade-offs

Pros

  • 70+ cloud and SaaS sources — covers AWS (200+ tables), GCP, Azure, GitHub, Kubernetes, Cloudflare, Okta, and many more
  • Open-source core — free to use with full source code access; no vendor lock-in on the extraction framework
  • SQL-based governance — extract cloud data into warehouses and use SQL for compliance, cost, and security analysis
  • dbt integration — pre-built dbt packages for common cloud governance transformations
  • Lightweight deployment — single binary, minimal infrastructure; simpler than running Airbyte or Fivetran self-hosted
  • Multi-cloud normalization — consistent schemas across AWS, GCP, and Azure for cross-cloud queries

Cons

  • Niche focus — primarily designed for cloud infrastructure and API data; not a general-purpose ELT tool for application databases
  • Plugin quality varies — plugin maturity and completeness vary across sources; AWS is comprehensive, small sources may have gaps
  • No built-in transformation — relies on dbt or SQL for transformations; no visual transformation builder
  • Limited community — 5,800+ GitHub stars is healthy but trails Airbyte (15,000+) or dbt (9,000+)
  • MPL 2.0 license — has stricter terms than Apache 2.0; some organizations have concerns about copyleft provisions

Getting Started

Getting started with CloudQuery is straightforward. Visit the official website to create a free account or download the application. The onboarding process typically takes under 5 minutes, and most users can be productive within their first session. For teams evaluating CloudQuery against alternatives, we recommend a 2-week trial period to assess whether the feature set and user experience align with your specific workflow requirements. Documentation and community resources are available to help with initial setup and configuration.

CloudQuery pricing

Starting at
Usage-based
Free access
Free trial

View full CloudQuery pricing intelligence →

Alternatives to CloudQuery

The reviewed substitutes for CloudQuery among the ELT platforms, and what would make each one the better answer.

Direct alternatives

Reviewed substitutes: products bought for the same job, where a team picks one.

Airbyte
Choose Airbyte if you need broad SaaS connector coverage with open-source flexibility and want a path from self-hosted to managed cloud.Applies to: Choosing between these two for the managed open elt decision.
Fivetran
Choose Fivetran if you want zero-maintenance data pipelines with the broadest connector library and enterprise-grade security clearances.Applies to: Choosing how data gets from sources into the warehouse.
Hevo Data
Choose Hevo if your team lacks dedicated data engineers and you want a reliable, no-code platform with transparent pricing and strong customer support.Applies to: Choosing between these two for the managed open elt decision.
Estuary Flow
Choose Estuary if your workloads demand sub-minute data freshness and you need CDC streaming and batch processing in a single platform.Applies to: Choosing between these two for the managed open elt decision.
Stitch
Choose Stitch if you have a small data team with straightforward SaaS-to-warehouse replication needs and want the lowest possible starting cost.Applies to: Choosing between these two for the managed open elt decision.

Related technologies

Normally used together rather than chosen between, so these are not alternatives.

Prefect
Choose Prefect if you need programmable orchestration for complex multi-step pipelines and your team writes Python-centric data workflows.Applies to: Whether a managed or code-first ingestion tool removes the need for an orchestrator, or runs inside one.
See detailed alternatives analysis

Looking for CloudQuery alternatives? CloudQuery is a powerful open-source ELT framework built in Go that specializes in extracting data from cloud APIs for infrastructure visibility, security posture management, and compliance. While CloudQuery excels at cloud asset inventory and SQL-based policy enforcement across AWS, GCP, Azure, and 50+ integrations, teams often need broader data pipeline capabilities, more SaaS connectors, or a fully managed experience. We evaluated the top CloudQuery alternatives across connector coverage, pricing, architecture, and operational overhead to help you find the right fit.

Top Alternatives Overview

Airbyte is the strongest open-source alternative with 600+ connectors and 21,000+ GitHub stars. It covers both SaaS and database replication with batch and CDC modes, and its Connector Development Kit lets you build custom connectors in under 30 minutes. Airbyte Cloud starts at $10/month with usage-based credit pricing, while the self-hosted edition is completely free. Choose Airbyte if you need broad SaaS connector coverage with open-source flexibility and want a path from self-hosted to managed cloud.

Fivetran is the market-leading managed ELT platform with 700+ fully managed connectors and proven enterprise scale, syncing 10.1 trillion rows per month across its customer base. It handles schema evolution, incremental updates, and connector maintenance automatically. The free tier includes 500,000 monthly active rows, with Enterprise plans offering 1-minute sync frequencies and hybrid deployment. Fivetran holds SOC 1/2, GDPR, HIPAA, ISO 27001, and PCI DSS Level 1 certifications. Choose Fivetran if you want zero-maintenance data pipelines with the broadest connector library and enterprise-grade security clearances.

Hevo Data is a no-code ELT platform with 150+ connectors and built-in dbt-based transformations. It processes over 1 petabyte of data monthly and offers log-based CDC for near-real-time database replication. Pricing starts with a free tier, then $299/month for Starter and $849/month for Professional, with usage-based event billing. Hevo automatically handles schema drift and provides 24/7 engineer support. Choose Hevo if your team lacks dedicated data engineers and you want a reliable, no-code platform with transparent pricing and strong customer support.

Estuary Flow is a real-time ETL/ELT platform that supports sub-second CDC streaming alongside batch workloads. It starts at $50/month with tiers up to $1,000/month, using a usage-based model priced per GB. Estuary combines streaming-native transforms with dbt integration for analytics. Choose Estuary if your workloads demand sub-minute data freshness and you need CDC streaming and batch processing in a single platform.

Prefect is a Python-native workflow orchestration platform for data pipelines, ETL/ELT jobs, and ML workflows. It is fully open-source under the Apache 2.0 license with a managed cloud control plane available. Prefect focuses on workflow orchestration rather than data extraction, providing scheduling, retries, observability, and dependency management for arbitrary Python tasks. Choose Prefect if you need programmable orchestration for complex multi-step pipelines and your team writes Python-centric data workflows.

Stitch is a cloud-first ELT tool focused on simplicity and low-cost entry for moving SaaS and database data into cloud warehouses. It offers a free tier for 1 user and Pro plans starting at $25/month. Stitch provides minimal in-pipe transformations and 30-minute minimum sync intervals. Choose Stitch if you have a small data team with straightforward SaaS-to-warehouse replication needs and want the lowest possible starting cost.

Architecture and Approach Comparison

CloudQuery is architecturally distinct from general-purpose ELT tools. It runs as a CLI written in Go that uses a plugin-based source/destination model to sync cloud infrastructure data into PostgreSQL, BigQuery, Snowflake, or other databases. Each sync extracts rows from cloud provider APIs (AWS, GCP, Azure, Kubernetes, and 70+ sources) and loads them into a normalized relational schema. The platform queries live infrastructure state rather than replicating application data, which makes it purpose-built for CSPM, FinOps, and cloud governance.

Airbyte and Fivetran take a connector-centric approach designed for SaaS and database replication. Airbyte runs each sync inside Docker containers with process isolation, using the Airbyte Protocol as a standardized JSON stream between source and destination. Fivetran operates as a fully managed service where connectors are maintained by the vendor, with automated schema evolution and idempotent pipelines that restart from the last successful state.

Hevo Data and Stitch sit on the managed, no-code end of the spectrum. Hevo uses isolated pipelines with auto-retries and self-healing schema mapping, while Stitch provides a lightweight extraction layer with minimal transformation. Estuary Flow stands apart with its streaming-first architecture that processes CDC events in sub-second latency, combining real-time and batch in one platform. Prefect operates at a different layer entirely as a workflow orchestrator: it schedules and monitors pipeline tasks but does not provide its own data connectors.

Pricing Comparison

ToolFree TierStarting Paid PricePricing ModelEnterprise
CloudQueryCLI (open-source)Rows synced/yearUsage-based (rows)Contact sales
AirbyteSelf-hosted (unlimited)$10/month (Cloud)Credits (volume-based)Median $16,350/year
Fivetran500K MARUsage-based MARMonthly Active RowsMedian $44,681/year
Hevo Data1M events$299/month (Starter)Event-basedCustom
Estuary FlowDeveloper tier$50/monthPer-GB usage$1,000/month+
Stitch1 user$25/month (Pro)Per-rowEnterprise custom
PrefectSelf-hosted (Apache 2.0)Cloud plans availableContact salesContact sales

CloudQuery's open-source CLI is free with no row limits, but the managed Platform requires contacting sales for pricing based on annual rows synced. Hevo Data's $299/month Starter tier sits between Airbyte Cloud's $10 entry and Fivetran's enterprise contracts, with the tradeoff being fewer connectors (150+) but built-in transformations and 24/7 support included.

When to Consider Switching

Switch from CloudQuery when your data needs extend beyond cloud infrastructure inventory. If you need to replicate data from SaaS applications like Salesforce, Stripe, HubSpot, or Google Analytics into a warehouse, tools like Airbyte (600+ connectors) or Fivetran (700+ connectors) cover those sources natively while CloudQuery does not.

Consider moving if you want a fully managed experience without operating CLI syncs. CloudQuery's self-hosted model requires running and scheduling syncs yourself, while Fivetran and Hevo Data handle everything from connector updates to schema evolution automatically. Teams that spent significant engineering time maintaining CloudQuery sync jobs report saving 40+ hours monthly after switching to managed platforms.

If real-time streaming matters to your use case, Estuary Flow delivers sub-second CDC latency that neither CloudQuery's batch sync nor most competitors can match. For teams that need workflow orchestration across multiple pipeline steps, ML training jobs, and custom Python logic, Prefect provides the scheduling and dependency management layer that CloudQuery lacks.

Stay with CloudQuery if your primary use case is cloud asset inventory, security posture management, or infrastructure compliance. No general-purpose ELT tool replicates CloudQuery's depth of coverage across AWS, GCP, Azure, Kubernetes, and security tools like Wiz in a single SQL-queryable schema.

Migration Considerations

CloudQuery uses a unique plugin-based architecture where sources and destinations are separate Go plugins. Migrating away means replacing CloudQuery's cloud API extraction with equivalent connectors in your target platform. Airbyte covers many cloud providers through its connector library, but the data schemas will differ from CloudQuery's normalized tables, so downstream SQL queries and dashboards need rewriting.

Data format compatibility is straightforward since CloudQuery loads into standard relational databases (PostgreSQL, BigQuery, Snowflake). Your existing destination tables and warehouse infrastructure remain usable with any replacement tool. The main migration effort centers on recreating extraction configurations and adapting any SQL-based policies or queries that reference CloudQuery's specific table schemas.

The learning curve varies significantly. Moving to Fivetran or Hevo Data reduces operational complexity since both are no-code platforms with web UIs. Switching to Airbyte keeps the open-source, self-hosted model but introduces Docker-based infrastructure and a different connector configuration system. Prefect requires Python proficiency and a fundamentally different mental model since you are writing orchestration code rather than configuring source-destination pairs.

For teams running CloudQuery alongside other tools, a gradual migration works well: keep CloudQuery for cloud infrastructure data where it excels, and add Airbyte or Fivetran for SaaS data replication. This hybrid approach avoids disrupting existing security and compliance workflows while expanding your data pipeline coverage.

Public signals

About these signals

Verified factual signals from public sources. They indicate observable activity or interest, not total adoption, product quality, or cost.

348 GitHub commits 90d6.5k GitHub starsOpenSSF score 5.4/10

See all signals from 3 sources
Source
Signals
Last updated
GitHub
Commits 90d:348↓9Stars:6.5k↑2
September 21, 2026
Product Hunt
Comments:1Reviews:0Votes:7
September 21, 2026
Security score:5.4/10

github.com/cloudquery/cloudquery

September 21, 2026

Frequently asked questions

What is CloudQuery?

CloudQuery is an open-source ELT (Extract, Load, Transform) framework designed for cloud infrastructure data. It allows users to efficiently extract and process large amounts of data from various sources.

Is CloudQuery free to use?

Yes, CloudQuery offers a freemium pricing model, allowing individuals and small teams to use it at no cost. Paid plans are available for larger organizations or those requiring advanced features.

How does CloudQuery compare to AWS Glue?

CloudQuery is designed specifically for cloud infrastructure data, whereas AWS Glue is a more general-purpose ETL service. While both tools can handle large datasets, CloudQuery's focus on cloud-native data and its open-source nature make it an attractive alternative for some users.

Can I use CloudQuery to migrate my on-premises database to the cloud?

Yes, CloudQuery supports data extraction from various sources, including on-premises databases. You can use it to extract your data and load it into a cloud-based storage solution or data warehouse.

What programming languages are supported by CloudQuery?

CloudQuery is built using Python, making it easy to integrate with other tools and services that also support this language. However, the framework's API allows developers to write extensions in any language they prefer.

Does CloudQuery offer data transformation capabilities out of the box?

Yes, CloudQuery includes a range of built-in data transformation functions, allowing users to easily manipulate and process their data. However, you can also extend or modify these transformations using custom Python code.

Related ELT Platforms

Other ELT platforms in the catalog. Same kind of product, not a substitution recommendation.