Coder vs GitHub Codespaces: self-hosted or managed?
Both give developers a cloud development environment instead of a fragile local setup. The real fork is who runs it: Coder is self-hosted on your own infrastructure with Terraform-defined workspaces; Codespaces is fully managed by GitHub. Here's how they differ, and when neither is what you need.
Decide by who operates the control plane:
- Self-hosted, own infra, data residency → Coder: Terraform workspaces on your Kubernetes/VMs.
- Zero operations, GitHub-native → Codespaces: managed,
devcontainer.json, free monthly hours.
Side by side
Coder vs Codespaces, at a glance
| Dimension | Coder | GitHub Codespaces |
|---|---|---|
| Who hosts it | You (self-hosted) | GitHub (managed) |
| Workspace config | Terraform | devcontainer.json |
| Browser/desktop IDE | ✓ web + desktop + SSH | ✓ web + desktop |
| Free tier | Community (AGPL); infra on you | 120 core-hrs/mo (personal) |
| Paid model | Premium per user, not published | ~$0.18/hr compute + storage |
| Data residency | ✓ your network | ✗ GitHub cloud |
| Best for | Self-hosted workstations | Zero-ops managed CDE |
Compiled July 2026 from each vendor's official pages. Pricing changes often; verify current terms.
Official pages: Coder · Codespaces billing
Where Coder wins. When the environment must live on your own infrastructure, for data residency, network isolation, or because a platform team wants full control of what a workspace can reach, Coder is built for it. Workspaces are Terraform, so the same infrastructure-as-code discipline you use elsewhere defines dev environments, and everything runs inside your network. Its 2026 AI-governance features (AI Gateway, Agent Firewall) extend that control to AI coding agents.
Where Codespaces wins. If you'd rather not run anything, Codespaces is the lowest-friction path: it's managed by GitHub, uses the portable devcontainer.json standard, spins up from a repository in seconds, and bills per compute-hour with a free monthly allowance for personal accounts. For teams already living in GitHub with no appetite for operating a control plane, it's hard to beat on convenience.
If you only need preview environments. Both tools are places to write code. If the reason you are comparing CDEs is that you actually want disposable environments per pull request with a preview URL, that is a different job. The full list of Coder alternatives covers it: Okteto is the pick there for Kubernetes preview environments, self-hosted or cloud.
Common questions
Coder vs Codespaces: common questions
Is Coder cheaper than GitHub Codespaces?
It depends on scale and what you count. Coder's Community edition is free software, but you pay for the infrastructure it runs on and the team-time to operate it; Premium adds a per-user annual fee quoted by sales. Codespaces has no infrastructure to run and a free personal tier (120 core-hours/month), then metered compute from about $0.18/hour plus storage. Small teams often find Codespaces cheaper all-in; large orgs with existing infra and platform teams may find self-hosted Coder cheaper per seat.
Can GitHub Codespaces be self-hosted?
No. Codespaces is a fully managed service run by GitHub on Microsoft's cloud; you can't run its control plane on your own infrastructure. If self-hosting on your own Kubernetes or VMs is a requirement (for data residency or network isolation), Coder or Eclipse Che / OpenShift Dev Spaces are the options; Codespaces is not.
Do Coder and Codespaces use the same config format?
Not exactly. Codespaces is built around the open devcontainer.json standard. Coder defines workspaces with Terraform templates (which can themselves reference dev containers), giving platform teams more infrastructure control at the cost of a steeper authoring curve. devcontainer.json files are more portable across tools.