Softwr

APIs · head to head

Episode Six vs Ona (formerly Gitpod)

Episode Six logo

Episode Six

APIs

Payment processing and ledger platform deployable on premise or in your own cloud

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; Episode Six prices on request.
  • Only Episode Six lists tritium API platform; only Ona (formerly Gitpod) lists ephemeral environments.
  • Prices and features on this page were last checked on 20 November 2026.

How do Episode Six and Ona (formerly Gitpod) differ?

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

Attributes where Episode Six and Ona (formerly Gitpod) differ
AttributeEpisode SixOna (formerly Gitpod)
Starting priceOn requestFree
Pricing modelQuotePer month by compute unit
Free tierNoYes
PlatformsWeb, API, Self-hostedWeb, Linux, macOS, Windows, AWS
CategoryAPIsDeveloper Tools

Which features does each one have?

They share no listed features; 8 appear only for Episode Six 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 Episode Six

  • Tritium API platform
  • Flexible deployment
  • Multi product issuing
  • Digital wallets
  • Multi currency ledger
  • Network connectivity
  • Configurable product engine
  • Institutional controls

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?

Episode Six is most often brought in for A telco or airline launching a branded wallet and card product at national scale. The jobs each tool is most often brought in to do.

Episode Six

  • A bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloudnot Ona (formerly Gitpod)
  • A large institution replacing a legacy card processor without moving off its own infrastructurenot Ona (formerly Gitpod)
  • A telco or airline launching a branded wallet and card product at national scalenot Ona (formerly Gitpod)
  • A bank running prepaid, debit and credit products that wants them on one ledger rather than three processorsnot 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 Episode Six
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot Episode Six
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Episode Six
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Episode Six

Where do Episode Six and Ona (formerly Gitpod) fall short?

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

Episode Six

  • Deployment on premise or in a private tenancy means the institution carries infrastructure, upgrade and PCI scope work that a hosted processor would absorb
  • Implementation runs to quarters and involves core banking, network certification and fraud system integration, so time to first card is far longer than with a self serve issuer processor
  • Pricing is entirely bespoke and weighted to large programmes, which prices out fintechs and small issuers who would be better served by a hosted platform
  • Being smaller than the incumbent processors, its network certifications and operational presence vary by region, so a global rollout can find gaps in specific markets
  • The flexibility of six hundred APIs and a configurable product engine shifts design responsibility onto the buyer, and institutions without strong internal payments architects end up dependent on professional services

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 Episode Six and Ona (formerly Gitpod) cost?

Episode Six 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.

Episode Six

On request
  • Tritium platformOn request
    • Licence and implementation quoted per institution
    • Deployment model affects cost materially: on premise, private cloud or hosted
    • Processing fees typically per transaction or per active card

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 Episode Six if

  • You need tritium api platform.
  • You work on Web, API, Self-hosted.
  • You also want flexible deployment.

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 Episode Six or Ona (formerly Gitpod) better?
Neither clearly leads. Episode Six 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, Episode Six or Ona (formerly Gitpod)?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at On request for Episode Six and Free for Ona (formerly Gitpod).
Does Episode Six or Ona (formerly Gitpod) run on more platforms?
Episode Six runs on Web, API, Self-hosted. 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. Episode Six starts at On request.
What is Episode Six best used for?
Episode Six is most often used for a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud, a large institution replacing a legacy card processor without moving off its own infrastructure, a telco or airline launching a branded wallet and card product at national scale, a bank running prepaid, debit and credit products that wants them on one ledger rather than three processors. Of those, a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud and a large institution replacing a legacy card processor without moving off its own infrastructure are not what Ona (formerly Gitpod) is typically brought in for.
What can Episode Six do that Ona (formerly Gitpod) cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard.

Answered from the vendors’ own pages

Episode Six: Can Episode Six run inside our own data centre?

Yes. On premise and private cloud deployment is the main reason banks choose it over hosted only processors.

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.

Episode Six: Is it suitable for a startup issuing its first cards?

Not really. The licence, implementation timeline and cost are aimed at banks and large institutions.

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.

Episode Six: Do we still need a card licence or sponsor?

Yes. Episode Six is a processor. Network membership, licensing or a sponsor arrangement remains your responsibility.

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