A hosted cloud dev environment tied to your Git provider is the quickest Gitpod replacement, and a self-hosted platform on your own cloud or Kubernetes cluster is the right one when code can't leave your infrastructure. Gitpod now trades as Ona and leads with background agents, which is why teams that only wanted workspaces are looking again.
A new developer joins on a Monday, clicks the badge in the readme that used to open a ready workspace, and lands on a homepage about running background agents in the cloud. The company behind the badge has moved its pitch from dev environments to agents. If what your team wanted was a ready-to-code environment from a repo, you need something else.
What your team needs from a Gitpod replacement
- Where the workspace runs: a vendor's cloud, your own cloud account, or a Kubernetes cluster your platform team already operates.
- Which editor your developers open: a browser IDE, VS Code connected to a remote machine, or a JetBrains IDE with a local thin client.
- Whether a workspace starts straight from a Git repository or branch, with no manual setup for the person clicking.
- How much of your existing workspace configuration carries over, and who will rewrite and test it for every repo that doesn't.
- How the bill is built: per compute hour, per vCPU, per user, or nothing beyond your own cloud costs for an open-source tool.
- Who keeps it running and patched: the vendor, your platform team, or each developer on their own laptop.
- How secrets, network access and audit trails work, since that's the reason security-sensitive teams choose managed workstations at all.
- Whether the vendor is still investing in workspaces, because products in this space do close: Codeanywhere switched its service off at the start of July.
Managed workspaces someone else runs
GitHub Codespaces
Cloud development environments native to GitHub and launched from the repository, the shortest hop for teams whose code already lives there.
Google Cloud Workstations
Managed development environments on Google Cloud aimed at security-sensitive teams, reachable from a browser or a local IDE.
JetBrains Remote Development
For JetBrains IDE users: the IDE backend runs on a remote machine while a local thin client keeps the editor feeling local.
Self-hosted and open-source routes
Coder
Self-hosted cloud development environments for developers and their agents, with an open-source Community edition to start on.
DevPod
Open-source and client-only, it builds repeatable workspaces on whatever infrastructure you point it at, with any IDE you like.
Eclipse Che
Kubernetes teams can run this open-source workspace server, which hosts the IDE in the cluster and starts each workspace from a Git repository.
Devbox
A command-line tool for isolated, reproducible environments on any machine, with no Docker or Nix knowledge needed.
Eclipse Theia
Open-source IDE that runs in the cloud or on the desktop, built on the Theia Platform and available to try online.
code-server
VS Code in the browser, served from a machine you host yourself; the plainest self-run swap for a browser IDE.
Okteto
On-demand Kubernetes environments for each developer, coding agent and pull request, run on a Kubernetes cluster you own, from a cloud account to bare metal.
Managed, self-hosted or client-only
A managed service means a vendor runs the machines, patches them and bills you for usage; your developers click and code. A self-hosted platform such as Coder or Eclipse Che runs on your own infrastructure or Kubernetes cluster, so your code and data never leave it, but someone on your side owns upgrades, capacity and the odd outage at a bad moment.
Client-only tools sit between the two. They put the orchestration on the developer's machine and create the workspace on whatever cloud or server you choose. DevPod works this way, with no server-side setup and no vendor lock-in. It's a strong fit for a small team that wants Gitpod-style repeatability without adopting a new platform, and a weaker fit for a company that needs central control over who can spin up what.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Self-hosting looks free on a licence line and isn't free in staff time. If nobody wants to own a Kubernetes-based workspace server, a managed service is the cheaper choice even when its bill is higher.
Browser IDE or your own editor, connected remotely
Gitpod put the editor in a browser tab, and the alternatives split on whether they do the same. Some give you a browser IDE first and a desktop connection second. Others assume you'll keep your local editor and simply connect it to a remote machine, which keeps your shortcuts, extensions and muscle memory intact. JetBrains users in particular should check this early: a remote backend with a local thin client feels very different from a browser editor, and it's the thing your developers will complain about first if you get it wrong.
If all you want is VS Code in a browser on a server you control, you don't need a platform at all; a self-run browser editor does that one job and nothing else. That's a perfectly sensible answer for a solo developer or a small team on a single shared box.
A trial with your slowest repo
Pick the repository that takes longest to set up on a new laptop. Time three things on each finalist: from click to a running workspace, from workspace to passing tests, and from a closed laptop lid back to where you left off. Then make a change to the environment definition and see how long a rebuild takes. A tool that's fast on a hello-world repo and slow on your real one will cost you every day.
Ask a developer who wasn't part of the choice to do the same trial without help. Whatever confuses them will confuse every new starter, and onboarding is where a workspace tool earns its keep.
What drives the bill
Managed environments charge for compute time, and the meter runs while a workspace is up, so auto-stop settings matter more than the headline rate. Some add layers on top: Google Cloud Workstations, for example, lists a control plane fee per hour and a per-vCPU management fee on top of the compute itself. Read the pricing page with a calculator open and model a normal week for one developer, idle time included.
Open-source and self-hosted tools move the cost rather than remove it. You pay your cloud provider for the machines and your own people for the upkeep; a free community edition, where one exists, carries no licence bill, so staff time is the line that grows. Check what a paid edition adds over the free one, and price the edition you'll be on in a year, not the one you start with.
Do you make cloud development environments or remote dev tools? Tool makers can ask to be considered for a featured place on this list.
Matching the tool to how your team works
A small team on GitHub that wants zero setup should start with a hosted environment native to its Git provider. A regulated or security-sensitive company should look at managed workstations inside its own cloud account, or a self-hosted platform on its own cluster if there's a platform team to run it. A team that wants repeatable workspaces without adopting a platform should try a client-only open-source tool first. And if what you really liked about Gitpod was the browser IDE, a self-run browser editor may be all you need.
If your interest has shifted to the agent side of things, the E2B alternatives cover sandboxes built for AI agents. For browser-first coding environments, see the CodeSandbox alternatives.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


