Steampipe
v2.3.0 open-sourceThe section your link pointed to isn't on Steampipe's page any more, so we've brought you to the top.
Zero-ETL tool that queries APIs and cloud services in real-time using SQL via plugins that map APIs to database tables.
steampipe query "select account_id, arn from aws_account" --output json | jq '.columns' select * from gcp_vertex_ai_model steampipe query "SELECT * FROM aws_acmpca_certificate_authority" steampipe query "select version from steampipe_plugin where name = 'aws'" steampipe query "select 1" 2> steampipe_errors.log steampipe query "select * from gcp_cloud_asset;" steampipe query 'SELECT * FROM steampipe_internal.steampipe_plugin_column' steampipe query "SELECT * FROM steampipe_plugin_limiter;" steampipe plugin install --skip-config SELECT * FROM steampipe_connection_state; steampipe plugin install aws --progress=false export STEAMPIPE_CACHE=disabled && steampipe serve steampipe dashboard run --max-parallel 20 OTEL_SERVICE_NAME=steampipe OTEL_TRACES_EXPORTER=otlp steampipe query 'select * from aws_ec2_instance' steampipe check my_control --output json > /tmp/timing.json && steampipe query 'select * from steampipe_command.scan_metadata where timing_file = '"'"'/tmp/timing.json'"'"'' steampipe check my_check --show-password steepipe --autocomplete steampipe service start
Summary
Steampipe is an open-source command-line tool that lets you query cloud APIs and services using SQL, exposing resources like AWS, Azure, or Kubernetes objects as queryable database tables through plugins. It runs as a single binary — install it locally with a package manager or shell script, run interactive queries, or drop it into a CI/CD pipeline — with no server to stand up, since it bundles its own Postgres instance. This fits cloud security and compliance teams who need to audit configuration across accounts and providers without writing bespoke API clients for each one, and platform engineers who want one query language across dozens of services. Its README frames it as the zero-ETL way to query APIs, distinguishing it from ETL pipelines or per-cloud CLI tools by treating live API data as SQL tables directly. With 58 contributors, 345 commits and 49 plugin and CLI releases in the past year, most recently 11 days ago, it is under active development.
Zero-ETL tool that queries APIs and cloud services in real-time using SQL via plugins that map APIs to database tables.
How Steampipe helps
Which Kubernetes workloads and cloud resources share the same misconfiguration?
joins tables from different plugins in one SQL statement, so a single query can compare pod specs against storage buckets or IAM policies side by side
Which S3 buckets, storage accounts, or security groups are open to the world right now?
queries the provider's live API at the moment the query runs and returns the current setting, not a cached snapshot from a prior scan
Who has access they shouldn't across my cloud accounts?
tables for IAM users, roles, and policies can be joined and filtered in one query to surface grants that don't match the access you expect
Are my different cloud accounts and providers configured consistently with each other?
the same SQL query runs against equivalent tables from AWS, Azure, Kubernetes, or other plugins, so differences show up as rows that don't match across providers
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Steampipe, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Steampipe puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
steampipe.io, every changeTurbot's home page and 9 more pages as they looked each month from September 2021 to October 2026: 21 renders, 5 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
26 entries
No entries match these filters.
- October 20251
- September 20251
- September 20242
- May 20241
- April 20241
- March 20246
- February 20241
- January 20243
- December 20231
- October 20231
- June 20231
- May 20232
- March 20231
- January 20231
- August 20221
- June 20221
- January 20211
Project health
Issue, contributor and maintainer activity in turbot/steampipe, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 7 −4 vs prior 12 months
- Maintainers 3 +2 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 4.5 days first maintainer reply 5.3 days
- Open backlog 5 of 2,315 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 5
- Contributors / month 2
- Commits / month 6
- Stars 7,957
- bugs 72%
- features 7%
- docs 1%
- other 20%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.