Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Steampipe

Ona (formerly Gitpod) logo

Ona (formerly Gitpod)

Developer Tools

Cloud development environments repositioned as a control plane for software engineering agents

From
Free
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

  • Each has a real cost: Ona (formerly Gitpod) acquisition risk has already materialised: the company closed a sale to OpenAI on 10 August 2026 and now sits inside the Codex team, so nothing public guarantees pricing, continuity or neutrality between model vendors beyond honouring existing commitments.; 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: Ona (formerly Gitpod) covers Ephemeral environments, 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 Ona (formerly Gitpod) and Steampipe actually diverge.

Attributes where Ona (formerly Gitpod) and Steampipe differ
AttributeOna (formerly Gitpod)Steampipe
Pricing modelPer month by compute unitOpen source, with paid hosting through Turbot Pipes
PlatformsWeb, Linux, macOS, Windows, AWS, Google Cloud PlatformmacOS, Linux, Windows, Docker, Web

Identical on both: starting price (Free), free tier (Yes), 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 Ona (formerly Gitpod)

  • Ephemeral environments
  • Agent sessions
  • Bring your own cloud
  • Devcontainer standard
  • Compute unit budgeting
  • Enterprise identity

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.

Ona (formerly Gitpod)

  • Giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setupnot Steampipe
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot Steampipe
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Steampipe
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Steampipe

Steampipe

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

Where each one falls short

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

Ona (formerly Gitpod)

  • Acquisition risk has already materialised: the company closed a sale to OpenAI on 10 August 2026 and now sits inside the Codex team, so nothing public guarantees pricing, continuity or neutrality between model vendors beyond honouring existing commitments.
  • Two disruptive changes of direction inside a year, from development environments to agent orchestration and then from independence to acquisition, mean the product a browser IDE buyer originally chose no longer exists in that form.
  • The Gitpod Classic sunset on 15 October 2025 required manual conversion of configuration, hand-moved secrets, self-rescued workspace data and a brand new account, which is the clearest available precedent for how the vendor handles deprecation.
  • Community self-hosting is finished: the AGPL-3.0 repository is deprecated by its own README, and self-hosted now means a vendor-operated install in your AWS or GCP account, with no Azure, no on-premises and no air-gapped path.
  • Pricing is difficult to model because it runs on a compute unit currency where subscription credits expire at the end of the month, the mapping from units to actual compute is not published on the pricing page, and Enterprise is quotation only.

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

Ona (formerly Gitpod)

Free
  • FreeFree
    • Up to 3 parallel environments
    • Machines up to 4 vCPU, 16 GB memory and 80 GB disk
    • Ona Cloud multi-tenant only
  • Core$20/month
    • From 20 US dollars a month, up to 100 team members
    • Includes 80 to 2,200 recurring compute units a month depending on tier
    • Additional units from 10 US dollars per 40 units
  • Enterprise$undefined/year
    • Single-tenant deployment in your own AWS or GCP account
    • SAML and OIDC single sign-on
    • Dedicated account management and forward deployed engineers

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 Ona (formerly Gitpod) if

  • You need ephemeral environments.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows, AWS, Google Cloud Platform.
  • You also want agent sessions.
Ona (formerly Gitpod) 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 Ona (formerly Gitpod) or Steampipe better?
Neither clearly leads. Ona (formerly Gitpod) 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, Ona (formerly Gitpod) or Steampipe?
Ona (formerly Gitpod) starts at Free and Steampipe at Free.
Does Ona (formerly Gitpod) or Steampipe run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS, Google Cloud Platform. Steampipe runs on macOS, Linux, Windows, Docker, Web.
Can I use Ona (formerly Gitpod) for free?
Both have a free tier, so you can try either at no cost before committing.
What is Ona (formerly Gitpod) best used for?
Ona (formerly Gitpod) is most often used for giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setup, running several coding agents in parallel against real databases and services instead of on a laptop, keeping source code off contractor and offshore laptops by moving the whole environment into a controlled account, reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machine. Of those, giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setup and running several coding agents in parallel against real databases and services instead of on a laptop are not what Steampipe is typically brought in for.
What can Ona (formerly Gitpod) do that Steampipe cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Steampipe covers SQL over live APIs, Wide plugin set, Embedded Postgres, Compliance benchmarks.

Answered from the vendors’ own pages

Ona (formerly Gitpod): Is Gitpod still called Gitpod?

No. It rebranded to Ona in September 2025, and gitpod.io now redirects to ona.com. The company was acquired by OpenAI in a deal that closed on 10 August 2026.

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.

Ona (formerly Gitpod): Can I still self-host it for free?

No. The AGPL-3.0 self-hosted project is deprecated by its own README. What is offered now is a vendor-operated single-tenant install in your AWS or GCP account on the Enterprise plan.

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.

Ona (formerly Gitpod): What happened to Gitpod Classic?

Pay-as-you-go Classic was switched off on 15 October 2025. Migration required converting gitpod.yml to devcontainer.json, moving secrets by hand, downloading workspace data before the cutoff and creating a new account.

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.

Ona (formerly Gitpod): What does it cost?

Core starts at 20 US dollars a month and includes a monthly allowance of Ona Compute Units, with more from 10 dollars per 40 units. Subscription credits expire monthly. Enterprise is quoted.

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 Ona (formerly Gitpod)

More on Steampipe

Keep looking

Other head to heads