Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Greenhouse

Ona (formerly Gitpod) logo

Ona (formerly Gitpod)

Developer Tools

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

From
Free
Free plan
Yes
Full reviewWebsite
Greenhouse logo

Greenhouse

Technology

Hiring software for growing companies

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Only Ona (formerly Gitpod) has a free tier, so it costs nothing to try first.
  • 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.; Greenhouse core plan lacks talent discovery and contact lookups
  • They diverge on capability: Ona (formerly Gitpod) covers Ephemeral environments, Greenhouse covers Applicant tracking.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Ona (formerly Gitpod) and Greenhouse actually diverge.

Attributes where Ona (formerly Gitpod) and Greenhouse differ
AttributeOna (formerly Gitpod)Greenhouse
Starting priceFreeOn request
Pricing modelPer month by compute unitquote
Free tierYesNo
PlatformsWeb, Linux, macOS, Windows, AWS, Google Cloud PlatformWeb, Ios, Android, Api
CategoryDeveloper ToolsTechnology
FoundedUnknown2012

Identical on both: 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 Ona (formerly Gitpod)

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

Only in Greenhouse

  • Applicant tracking
  • Interview scheduling
  • Scorecard system
  • Job board posting
  • Candidate CRM
  • Reporting & analytics
  • Offer management
  • EEO compliance

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 Greenhouse
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot Greenhouse
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Greenhouse
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Greenhouse

Greenhouse

  • Enterprise hiring and recruiting automationnot Ona (formerly Gitpod)
  • Multi-location and multi-team talent acquisitionnot Ona (formerly Gitpod)
  • Structured interview process managementnot 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.

Greenhouse

  • Core plan lacks talent discovery and contact lookups
  • Core plan lacks email automation and applicant texting
  • Plus plan lacks resume anonymisation and application limits
  • Plus plan lacks audit logging and developer tools
  • Pricing customised by hiring volume and company size, not published
  • Only Pro tier offers audit logs and developer sandbox

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

Greenhouse

On request

No published plan breakdown. See the Greenhouse review.

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

  • You need applicant tracking.
  • You work on Web, Ios, Android, Api.
  • You also want interview scheduling.
Greenhouse review

Questions people ask

Is Ona (formerly Gitpod) or Greenhouse better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and Greenhouse at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ona (formerly Gitpod) or Greenhouse?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and On request for Greenhouse.
Does Ona (formerly Gitpod) or Greenhouse run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS, Google Cloud Platform. Greenhouse runs on Web, Ios, Android, Api.
Can I use Ona (formerly Gitpod) for free?
Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. Greenhouse starts at On request.
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 Greenhouse is typically brought in for.
What can Ona (formerly Gitpod) do that Greenhouse cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Greenhouse covers Applicant tracking, Interview scheduling, Scorecard system, Job board posting.

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.

Greenhouse: How much does Greenhouse cost?

Greenhouse does not publish specific pricing. The company states that pricing is customized based on your hiring needs, hiring volume, organizational complexity, and required features.

Source
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.

Greenhouse: What are the Greenhouse pricing tiers?

Greenhouse offers three plan levels: Core (basic hiring structure), Plus (multi-location optimization), and Pro (complex enterprise hiring). Exact pricing requires contacting Greenhouse for a custom quote.

Source
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.

Greenhouse: Do all Greenhouse tiers include the same features?

No. Core includes sourcing and scheduling, Plus adds automation and texting, and Pro adds enterprise data configuration and audit logs. All tiers can be customized.

Source
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.

Share

Related pages

More on Ona (formerly Gitpod)

More on Greenhouse

Keep looking

Other head to heads