GitHub Codespaces

Cloud development environments that open in the browser or desktop VS Code

AI Coding & DevelopmentFree planOverseas★★★★☆ 4.0

Visit GitHub Codespaces official site ↗ View similar tools Compare alternatives →

What is GitHub Codespaces?

GitHub Codespaces provides full development environments running in the cloud, configured from a repository's devcontainer file so every developer gets the same toolchain, extensions and settings from the first minute. You can work in the browser editor, attach desktop VS Code, or connect over SSH, and usage is billed by compute hours plus storage while the environment exists. Because the setup lives in the repository, onboarding a contributor or reproducing a bug that only appears in CI stops being a day of environment archaeology. It is a GitHub feature rather than a standalone product, which is both its convenience and its main limitation.

Last updated: 2026-09-20. This site only provides an index; for exact features, pricing, and licensing, see the official website.

Key features

Cloud development environments created from a repository in seconds
Devcontainer configuration so toolchains live in version control
Browser editor plus desktop VS Code and SSH access
Machine sizes from small instances up to GPU-class for heavy builds
Free monthly core hours and storage on personal accounts
Port forwarding and prebuilds that shorten the first startup

Pros & cons

Strengths

Reproducible environments remove setup drift across a team
Onboarding a new developer takes minutes rather than days
Prebuilds make large monorepos practical to open in a browser

Watch out for

Compute-hour billing is easy to forget about while idle
Tied to GitHub, so other code hosts need a different answer
Very heavy builds can still feel constrained by the instance

Best for & use cases

onboarding, consistent dev environments, monorepos, remote teams and contributor sandboxes

If you're comparing similar products, check the alternatives below, or browse all tools in the AI Coding & Development category.

FAQ

What happens when I stop working?

The environment keeps its state but continues to consume storage, and compute stops after a timeout period. Setting a short idle timeout and deleting environments you no longer need avoids quiet costs.

Can I keep using my own editor?

Yes. You can open a codespace in the browser, attach desktop VS Code, or connect over SSH with whichever local editor you prefer, so the environment is portable even when the tooling is standardised.

Is it useful outside GitHub?

Not directly. Codespaces is part of GitHub, so teams on GitLab, Bitbucket or a self-hosted forge need a separate cloud development environment product instead.