Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Ozone API

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
Ozone API logo

Ozone API

APIs

Standards-compliant open banking API layer for banks and regulators

From
On request
Free plan
No

The short version

  • Ona (formerly Gitpod) starts at $20/mo; Ozone API prices on request.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only Ozone API lists consent management.
  • Where Ozone API falls short: value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend.
  • Prices and features on this page were last checked on 20 November 2026.

How do Ona (formerly Gitpod) and Ozone API differ?

Ona (formerly Gitpod) and Ozone API differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Ona (formerly Gitpod) and Ozone API actually diverge.

Attributes where Ona (formerly Gitpod) and Ozone API differ
AttributeOna (formerly Gitpod)Ozone API
Starting priceFreeOn request
Pricing modelPer month by compute unitQuote
Free tierYesNo
PlatformsWeb, Linux, macOS, Windows, AWSWeb, API, Linux
CategoryDeveloper ToolsAPIs

Which features does each one have?

They share no listed features; 6 appear only for Ona (formerly Gitpod) and 6 only for Ozone API. 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 Ozone API

  • Multi-standard support
  • Consent management
  • Developer portal
  • Regulatory reporting
  • Premium API monetisation
  • Deployment flexibility

What is each one used for?

Ozone API is most often brought in for A regulator or standards body building national open finance infrastructure. 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 Ozone API
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot Ozone API
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Ozone API
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Ozone API

Ozone API

  • A building society facing an open banking compliance deadline with no API team of its ownnot Ona (formerly Gitpod)
  • A bank operating in several jurisdictions that must satisfy different open banking standards at oncenot Ona (formerly Gitpod)
  • A regulator or standards body building national open finance infrastructurenot Ona (formerly Gitpod)
  • A bank wanting to sell premium APIs beyond the regulatory minimum without building entitlement plumbingnot Ona (formerly Gitpod)

Where do Ona (formerly Gitpod) and Ozone API fall 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

Ozone API

  • It provides the API layer, not the core connectivity, so the bulk of the project is still integrating your own core banking systems and that cost is not in the licence
  • Value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend
  • It is a small UK vendor selling to large regulated institutions, which raises procurement and vendor viability questions during bank due diligence
  • Premium API monetisation is a genuine capability but few banks have found real demand, so revenue projections used to justify the purchase often do not materialise
  • Standards evolve continuously and each revision means a change programme in your own systems, even where Ozone absorbs the specification work at the API edge

How much do Ona (formerly Gitpod) and Ozone API cost?

Ona (formerly Gitpod) has a free plan, with paid plans from $20/mo; Ozone API is priced on request. Plan by plan below, from each vendor's own pricing page.

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/mo
    • 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
  • EnterpriseOn request
    • Single-tenant deployment in your own AWS or GCP account
    • SAML and OIDC single sign-on
    • Dedicated account management and forward deployed engineers

Ozone API

On request
  • Ozone APIOn request
    • Annual licence or managed service subscription, quoted
    • Scaling by institution size, standards in scope and API call volume
    • Implementation and core integration charged separately

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.
  • You also want agent sessions.

Choose Ozone API if

  • You need multi-standard support.
  • You work on Web, API, Linux.
  • You also want consent management.

Questions people ask

Is Ona (formerly Gitpod) or Ozone API better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and Ozone API 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 Ozone API?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and On request for Ozone API.
Does Ona (formerly Gitpod) or Ozone API run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. Ozone API runs on Web, API, Linux.
Can I use Ona (formerly Gitpod) for free?
Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. Ozone API 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 Ozone API is typically brought in for.
What can Ona (formerly Gitpod) do that Ozone API cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Ozone API covers Multi-standard support, Consent management, Developer portal, Regulatory reporting.

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.

Ozone API: Is this a competitor to Plaid or TrueLayer?

No, the opposite side. Ozone is bought by the bank exposing data; Plaid and TrueLayer consume it on behalf of third parties.

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.

Ozone API: Does it connect to my core banking system?

It provides the standards-compliant API surface and adapters, but connecting your core is an integration project you scope separately.

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.

Ozone API: Which standards does it support?

UK Open Banking, Berlin Group, FDX, Consumer Data Right and Gulf regional standards, among others, from one platform.

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

Other head to heads