Developer Tools · head to head
Ona (formerly Gitpod) vs Restate

Ona (formerly Gitpod)
Developer Tools
Cloud development environments repositioned as a control plane for software engineering agents
- From
- Free
- Rated
- -

Restate
Developer Tools
Durable execution engine in Rust with a free tier and low-latency workflows
- From
- Free
- Rated
- -
The short version
- Each has a real cost: 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.; Restate the runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone.
- They diverge on capability: Ona (formerly Gitpod) covers Ephemeral environments, Restate covers Durable execution.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Ona (formerly Gitpod) and Restate actually diverge.
| Attribute | Ona (formerly Gitpod) | Restate |
|---|---|---|
| Pricing model | Per month by compute unit | Per month by durable action count |
| Platforms | Web, Linux, macOS, Windows, AWS, Google Cloud Platform | Linux, macOS, Web |
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Developer Tools).
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 Restate
- Durable execution
- Virtual objects
- Single binary runtime
- Multi-language SDKs
- Workflows and sagas
- Restate Cloud
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 Restate
- Running several coding agents in parallel against real databases and services instead of on a laptopnot Restate
- Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Restate
- Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Restate
Restate
- Payment or order flows where a crash between two external API calls must not double-charge or lose the ordernot Ona (formerly Gitpod)
- AI agent loops that call tools over minutes or hours and must survive a deployment mid-runnot Ona (formerly Gitpod)
- Replacing hand-rolled retry, idempotency key and outbox code across a set of microservicesnot Ona (formerly Gitpod)
- A small team that wants durable workflows without operating a Temporal cluster and its databasenot 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.
Restate
- The runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone.
- Restate Cloud jumps from a free fifty thousand actions straight to 300 US dollars a month for twenty million, so a workload sitting at a few hundred thousand actions pays enterprise-shaped money for hobby-shaped volume.
- It is a young project against Temporal’s established base, so hiring engineers who already know it is unrealistic and the answer to most questions is in the docs rather than on Stack Overflow.
- The programming model requires structuring code around durable handlers and virtual objects, which is a genuine rewrite for existing services rather than a library you add.
- The single-binary simplicity that makes small deployments cheap also means fewer operational knobs at very large scale than a system designed as separable components.
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/month
- 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
- Enterprise$undefined/year
- Single-tenant deployment in your own AWS or GCP account
- SAML and OIDC single sign-on
- Dedicated account management and forward deployed engineers
Restate
Free- FreeFree
- Fifty thousand durable actions per month
- No credit card required
- Community support
- Starter$300/month
- Twenty million actions per month
- Two hundred actions per second, bursting to one thousand
- Twenty GB storage
- Pro$1000/month
- Fifty million actions per month
- Five hundred actions per second, bursting to two thousand
- Fifty GB storage
- Enterprise$undefined/year
- Negotiated volume
- Twenty-four seven P0 support
- 99.99 per cent SLA
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, Google Cloud Platform.
- You also want agent sessions.
Choose Restate if
- You need durable execution.
- You want to start without paying.
- You work on Linux, macOS, Web.
- You also want virtual objects.
Questions people ask
- Is Ona (formerly Gitpod) or Restate better?
- Neither clearly leads. Ona (formerly Gitpod) starts at Free and Restate at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Ona (formerly Gitpod) or Restate?
- Ona (formerly Gitpod) starts at Free and Restate at Free.
- Does Ona (formerly Gitpod) or Restate run on more platforms?
- Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS, Google Cloud Platform. Restate runs on Linux, macOS, 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 Restate is typically brought in for.
- What can Ona (formerly Gitpod) do that Restate cannot?
- Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Restate covers Durable execution, Virtual objects, Single binary runtime, Multi-language SDKs.
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.
Restate: Is Restate open source?
The SDKs are MIT. The runtime is under a Business Source Licence, which permits self-hosting but not offering it as a competing service.
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.
Restate: How does it compare with Temporal?
Same problem, different shape: one Rust binary with embedded storage instead of a server plus database plus workers, and lower per-step latency.
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.
Restate: Is there a free tier?
Yes, fifty thousand durable actions a month on Restate Cloud with no card required.
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.
Restate: Which languages are supported?
TypeScript, Java, Kotlin, Go, Python and Rust.
Related pages
More on Ona (formerly Gitpod)
Other head to heads
- Ona (formerly Gitpod) vs Coder
- Ona (formerly Gitpod) vs CodeSandbox
- Ona (formerly Gitpod) vs StackBlitz
- Ona (formerly Gitpod) vs Namespace
- Ona (formerly Gitpod) vs Daytona
- Ona (formerly Gitpod) vs Earthly
- Ona (formerly Gitpod) vs Nixpacks
- Ona (formerly Gitpod) vs Spacelift
- Ona (formerly Gitpod) vs Atlantis
- Ona (formerly Gitpod) vs Backstage
- Ona (formerly Gitpod) vs Cloud Native Buildpacks
- Ona (formerly Gitpod) vs ConfigCat
- Ona (formerly Gitpod) vs Keil MDK
- Ona (formerly Gitpod) vs Vite
- Ona (formerly Gitpod) vs Bazel
- Ona (formerly Gitpod) vs Depot
- Ona (formerly Gitpod) vs Helix
- Ona (formerly Gitpod) vs Rust
- Ona (formerly Gitpod) vs Jitsu
- Ona (formerly Gitpod) vs Okteto
- Ona (formerly Gitpod) vs Argo CD
- Ona (formerly Gitpod) vs Steampipe
- Ona (formerly Gitpod) vs Deno
- Ona (formerly Gitpod) vs Visual Studio Code
- Ona (formerly Gitpod) vs Turborepo
- Ona (formerly Gitpod) vs Keycloak
- Ona (formerly Gitpod) vs Prettier
- Ona (formerly Gitpod) vs Tilt
- Ona (formerly Gitpod) vs WarpBuild
- Ona (formerly Gitpod) vs Webpack
- Restate vs Coder
- Restate vs CodeSandbox
- Restate vs StackBlitz
- Restate vs Namespace
- Restate vs Daytona
- Restate vs Earthly
- Restate vs Nixpacks
- Restate vs Spacelift
- Restate vs Atlantis
- Restate vs Backstage
- Restate vs Cloud Native Buildpacks
- Restate vs ConfigCat
- Restate vs Keil MDK
- Restate vs Vite
- Restate vs Bazel
- Restate vs Depot
- Restate vs Helix
- Restate vs Rust
- Restate vs Jitsu
- Restate vs Okteto
- Restate vs Argo CD
- Restate vs Steampipe
- Restate vs Deno
- Restate vs Visual Studio Code
- Restate vs Turborepo
- Restate vs Keycloak
- Restate vs Prettier
- Restate vs Tilt
- Restate vs WarpBuild
- Restate vs Webpack
