Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Swan

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

Swan

APIs

European banking-as-a-service platform for embedding accounts, cards and payments into other products

From
€2990/month
Free plan
No

The short version

  • Ona (formerly Gitpod) has a free plan, then $20/mo; Swan starts at €2990/mo.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only Swan lists embedded business accounts.
  • Prices and features on this page were last checked on 20 November 2026.

How do Ona (formerly Gitpod) and Swan differ?

Ona (formerly Gitpod) and Swan differ on starting price (Free against €2990/month), pricing model and free tier (Yes against No). Only the attributes on which Ona (formerly Gitpod) and Swan actually diverge.

Attributes where Ona (formerly Gitpod) and Swan differ
AttributeOna (formerly Gitpod)Swan
Starting priceFree€2990/month
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 Swan. 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 Swan

  • Embedded business accounts
  • Card issuing
  • SEPA payments
  • Local account localisation
  • ACPR regulation
  • Usage-based pricing

What is each one used for?

Swan is most often brought in for A company wanting SEPA payment initiation embedded directly into its own product. 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 Swan
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot Swan
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Swan
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Swan

Swan

  • A vertical SaaS platform wanting to embed business bank accounts under its own brandnot Ona (formerly Gitpod)
  • A marketplace wanting to issue cards to sellers or partners without becoming a licensed banknot Ona (formerly Gitpod)
  • A company wanting SEPA payment initiation embedded directly into its own productnot Ona (formerly Gitpod)
  • A European fintech wanting to avoid a six-figure setup fee and long lock-in typical of legacy banking-as-a-service dealsnot Ona (formerly Gitpod)

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

Swan

  • Its regulatory base and strongest local account coverage are French and European, so companies needing US, UK-post-Brexit-specific, or broader global banking-as-a-service need an additional provider
  • Pricing is described only philosophically (usage-based, no big setup fee) rather than published as an actual rate card, so a company still needs a sales conversation to get real numbers
  • Embedding banking features into a product is a substantial compliance and design undertaking regardless of the vendor, and Swan handling the licence does not remove a platform's own KYC, AML and customer support obligations for the accounts it offers
  • As a comparatively young, single-country-licensed e-money institution, its balance sheet and regulatory standing carry more concentration risk than a banking-as-a-service offering backed by an established, multi-jurisdiction bank
  • Local account depth is explicitly limited to France, Germany and Spain, so a platform needing native local accounts in other European countries may find coverage thinner than expected

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

Ona (formerly Gitpod) has a free plan, with paid plans from $20/mo; Swan starts at €2990/mo. 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

Swan

€2990/month
  • SwanOn request
    • Usage-based pricing, no published rate card
    • No long-term contract or large setup fee required
    • Custom quote based on current, not forecast, usage
  • SandboxFree
  • Swan on demand€2,990/mo
  • Swan EnterpriseOn request

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

  • You need embedded business accounts.
  • You work on Web, API.
  • You also want card issuing.

Questions people ask

Is Ona (formerly Gitpod) or Swan better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and Swan at €2990/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ona (formerly Gitpod) or Swan?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and €2990/month for Swan.
Does Ona (formerly Gitpod) or Swan run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. Swan 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. Swan starts at €2990/month.
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 Swan is typically brought in for.
What can Ona (formerly Gitpod) do that Swan cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Swan covers Embedded business accounts, Card issuing, SEPA payments, Local account localisation.

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.

Swan: Which countries does Swan offer local accounts in?

France, Germany and Spain specifically, alongside broader SEPA payment coverage.

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.

Swan: Is pricing published?

No, Swan describes a usage-based, no-large-setup-fee philosophy but requires a quote for actual numbers.

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.

Swan: Who regulates Swan?

France's ACPR (Autorite de Controle Prudentiel et de Resolution), as a licensed e-money institution.

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