Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Lithic

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

Lithic

APIs

API-first card issuing platform with direct Visa, Mastercard and Amex network connections

From
On request
Free plan
No

The short version

  • Ona (formerly Gitpod) starts at $20/mo; Lithic prices on request.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only Lithic lists direct network connections.
  • Where Lithic falls short: pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation.
  • Prices and features on this page were last checked on 20 November 2026.

How do Ona (formerly Gitpod) and Lithic differ?

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

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

Which features does each one have?

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

  • Direct network connections
  • Processor Client mode
  • Lithic Program Management
  • Card lifecycle APIs
  • Sandbox environment
  • Real-time authorization controls

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

Lithic

  • A fintech wanting direct Visa or Mastercard network access rather than routing through a third-party processornot Ona (formerly Gitpod)
  • A company that already holds its own issuing licence and wants API access without full programme managementnot Ona (formerly Gitpod)
  • A neobank or expense platform wanting Lithic to manage bank and network relationships end to endnot Ona (formerly Gitpod)
  • A product team prototyping a card programme in sandbox before committing to a launchnot Ona (formerly Gitpod)

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

Lithic

  • Pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation
  • Choosing Processor Client mode still leaves the company responsible for holding its own issuing licence and managing the regulatory relationship, which is a substantial undertaking many teams underestimate
  • As with any card infrastructure provider, an outage or network issue at Lithic becomes a direct outage for every card programme built on it, and a customer has limited visibility into root cause during an incident
  • Building a card programme on API infrastructure requires real engineering investment; it is not a plug-and-play product for a non-technical team
  • Switching card infrastructure providers after launch is a major undertaking involving card reissuance and programme migration, so the initial choice carries lasting lock-in

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

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

Lithic

On request
  • LithicOn request
    • Volume and interchange-based pricing, not published
    • Separate Processor Client and Program Management pricing tracks
    • Custom quote required via sales

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

  • You need direct network connections.
  • You work on Web, API.
  • You also want processor client mode.

Questions people ask

Is Ona (formerly Gitpod) or Lithic better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and Lithic 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 Lithic?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and On request for Lithic.
Does Ona (formerly Gitpod) or Lithic run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. Lithic runs on Web, API.
Can I use Ona (formerly Gitpod) for free?
Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. Lithic 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 Lithic is typically brought in for.
What can Ona (formerly Gitpod) do that Lithic cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Lithic covers Direct network connections, Processor Client mode, Lithic Program Management, Card lifecycle APIs.

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.

Lithic: Does Lithic publish pricing?

No, pricing is volume-based and requires a sales conversation.

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.

Lithic: What is the difference between Processor Client and Program Management?

Processor Client suits companies with their own issuing licence and bank relationships; Program Management is for companies wanting Lithic to coordinate those relationships on their behalf.

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.

Lithic: Which networks does it connect to?

Visa, Mastercard and American Express directly.

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