head to head · open source

CloudQuery vs wexflow

CloudQuery has 6,521 GitHub stars, 558 forks, 166 open issues and last shipped 2 days ago. wexflow has 842 stars, 189 forks, 0 open issues and last shipped 9 days ago. CloudQuery leads on adoption by 674% (6,521 vs 842 stars). CloudQuery is written in Go under MPL-2.0; wexflow is written in C# under MIT. CloudQuery has attracted 9% as many forks as stars, wexflow 22%. CloudQuery was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

CloudQuery ★ 6.5K wexflow ★ 842 category Data & Analytics

← all 20902 open source comparisons

Side by side

CloudQuery wexflow
GitHub stars ★ 6.5K ★ 842
License MPL-2.0 MIT
Written in Go C#
Last push 2026-09-18 2026-09-11
Forks ⑂ 558 ⑂ 189
Self-hosting Yes Yes
Data ownership Your server Your server

pick CloudQuery if

  • You weight community size — 6.5K stars and counting
  • You want the MPL-2.0 license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full CloudQuery profile →

pick wexflow if

  • You want the wexflow feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches C#
  • You evaluated both and wexflow fits your workflow better

full wexflow profile →

About CloudQuery

CloudQuery is an open source, Go based cloud asset inventory and ELT tool, licensed under MPL 2.0, that syncs metadata from AWS, Azure, GCP, and more than 70 cloud and SaaS sources into a data warehouse so platform, security, and FinOps teams can query it with SQL.

read the full CloudQuery overview →

About wexflow

Wexflow is an open source, cross platform workflow automation engine written in C for developers and technical users who need to automate file operations, system processes, scripting, networking, scheduling and alerts instead of maintaining that plumbing by hand.

read the full wexflow overview →

More in Data & Analytics

Browser Use ★ 115K Mermaid ★ 90K Crawl4AI ★ 84K Scrapling ★ 82K Apache Superset ★ 75K echarts ★ 67K

Related comparisons

airbyte vs cube airbyte vs shardingsphere cube vs shardingsphere airbyte vs debezium cube vs debezium shardingsphere vs debezium airbyte vs cocoindex cube vs cocoindex firecrawl vs scrapy firecrawl vs crawlee browser-use vs crawl4ai browser-use vs scrapling playwright vs crawl4ai browser-use vs scrapy playwright vs scrapling crawl4ai vs scrapling godot vs pixijs mermaid vs apache-superset three-js vs pixijs supabase vs metabase mermaid vs echarts grafana vs apache-superset apache-superset vs echarts mermaid vs metabase

More Data Engineering & Integration projects

Compare either of these against the rest of the Data Engineering & Integration field.

CloudQuery vs Airbyte CloudQuery vs Cube CloudQuery vs shardingsphere CloudQuery vs debezium CloudQuery vs CocoIndex CloudQuery vs seatunnel CloudQuery vs steampipe CloudQuery vs realtime CloudQuery vs flink-cdc CloudQuery vs Lightdash CloudQuery vs fluvio CloudQuery vs whodb

Frequently asked questions

Is CloudQuery or wexflow more popular?

CloudQuery has 6,521 GitHub stars and wexflow has 842. CloudQuery has the larger community by that measure.

Are CloudQuery and wexflow free?

Both are open source. CloudQuery is licensed under MPL-2.0 and wexflow under MIT. Neither carries a licence fee.

What is the difference between CloudQuery and wexflow?

CloudQuery is written in Go and wexflow in C#. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, CloudQuery or wexflow?

Choose CloudQuery if you want the larger community (6,521 stars) or its MPL-2.0 licence terms. Choose wexflow if its feature set, stack or MIT licence fits better. Both are self-hostable.