starter.wikiSearch⌘K

Managed cloud development environments

GitHub Codespaces

GitHub-managed cloud development environments connected to repositories, dev containers, identity, and policy.

Visit official site

Editorial verdict

Choose Codespaces when GitHub-native managed workspaces materially reduce onboarding and local-machine constraints, and the organization can govern compute and storage use.12

Best for

  • GitHub repositories with documented development setup
  • Teams needing browser or editor access to managed compute
  • Organizations able to enforce machine, timeout, retention, and access policy
12

Not ideal for

  • Provider-neutral workspace requirements
  • Teams with strict non-GitHub control-plane constraints
  • Organizations without cost and lifecycle governance
12
Main trade-off

Managed workspaces reduce host setup and fleet operations while adding GitHub dependence, metered compute and storage, lifecycle policy, and regional constraints.12

Product boundary

Whether GitHub-managed workspaces are worth their compute, storage, lifecycle, and platform coupling.

Codespaces provides managed development compute and editor access; it does not remove repository setup, environment security, cost policy, or application infrastructure decisions.12

For: GitHub-centered teams needing repeatable cloud workspaces with minimal platform operations

  • GitHub cannot be the workspace control plane.
  • Compute or storage usage is materially more expensive than managed alternatives.
  • Self-hosted networking and policy are mandatory.

Why teams consider GitHub Codespaces

  • Managed computeGitHub provisions and operates development workspace compute.12
  • Repository integrationWorkspaces are created in direct repository context.12
  • Dev container supportRepositories can reuse dev container configuration for environment setup.12

Pricing

Codespaces meters compute by machine size and active time and storage by retained usage, subject to account-plan allowances and organization policy.2

Cloud workspace

Account allowance plus metered usage

Model machine size, active hours, stopped retention, storage, prebuilds, timeout, and organization ownership.2

Primary meters
Compute time by machine type and retained storage2
Lifecycle lever
Timeout and retention policy directly affect usage2
Pricing checked View official pricing

GitHub Codespaces vs alternatives

VS Code Dev Containers

Choose when
Repository-owned portable configuration solves the need.
Avoid when
Managed cloud capacity is mandatory.
Compared with GitHub Codespaces
The team owns the host and runtime instead of paying for managed workspaces.45

Ona

Choose when
Human and agent environments, automation, and broader policy are the decision.
Avoid when
GitHub-native developer workspaces are sufficient.
Compared with GitHub Codespaces
A broader platform and OCU model replace Codespaces' repository-native path.67

Coder

Choose when
Self-hosted workspace infrastructure and organizational control are mandatory.
Avoid when
The team does not want platform operations.
Compared with GitHub Codespaces
Control increases alongside availability and security responsibility.89

Resources and sources

Official product, policy, pricing, and maintenance

  • GitHub Codespaces overview
    Open
  • Billing for GitHub Codespaces
    Open
  • Codespaces timeout policy
    Open
  1. 1
    GitHub Codespaces overview

    GitHub · Accessed Official

  2. 2
    Billing for GitHub Codespaces

    GitHub · Accessed Official

  3. 3
    Codespaces timeout policy

    GitHub · Accessed Official

  4. 4
    Development Containers specification

    Dev Container Specification · Accessed Official

  5. 5
    Developing inside a container

    Microsoft · Accessed Official

  6. 6
    Ona development environments

    Ona · Accessed Official

  7. 7
    Ona pricing

    Ona · Accessed Official

  8. 8
    Coder documentation

    Coder · Accessed Official

  9. 9
    Coder pricing

    Coder · Accessed Official