Cloud development environments (CDEs) are no longer exotic. The two main players — Gitpod and GitHub Codespaces — solve the same problem: give a developer a ready environment with one click. But under the hood they are built differently, and the choice affects everything — from price to security.
Architecture and launch model
Gitpod is built around its own workspace orchestrator. The environment is described in .gitpod.yml or a standard devcontainer.json, and containers run in Gitpod’s isolated infrastructure (or self-hosted on your Kubernetes). The key idea is prebuilds: the environment is built in advance on every push, so a new workspace spins up in seconds.
GitHub Codespaces is deeply embedded in GitHub. The environment is a container based on devcontainer.json, running in Microsoft’s Azure infrastructure. Everything lives right in the repository: open any PR — and in half a minute you have an environment with the branch’s code.
Integrations and DX
Codespaces wins thanks to seamless GitHub integration: ports, secrets, prebuilds, Actions — all in one place. If the team already lives in GitHub, the entry barrier is minimal.
Gitpod is stronger in independence: it works with GitLab, Bitbucket and self-hosted Git, and you can choose the editor — VS Code, JetBrains (via Gateway) or the browser. This is critical for companies that don’t want to be locked into Microsoft’s ecosystem.
Pricing
Codespaces is included in GitHub Pro/Team ($4/month and up) and gives 120 core-hours + 15 GB of storage for free. Extra hours are billed on usage.
Gitpod gives 50 hours per month free on the free plan, then from $9/month per developer. The self-hosted version of Gitpod is available on enterprise plans.
Security
Gitpod wins for teams with strict requirements: the self-hosted option gives full control over infrastructure and data. Codespaces only runs in Microsoft’s cloud (with the option to connect to private networks via Azure).
What to choose
- GitHub teams that need simplicity and minimal setup → Codespaces;
- Multi-Git / self-hosted / JetBrains → Gitpod;
- Strict security and data requirements → Gitpod (self-hosted).
Both products are mature. The decision ultimately comes down to how tied you are to the GitHub ecosystem and whether you need control over infrastructure.