Softwr

Developer Tools · head to head

Cortex vs Steampipe

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Rated
-
Full reviewWebsite
Steampipe logo

Steampipe

Developer Tools

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

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Steampipe has a free tier, so it costs nothing to try first.
  • Each has a real cost: Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.; 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: Cortex covers Service catalogue, 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 Cortex and Steampipe actually diverge.

Attributes where Cortex and Steampipe differ
AttributeCortexSteampipe
Starting priceOn requestFree
Pricing modelquoteOpen source, with paid hosting through Turbot Pipes
Free tierNoYes
PlatformsWeb, APImacOS, Linux, Windows, Docker, Web

Identical on both: user rating (Not yet rated), category (Developer Tools).

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 Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

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.

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Steampipe
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Steampipe
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Steampipe
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Steampipe

Steampipe

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

Where each one falls short

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

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.

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

Cortex

On request
  • Cortex$undefined/year
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

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 Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.
Cortex review

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.
Steampipe review

Questions people ask

Is Cortex or Steampipe better?
Neither clearly leads. Cortex starts at On request and Steampipe at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Steampipe?
Steampipe has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Steampipe.
Does Cortex or Steampipe run on more platforms?
Cortex runs on Web, API. Steampipe runs on macOS, Linux, Windows, Docker, Web.
Can I use Steampipe for free?
Yes. Steampipe has a free tier, so you can try it without paying. Cortex starts at On request.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Steampipe is typically brought in for.
What can Cortex do that Steampipe cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Steampipe covers SQL over live APIs, Wide plugin set, Embedded Postgres, Compliance benchmarks.

Answered from the vendors’ own pages

Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

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.

Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

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.

Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

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.

Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

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

More on Cortex

More on Steampipe

Keep looking

Other head to heads