Softwr

Web Development · head to head

Rollup vs Steampipe

Rollup logo

Rollup

Web Development

JavaScript module bundler built for libraries

From
Free
Rated
-
Steampipe logo

Steampipe

Developer Tools

Query cloud APIs, SaaS tools and code with SQL, with no extract or load step

From
Free
Rated
-

The short version

  • Each has a real cost: Rollup slower than the Go and Rust bundlers that followed it, since it is written in JavaScript; Steampipe aGPL-3.0 across all four engines is a procurement blocker at organisations that ban the licence outright, and the network clause reaches any internal portal or service that puts a web interface in front of it.
  • They diverge on capability: Rollup covers Tree shaking, Steampipe covers SQL over live APIs.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Rollup and Steampipe actually diverge.

Attributes where Rollup and Steampipe differ
AttributeRollupSteampipe
Pricing modelOpen source, no licence feeOpen source, with paid hosting through Turbot Pipes
PlatformsLinux, macOS, WindowsmacOS, Linux, Windows, Docker, Web
CategoryWeb DevelopmentDeveloper Tools

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Rollup

  • Tree shaking
  • Clean output
  • Multiple output formats
  • Plugin API

Only in Steampipe

  • SQL over live APIs
  • Wide plugin set
  • Embedded Postgres
  • Compliance benchmarks
  • Joins across providers
  • Hosted option

What people use each for

The jobs each tool is most often brought in to do.

Rollup

  • Publishing a JavaScript library in several module formatsnot Steampipe
  • Builds where output size and cleanliness matter more than build speednot Steampipe
  • Producing ES module output for consumers who will bundle it themselvesnot Steampipe

Steampipe

  • Security teams answering posture questions against live cloud accounts rather than a nightly exportnot Rollup
  • Compliance evidence gathering where the answer must reflect the account at the moment it is askednot Rollup
  • Inventory and drift questions spanning several cloud providers in one querynot Rollup
  • Engineers who would rather write SQL than learn each provider command line toolnot Rollup

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Rollup

  • Slower than the Go and Rust bundlers that followed it, since it is written in JavaScript
  • Application concerns like dev servers and hot reloading are not its job, so app builds need Vite on top
  • Configuration for non-trivial applications gets verbose compared with tools that assume more

Steampipe

  • AGPL-3.0 across all four engines is a procurement blocker at organisations that ban the licence outright, and the network clause reaches any internal portal or service that puts a web interface in front of it.
  • Dashboards, benchmarks and mods were removed from Steampipe entirely at version 1.0 in October 2024 and now live in a separate product, so pre-2024 documentation and tutorials describe commands that no longer exist.
  • Live querying is bound by cloud provider API rate limits and keeps no persistent store by default, which is why a separate DuckDB-backed product exists for log volumes and why large accounts return slowly.
  • The company is fifteen people and bootstrapped, maintaining four command line tools plus a hosted service plus two further products, and the newer tools have thin community traction relative to that surface area.
  • Hosted tiers include only three users regardless of tier, with additional Enterprise users charged separately, so a team of thirty costs an order of magnitude more than the headline figure before compute and storage are counted.

Pricing, plan by plan

Rollup

Free
  • RollupFree
    • Full functionality
    • Commercial use permitted
    • Community support

Steampipe

Free
  • Steampipe CLIFree
    • AGPL-3.0
    • All plugins
    • No user or query limits
  • Pipes DeveloperFree
    • One user
    • 400 compute minutes
    • 3GB storage
  • Pipes Team$49/month
    • Three users
    • 2,000 compute minutes
    • 20GB storage
  • Pipes Enterprise$249/month
    • Three users
    • 10,000 compute minutes
    • 100GB storage

Which should you pick?

Choose Rollup if

  • You need tree shaking.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want clean output.

Choose Steampipe if

  • You need sql over live apis.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Docker, Web.
  • You also want wide plugin set.

Questions people ask

Is Rollup or Steampipe better?
Neither clearly leads. Rollup starts at Free and Steampipe at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Rollup or Steampipe?
Rollup starts at Free and Steampipe at Free.
Does Rollup or Steampipe run on more platforms?
Rollup runs on Linux, macOS, Windows. Steampipe runs on macOS, Linux, Windows, Docker, Web.
Can I use Rollup for free?
Both have a free tier, so you can try either at no cost before committing.
What is Rollup best used for?
Rollup is most often used for publishing a javascript library in several module formats, builds where output size and cleanliness matter more than build speed, producing es module output for consumers who will bundle it themselves. Of those, publishing a javascript library in several module formats and builds where output size and cleanliness matter more than build speed are not what Steampipe is typically brought in for.
What can Rollup do that Steampipe cannot?
Rollup covers Tree shaking, Clean output, Multiple output formats, Plugin API. Steampipe covers SQL over live APIs, Wide plugin set, Embedded Postgres, Compliance benchmarks.

Answered from the vendors’ own pages

Rollup: Is Rollup free?

Yes, open source under the MIT licence.

Steampipe: When did Steampipe become AGPL?

May 2021, about four months after the project went public. It is a settled licence rather than a recent change, and predates the Business Source Licence wave it is often confused with.

Rollup: Rollup or webpack?

Rollup is the usual choice for libraries thanks to cleaner output and better tree shaking. webpack remains stronger for complex applications with heavy asset handling.

Steampipe: Where did the dashboards and benchmarks go?

Into Powerpipe. They were deprecated in March 2024 and removed from Steampipe at version 1.0 in October 2024, so the check, dashboard, mod and variable commands are gone.

Rollup: Do I need Rollup if I use Vite?

Not directly. Vite uses Rollup for production builds, so you already benefit from it.

Steampipe: Is it fast on a large cloud estate?

Not always. Queries call provider APIs at request time, so rate limits rather than query planning set the pace, and there is no persistent store by default.

Steampipe: Does the AGPL affect internal use?

Running it internally for your own analysis is fine. Putting a web interface in front of it that other people use is where the network clause becomes a question for your legal team.

Steampipe: Is a bootstrapped vendor a risk?

It cuts both ways. There is no investor pressure toward a licence change or an exit, and there are also fifteen people supporting a large product surface.

Share

Related pages

Other head to heads