Cloud · head to head
CapRover vs Ona (formerly Gitpod)

CapRover
Cloud
Free self-hosted platform built on Docker Swarm with a dashboard and automatic certificates
- From
- Free
- Free plan
- Yes

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
- Each has a real cost: CapRover since June 2026 one pseudonymous account wrote 97 of roughly 100 commits and the next human contributor wrote one, so there is no identifiable person or company to contract with, escalate to or hold responsible.; 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.
- They diverge on capability: CapRover covers One-click applications, Ona (formerly Gitpod) covers Ephemeral environments.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which CapRover and Ona (formerly Gitpod) actually diverge.
| Attribute | CapRover | Ona (formerly Gitpod) |
|---|---|---|
| Pricing model | Open source, no licence fee | Per month by compute unit |
| Platforms | Web, Linux, Docker, CLI, Self-hosted | Web, Linux, macOS, Windows, AWS, Google Cloud Platform |
| Category | Cloud | Developer Tools |
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).
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 CapRover
- One-click applications
- Automatic certificates
- Web dashboard
- Multiple deploy paths
- Docker Swarm clustering
- Custom nginx configuration
Only in Ona (formerly Gitpod)
- Ephemeral environments
- Agent sessions
- Bring your own cloud
- Devcontainer standard
- Compute unit budgeting
- Enterprise identity
What people use each for
The jobs each tool is most often brought in to do.
CapRover
- Running a personal server or homelab with several applications behind automatic certificatesnot Ona (formerly Gitpod)
- A two person team that wants a dashboard rather than a terminal for deployments on one boxnot Ona (formerly Gitpod)
- Standing up one-click databases and internal tools without writing Compose filesnot Ona (formerly Gitpod)
- Hosting client demos cheaply where downtime is inconvenient rather than expensivenot 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 CapRover
- Running several coding agents in parallel against real databases and services instead of on a laptopnot CapRover
- Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot CapRover
- Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot CapRover
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
CapRover
- Since June 2026 one pseudonymous account wrote 97 of roughly 100 commits and the next human contributor wrote one, so there is no identifiable person or company to contract with, escalate to or hold responsible.
- Donations over the last twelve months totalled 285 US dollars and there is no commercial tier, so no paid support exists at any price and no maintenance commitment is funded.
- The LICENSE file is Apache 2.0 with a superseding appendix that bans redistributing a paid version and refers to paid features that do not yet exist, and GitHub cannot classify it, so the terms already anticipate a commercial change of direction.
- Releases arrive in bursts with an eleven month gap between September 2023 and August 2024 and two further gaps of about six months since, so there is no basis for assuming a security fix will land promptly.
- The backup feature is documented as experimental, covers only the CapRover configuration directory and explicitly excludes persistent volumes and container images, so every database has to be dumped separately with its container stopped.
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.
Pricing, plan by plan
CapRover
Free- CapRoverFree
- No paid tier and no hosted offering
- Unlimited applications, servers and users
- Community support through Slack and GitHub
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
Which should you pick?
Choose CapRover if
- You need one-click applications.
- You want to start without paying.
- You work on Web, Linux, Docker, CLI, Self-hosted.
- You also want automatic certificates.
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.
Questions people ask
- Is CapRover or Ona (formerly Gitpod) better?
- Neither clearly leads. CapRover starts at Free and Ona (formerly Gitpod) at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, CapRover or Ona (formerly Gitpod)?
- CapRover starts at Free and Ona (formerly Gitpod) at Free.
- Does CapRover or Ona (formerly Gitpod) run on more platforms?
- CapRover runs on Web, Linux, Docker, CLI, Self-hosted. Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS, Google Cloud Platform.
- Can I use CapRover for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is CapRover best used for?
- CapRover is most often used for running a personal server or homelab with several applications behind automatic certificates, a two person team that wants a dashboard rather than a terminal for deployments on one box, standing up one-click databases and internal tools without writing compose files, hosting client demos cheaply where downtime is inconvenient rather than expensive. Of those, running a personal server or homelab with several applications behind automatic certificates and a two person team that wants a dashboard rather than a terminal for deployments on one box are not what Ona (formerly Gitpod) is typically brought in for.
- What can CapRover do that Ona (formerly Gitpod) cannot?
- CapRover covers One-click applications, Automatic certificates, Web dashboard, Multiple deploy paths. Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard.
Answered from the vendors’ own pages
CapRover: Does CapRover cost anything?
No. There is no paid tier and no hosted version. The only income is donations, which came to 285 US dollars over the last twelve months.
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.
CapRover: Is the licence really Apache 2.0?
Not quite. The LICENSE file is Apache 2.0 plus an appendix that supersedes it in case of conflict, forbidding modification of paid features and redistribution of a paid version. GitHub does not recognise the result as a standard licence.
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.
CapRover: Does the backup feature protect my databases?
No. It backs up the CapRover configuration directory only and explicitly excludes persistent directories and container images. You have to dump each database yourself with the container stopped.
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.
CapRover: Can I move off Docker Swarm later?
Not without rebuilding. CapRover is architecturally tied to Swarm, so outgrowing it means migrating applications to a different platform rather than switching a scheduler.
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.
Related pages
More on Ona (formerly Gitpod)
Other head to heads
- CapRover vs Render
- CapRover vs K3s
- CapRover vs DigitalOcean
- CapRover vs Coolify
- CapRover vs Dokku
- CapRover vs Qovery
- CapRover vs Porter
- CapRover vs Railway
- CapRover vs Fly.io
- CapRover vs Northflank
- CapRover vs SST
- CapRover vs Heroku
- CapRover vs Jaeger
- CapRover vs Lambda
- CapRover vs Linode
- CapRover vs Longhorn
- CapRover vs minikube
- CapRover vs Coder
- CapRover vs CodeSandbox
- CapRover vs StackBlitz
- CapRover vs Namespace
- CapRover vs Daytona
- CapRover vs Earthly
- CapRover vs Nixpacks
- CapRover vs Spacelift
- CapRover vs Atlantis
- CapRover vs Backstage
- CapRover vs Cloud Native Buildpacks
- CapRover vs ConfigCat
- CapRover vs Xlinesoft
- CapRover vs GNU Emacs
- CapRover vs Keil MDK
- CapRover vs Vite
- CapRover vs Bazel
- Ona (formerly Gitpod) vs Render
- Ona (formerly Gitpod) vs K3s
- Ona (formerly Gitpod) vs DigitalOcean
- Ona (formerly Gitpod) vs Coolify
- Ona (formerly Gitpod) vs Dokku
- Ona (formerly Gitpod) vs Qovery
- Ona (formerly Gitpod) vs Porter
- Ona (formerly Gitpod) vs Railway
- Ona (formerly Gitpod) vs Fly.io
- Ona (formerly Gitpod) vs Northflank
- Ona (formerly Gitpod) vs SST
- Ona (formerly Gitpod) vs Heroku
- Ona (formerly Gitpod) vs Jaeger
- Ona (formerly Gitpod) vs Lambda
- Ona (formerly Gitpod) vs Linode
- Ona (formerly Gitpod) vs Longhorn
- Ona (formerly Gitpod) vs minikube
- 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 Xlinesoft
- Ona (formerly Gitpod) vs GNU Emacs
- Ona (formerly Gitpod) vs Keil MDK
- Ona (formerly Gitpod) vs Vite
- Ona (formerly Gitpod) vs Bazel
