Developer Workflow
Development Environments
Choose a reproducible contributor workspace by execution location, configuration ownership, onboarding, and enterprise control.
Recommendation
Choose where the contributor workspace should run.
Three workspace operating models
A container definition, managed workspace service, and self-hosted workspace control plane transfer different responsibilities.
Development environment routes
Keep cloud-service emulators and production runtimes out of the peer solution set.
The team wants a portable repository-defined environment
Start with VS Code Dev Containers.
Dev Containers is the open configuration route when the repository should define a containerized toolchain usable on local or compatible remote container hosts.
Verify: The team still owns container runtime, image supply chain, host resources, networking, secrets, performance, and editor compatibility.1
GitHub-hosted source should open in a managed cloud workspace
Evaluate GitHub Codespaces.
Codespaces is the GitHub-native managed route when repository, identity, dev-container configuration, compute, and lifecycle should share GitHub.
Verify: Model machine sizes, prebuilds, storage, idle and retention policy, network access, secrets, billing, and provider concentration.2
Humans and coding agents need managed isolated cloud environments
Evaluate Ona.
Ona is the current managed cloud-environment route when teams want isolated workspaces for developers and agents around repository-defined automation.
Verify: Treat Gitpod Classic only as migration context; verify the current Ona environment, OCU, storage, integration, security, and lifecycle model.3
The organization must host workspaces on controlled infrastructure
Evaluate Coder.
Coder is the self-hosted enterprise route when templates should provision remote workspaces on infrastructure controlled by the organization.
Verify: The organization owns deployment, identity integration, Terraform templates, compute, network, images, upgrades, observability, and workspace reliability.4
Boundary: Local Cloud Emulation reproduces selected cloud APIs and behavior; Preview Environments are remote deployed review instances; production Container Platforms run application workloads.
Differences that change the choice
Compare only the boundaries that materially alter adoption and ongoing ownership.
- Execution
- Local container hosts, vendor-managed compute, and self-hosted workspaces shift latency and operations differently.12
- Configuration
- Open dev-container definitions and platform templates have different portability and provisioning scope.12
Official resources
Verify current product boundaries, control-plane behavior, execution limits, pricing, licensing, and operating requirements in first-party material before adoption.
Sources
Official product material supports the bounded routes and verification points; route selection remains an editorial judgment.
- 1VS Code Dev Containers documentation
Microsoft · Accessed Official
- 2GitHub Codespaces overview
GitHub · Accessed Official
- 3Ona environments overview
Ona · Accessed Official
- 4Coder workspace templates
Coder · Accessed Official
- 5GitHub Codespaces billing
GitHub · Accessed Official
- 6Ona pricing
Ona · Accessed Official
- 7Coder pricing
Coder · Accessed Official