Softwr

APIs · head to head

Enfuce vs Ona (formerly Gitpod)

Enfuce logo

Enfuce

APIs

European issuer processor holding its own payment institution licence

From
On request
Free plan
No
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

The short version

  • Ona (formerly Gitpod) starts at $20/mo; Enfuce prices on request.
  • Only Enfuce lists licensed issuing; only Ona (formerly Gitpod) lists ephemeral environments.
  • Where Enfuce falls short: coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.
  • Prices and features on this page were last checked on 20 November 2026.

How do Enfuce and Ona (formerly Gitpod) differ?

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

Attributes where Enfuce and Ona (formerly Gitpod) differ
AttributeEnfuceOna (formerly Gitpod)
Starting priceOn requestFree
Pricing modelQuotePer month by compute unit
Free tierNoYes
PlatformsWeb, APIWeb, Linux, macOS, Windows, AWS
CategoryAPIsDeveloper Tools

Which features does each one have?

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

  • Licensed issuing
  • Card processing
  • Tokenisation
  • Spend controls
  • Multi-currency programmes
  • Carbon and data services

Only in Ona (formerly Gitpod)

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

What is each one used for?

Enfuce is most often brought in for A bank migrating an existing European card portfolio off a legacy processor. The jobs each tool is most often brought in to do.

Enfuce

  • A European fintech launching cards without spending two quarters finding a sponsor banknot Ona (formerly Gitpod)
  • A corporate issuing fuel or expense cards across several EU countries on one programmenot Ona (formerly Gitpod)
  • A bank migrating an existing European card portfolio off a legacy processornot Ona (formerly Gitpod)
  • A programme that must report cardholder transaction carbon data to meet sustainability commitmentsnot Ona (formerly Gitpod)

Ona (formerly Gitpod)

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

Where do Enfuce and Ona (formerly Gitpod) fall short?

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

Enfuce

  • Coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration
  • Where Enfuce acts as the licensed issuer it takes on regulatory risk and prices accordingly, so the convenience of skipping a sponsor bank is not free
  • European interchange caps limit programme revenue far below US levels, so business cases imported from a US card model do not survive the move
  • It is a smaller supplier than Marqeta or i2c, which means less negotiating room on scheme fees and a thinner partner ecosystem around it
  • Pricing is entirely quoted with monthly minimums, so low-volume programmes carry a fixed cost that does not scale down with a slow launch

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

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

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

Enfuce

On request
  • Enfuce issuing and processingOn request
    • Per-active-card and per-transaction fees with monthly minimums
    • Higher pricing where Enfuce acts as licensed issuer rather than processor only
    • Interchange arrangements depend on who holds the issuing licence

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

Which should you pick?

Choose Enfuce if

  • You need licensed issuing.
  • You work on Web, API.
  • You also want card processing.

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.

Questions people ask

Is Enfuce or Ona (formerly Gitpod) better?
Neither clearly leads. Enfuce starts at On request and Ona (formerly Gitpod) at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Enfuce or Ona (formerly Gitpod)?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at On request for Enfuce and Free for Ona (formerly Gitpod).
Does Enfuce or Ona (formerly Gitpod) run on more platforms?
Enfuce runs on Web, API. Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS.
Can I use Ona (formerly Gitpod) for free?
Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. Enfuce starts at On request.
What is Enfuce best used for?
Enfuce is most often used for a european fintech launching cards without spending two quarters finding a sponsor bank, a corporate issuing fuel or expense cards across several eu countries on one programme, a bank migrating an existing european card portfolio off a legacy processor, a programme that must report cardholder transaction carbon data to meet sustainability commitments. Of those, a european fintech launching cards without spending two quarters finding a sponsor bank and a corporate issuing fuel or expense cards across several eu countries on one programme are not what Ona (formerly Gitpod) is typically brought in for.
What can Enfuce do that Ona (formerly Gitpod) cannot?
Enfuce covers Licensed issuing, Card processing, Tokenisation, Spend controls. Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard.

Answered from the vendors’ own pages

Enfuce: Do I need my own licence to use Enfuce?

Not necessarily. Enfuce holds Finnish payment institution authorisation and can act as issuer, or process under your own licence if you have one.

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.

Enfuce: Which regions does it cover?

Europe. It is not a route to issuing cards in the United States or Asia.

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.

Enfuce: How does interchange work?

Who holds the issuing licence determines who receives interchange, so the licensing choice and the revenue model are the same decision.

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.

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