head to head · open source

steampipe vs wexflow

steampipe has 7,957 GitHub stars, 341 forks, 17 open issues and last shipped 3 days ago. wexflow has 842 stars, 189 forks, 0 open issues and last shipped 9 days ago. steampipe leads on adoption by 845% (7,957 vs 842 stars). steampipe is written in Go under AGPL-3.0; wexflow is written in C# under MIT. steampipe has attracted 4% as many forks as stars, wexflow 22%. steampipe was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (etl), so they are genuine substitutes rather than adjacent tools.

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

steampipe ★ 8.0K wexflow ★ 842 category Data & Analytics

← all 20902 open source comparisons

Side by side

steampipe wexflow
GitHub stars ★ 8.0K ★ 842
License AGPL-3.0 MIT
Written in Go C#
Last push 2026-09-17 2026-09-11
Forks ⑂ 341 ⑂ 189
Self-hosting Yes Yes
Data ownership Your server Your server

pick steampipe if

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

full steampipe 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 steampipe

Steampipe is an AGPL 3.0, Go based zero ETL tool that maps APIs and services to SQL tables, letting anyone who already writes SQL — cloud engineers, DevSecOps and security teams, data engineers — query live data from AWS, Azure, GCP, GitHub and Kubernetes without building a pipeline or running a database.

read the full steampipe 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.

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

Frequently asked questions

Is steampipe or wexflow more popular?

steampipe has 7,957 GitHub stars and wexflow has 842. steampipe has the larger community by that measure.

Are steampipe and wexflow free?

Both are open source. steampipe is licensed under AGPL-3.0 and wexflow under MIT. Neither carries a licence fee.

What is the difference between steampipe and wexflow?

steampipe 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, steampipe or wexflow?

Choose steampipe if you want the larger community (7,957 stars) or its AGPL-3.0 licence terms. Choose wexflow if its feature set, stack or MIT licence fits better. Both are self-hostable.