Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Orkes

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

Orkes

Automation Integration

Commercial Conductor, now the maintainer of the workflow engine Netflix archived

From
Free
Free plan
Yes

The short version

  • Orkes is free; Ona (formerly Gitpod) starts at $20/mo.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only Orkes lists JSON workflow definitions.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Ona (formerly Gitpod) and Orkes actually diverge.

Attributes where Ona (formerly Gitpod) and Orkes differ
AttributeOna (formerly Gitpod)Orkes
Pricing modelPer month by compute unitQuote
PlatformsWeb, Linux, macOS, Windows, AWSLinux, Self-hosted, Web
CategoryDeveloper ToolsAutomation Integration

Identical on both: starting price (Free), free tier (Yes).

What each one covers

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 Orkes

  • JSON workflow definitions
  • Polyglot workers
  • Visual workflow builder
  • AI and LLM tasks
  • Human tasks
  • Event handlers
  • RBAC and secrets
  • Hosted or self-hosted

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

Orkes

  • A microservices estate that needs orchestration across services written in different languages without a shared SDKnot Ona (formerly Gitpod)
  • A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot Ona (formerly Gitpod)
  • An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot Ona (formerly Gitpod)
  • A business process needing human approval steps interleaved with automated service callsnot Ona (formerly Gitpod)

Where each one falls 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

Orkes

  • Netflix archived the Conductor repository in December 2023 and Orkes took over maintenance, so the large-company backing that justified many original adoptions no longer exists
  • Enterprise pricing is entirely unpublished, and the only free option is explicitly a prototyping sandbox whose limits can change at any time, so there is no supported low-cost entry point
  • Self-hosting Conductor OSS in production means operating the engine plus its persistence and indexing dependencies, typically Postgres or Cassandra with Elasticsearch, which is a substantial platform commitment
  • JSON workflow definitions are language agnostic but verbose and awkward to test, and teams accustomed to defining workflows in code find them a step backwards in developer experience
  • Orkes is a small company whose commercial future is tied to a single open source project it also maintains, which concentrates both vendor and project risk in the same place

Pricing, plan by plan

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

Orkes

Free
  • Developer EditionFree
    • All Conductor OSS features plus enterprise capabilities
    • Sandbox for prototyping only
    • Rate limits and resources may change without notice
  • EnterpriseOn request
    • Availability SLA up to 99.99%
    • Orkes-hosted or customer-hosted deployment
    • Dedicated technical account manager

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

  • You need json workflow definitions.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web.
  • You also want polyglot workers.

Questions people ask

Is Ona (formerly Gitpod) or Orkes better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and Orkes at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ona (formerly Gitpod) or Orkes?
Ona (formerly Gitpod) starts at Free and Orkes at Free.
Does Ona (formerly Gitpod) or Orkes run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. Orkes runs on Linux, Self-hosted, Web.
Can I use Ona (formerly Gitpod) for free?
Both have a free tier, so you can try either at no cost before committing.
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 Orkes is typically brought in for.
What can Ona (formerly Gitpod) do that Orkes cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks.

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.

Orkes: Does Netflix still maintain Conductor?

No. Netflix archived its repository in December 2023. The open source project continues at conductor-oss under Apache 2.0, maintained by Orkes.

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.

Orkes: Is there a free production tier?

No. The Developer Edition is a sandbox that the vendor states is unsuitable for production. Self-hosting Conductor OSS is the free production route.

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.

Orkes: What does Enterprise cost?

Nothing is published; it is quoted by deployment and support requirements.

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.

Orkes: How does it compare with Temporal?

Conductor uses declarative JSON workflow definitions and external workers; Temporal defines workflows in code. Temporal has the larger community.

Share

Related pages

Other head to heads