Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Unit

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
Unit logo

Unit

APIs

Banking as a service platform for embedding deposit accounts, cards and payments, with a sponsor bank behind it

From
On request
Free plan
No

The short version

  • Ona (formerly Gitpod) starts at $20/mo; Unit prices on request.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only Unit lists deposit accounts.
  • Prices and features on this page were last checked on 20 November 2026.

How do Ona (formerly Gitpod) and Unit differ?

Ona (formerly Gitpod) and Unit 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 Unit actually diverge.

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

Which features does each one have?

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

  • Deposit accounts
  • Card issuing
  • Payments
  • White label components
  • Compliance operations
  • Lending
  • Programme reporting
  • Sandbox

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

Unit

  • A vertical SaaS platform for contractors that wants to hold customer funds and issue expense cards without pursuing a charternot Ona (formerly Gitpod)
  • A payroll or benefits platform embedding accounts so employees can be paid ahead of schedulenot Ona (formerly Gitpod)
  • A marketplace that wants seller balances to sit in real accounts under its own brand rather than as ledger entries at a processornot Ona (formerly Gitpod)
  • A company that needs interchange revenue from a card programme to make the unit economics of its core product worknot Ona (formerly Gitpod)

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

Unit

  • Your product depends on a sponsor bank you do not contract with directly, and 2024 showed what that means: Thread Bank received an FDIC enforcement action naming its banking as a service programmes and Blue Ridge Bank went under an OCC consent order and offboarded fintech partners
  • Programme approval by the bank is a separate gate from signing with Unit, and it can add months and impose product restrictions that were not visible during the commercial conversation
  • Compliance obligations are shared but the operational load lands on you, and platforms consistently underestimate the staffing needed for disputes, escalations and the bank ongoing oversight requests
  • Pricing is unpublished and blends platform fees, per-account and per-transaction charges and interchange sharing, which makes it hard to model unit economics before you have volume and easy to be surprised by the minimum
  • Migrating a live deposit programme to a different provider or bank is extremely disruptive because it involves moving customer accounts and card credentials, so switching costs are far higher than for ordinary software

How much do Ona (formerly Gitpod) and Unit cost?

Ona (formerly Gitpod) has a free plan, with paid plans from $20/mo; Unit 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

Unit

On request
  • Unit Banking as a ServiceOn request
    • Platform fee plus per-account and per-transaction charges, quoted
    • Interchange sharing arrangements negotiated per programme
    • Minimum commitment typical

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

  • You need deposit accounts.
  • You work on Web, iOS, Android.
  • You also want card issuing.

Questions people ask

Is Ona (formerly Gitpod) or Unit better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and Unit 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 Unit?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and On request for Unit.
Does Ona (formerly Gitpod) or Unit run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. Unit runs on Web, iOS, Android.
Can I use Ona (formerly Gitpod) for free?
Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. Unit 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 Unit is typically brought in for.
What can Ona (formerly Gitpod) do that Unit cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Unit covers Deposit accounts, Card issuing, Payments, White label components.

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.

Unit: Who actually holds the money?

A chartered partner bank, not Unit. Deposits sit at the sponsor bank and FDIC insurance flows from that bank, so its condition is your condition.

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.

Unit: What happened with Unit sponsor banks in 2024?

Thread Bank received an FDIC enforcement action that explicitly named its banking as a service and lending as a service programmes, and Blue Ridge Bank was under an OCC consent order from January 2024 and offboarded fintech partners. Blue Ridge exited the order in late 2025.

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.

Unit: What does Unit cost?

Not published. Expect a platform fee, per-account and per-transaction charges, an interchange share and a minimum commitment.

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.

Unit: Do we need our own compliance team?

Yes. Unit supplies tooling and the bank sets the rules, but disputes, escalations and evidence for bank oversight require named people on your side.

Share

Related pages

Other head to heads