Guides · September 2026
Cloud development environment, defined
The definition, the decade that produced it, the bill that comes with it, and the version that runs on hardware you already own.
The definition.
A cloud development environment is a complete, working development setup — the source checkout, the toolchain, the dependencies, the services a project needs to run — that lives on a machine other than the one in front of you, is built from a definition rather than by hand, and is reached over the network from something thin: a browser tab, a local IDE in remote mode, or a terminal.
Each clause does work. Environment, not editor: an editor in a tab is a web IDE, and a CDE is the whole machine behind it. From a definition: a devcontainer.json, a Nix file, a Terraform template — something that rebuilds the same environment tomorrow, for a colleague, or after you deleted it in anger. Elsewhere: the device you type on holds no code, no credentials, and no state that matters, which is the property that lets you switch devices, onboard a stranger, or wipe a laptop without ceremony.
Where the category came from.
The idea is older than the name. AWS Cloud9 put an IDE in the browser, and AWS closed it to new customers on 25 July 2024. GitHub Codespaces made the modern shape mainstream: a devcontainer built per branch, reachable from VS Code or a browser, billed per core-hour after a free allowance. Gitpod grew the same shape into a company, then renamed itself Ona in September 2025 and repositioned around agents; in June 2026 OpenAI agreed to acquire it. Google’s Project IDX became Firebase Studio, and Firebase Studio is being shut down: no new workspaces since 22 June 2026, everything deleted on 22 March 2027.
The self-hosted line runs alongside. Coder is an AGPL-3.0 platform you run on your own infrastructure: workspaces defined in Terraform, connected through a WireGuard tunnel, shut down automatically when idle. DevPod is MPL-2.0 and client-only: it takes a devcontainer.json and stands it up on your laptop’s Docker, a machine over SSH, a cloud VM, or a Kubernetes cluster. Read the arc together and a pattern shows: several of the hosted products have closed, renamed, or turned into agent platforms, while the self-hosted tools kept doing the one job.
What they solve.
Reproducibility
The environment is a file in the repo. Two people on the same branch have the same toolchain to the version, and the ‘works on my machine’ conversation ends.
Onboarding
A new contributor clicks and is compiling before lunch, without a day of installs or a checklist that was true last year.
Big machines on demand
A 32-core box for the afternoon a build needs one, then gone. Codespaces sells exactly that, by the hour.
Nothing on the laptop
Code and credentials stay in the environment. Reviewing a stranger’s pull request stops being a risk to the device you bank on.
What they cost.
| The cost | What it looks like | The numbers |
|---|---|---|
| Metered hours | The environment bills while it runs, whether or not you are typing | Codespaces: $0.18 an hour for 2 cores up to $2.88 for 32, after 120 free core-hours a month on GitHub Free (180 on Pro) |
| Storage while stopped | The disk is billed with the machine off, and deleted if you stay away | Codespaces: $0.07 per GB-month; a stopped codespace is deleted after 30 days of inactivity by default |
| Idle timeouts | The machine stops when you stop touching it — which is precisely when an agent is doing the work | Codespaces: 30 minutes by default, 240 at most |
| Someone else’s environment | Your code runs on their VM, under their terms, for as long as they offer the product | Cloud9 closed to new customers in 2024; Firebase Studio shuts down in March 2027 |
| Operating one yourself | The self-hosted tools remove the meter and add a platform to run | Coder is a server you deploy and keep; DevPod still needs a backend to provision onto |
The self-hosted kind, and the plainest version of it.
Coder and DevPod are self-hosted CDEs in the full sense: they still provision, they just do it on machines you control. Underneath them is a plainer version that most working developers already own without calling it anything. The workstation under the desk, the Mac mini, the GPU box in the closet — each is already a complete environment, with the checkout, the toolchain, the credentials, and the disk that a hosted product would have to rebuild. ‘Cloud’ in that version means only ‘reached from anywhere’. Nothing is provisioned, nothing meters, nothing times out; the price is that the machine stays on and you can get to it.
Getting to it is the part that was hard. The classic answer is SSH plus tmux behind a port forward or a VPN, and it works if you keep the discipline. spawnd is that job built as a product: one daemon on each host you own, dialing out, so nothing listens and no port opens; sessions that live on the host, each PTY owned by a worker process, so a build or an agent run survives the closed tab, the dropped connection, and a daemon restart with scrollback intact; and any browser as the console, a phone included, with a new device approved once against a short code. Your browser talks to each daemon peer-to-peer, end-to-end encrypted, and the server that introduces them never sees session content. It provisions nothing and standardises nothing, which is the honest limit — if reproducibility is your problem, Codespaces or Coder solves it and this does not. If the problem is reaching machines that already exist, this is the self-hosted CDE with the provisioning removed.
Start
Your own machines, reached from anywhere.
curl -fsSL https://spawnd.dev/install.sh | shQuestions
- Is a cloud development environment the same as remote development?
- Remote development is the older, narrower thing: your IDE driving one machine over SSH. A CDE adds the definition — the environment is built from a file, so it can be rebuilt, duplicated, and thrown away.
- Are cloud development environments free?
- Some have a free allowance — Codespaces gives personal accounts 120 core-hours a month — and the self-hosted tools are open source, but you supply the machines. Your own hardware, reached through spawnd, is the version where the environment itself costs nothing new.
- Do coding agents need a CDE?
- They need an environment: a real checkout, a toolchain, and hours of uninterrupted runtime. Hosted agents rent one per task; agents on your own machines already have one. The background agents page covers that split.