Tool profile
GitHub Codespaces: cost, fit and limits
GitHub Codespaces is a cloud development environment made by GitHub, Inc. that starts a ready-to-code machine from a GitHub repository and opens it in a browser or a local editor, billed by core hours with a monthly free allowance for personal accounts.
What to know first
GitHub Codespaces gives every personal account a monthly allowance of 120 core hours, or 60 hours on a 2-core machine, plus 15 GB of storage. Past that, usage is pay-as-you-go, and organizations can switch it on for private and internal repositories. The feature page prints no overage rates, and it describes no AI inside the codespace; GitHub Copilot appears as a separate product in the same navigation.
GitHub Codespaces at a glance
| Maker | GitHub, Inc., Not stated on the vendor pages |
|---|---|
| Free plan | Yes |
| Entry price | Free: 120 core hours a month on a personal account |
| API access | No |
| Category | Best AI Cloud IDE Software in 2026, rank 1 of 12 |
| Website | github.com/features/codespaces |
Who GitHub Codespaces is best for
Open-source maintainers
Contributors can open a codespace from a repository and start on an issue the same day, without installing toolchains, and the free allowance covers light use.
Organizations standardizing onboarding
Admins can enable and pay for usage, so new hires get a working environment for private repos without a laptop setup guide.
Developers who switch devices
The page says you can code from any device, including a browser on an iPad, which suits travel or a borrowed machine.
GitHub Codespaces plans and pricing
| Plan | Price | What it includes |
|---|---|---|
| Personal free allowance | Free each month | 120 core hours or 60 hours of run time on a 2-core codespace, plus 15 GB of storage, per personal account. |
| Pay-as-you-go | Rates not published on the page | Usage above the free quota. Organizations can enable it for private and internal repositories and pay for what members use. |
| Enterprise or organization | Contact sales | Organization billing and policies handled through GitHub sales; the feature page does not print a figure. |
Checked November 2026.
What GitHub Codespaces does
- Repository-native start
- A codespace is created from a GitHub repository, so the code, branch and history are already present. The page describes the environments as native to GitHub rather than imported from elsewhere.
- Browser or local access
- The same environment can be reached from a browser tab, and the page highlights coding from an iPad. That makes the machine disposable while the work stays in the repository.
- Free monthly quota
- Personal accounts receive 120 core hours and 15 GB of storage each month. Hours are counted in cores, so a larger machine type uses the allowance faster than a 2-core one.
- Admin-controlled billing
- The page poses the question of who pays for organization usage, and the answer is that admins enable it. Spend therefore sits with the organization account, not with each developer.
How GitHub Codespaces handles your data
The Codespaces feature page does not state whether code or prompts are used for model training, how long data is retained or in which region codespaces run, and it names no certification. The page links to GitHub's terms of service, which are the document to read for ownership and licensing language. The vendor's policy was not checked beyond those pages for this review. Because the codespace is tied to repositories hosted on GitHub, repository access controls decide who can open one. Teams with residency or retention duties should ask GitHub for written answers before moving private code into a codespace.
Where GitHub Codespaces falls short in practice
- . Beyond the free allowance, usage is billed pay-as-you-go but the feature page prints no rates. A team has to find the pricing documents elsewhere before it can forecast a monthly bill.
- . The page does not describe an AI assistant or agent inside the codespace. Copilot is named in GitHub's navigation as its own product, so AI features are bought and judged apart.
- . The environment starts from GitHub repositories. Code hosted on another Git service does not get the same repository-native start, which narrows the audience to teams already on GitHub.
Works with
Alternatives to GitHub Codespaces
GitHub Codespaces: common questions
How many free hours does GitHub Codespaces give?
Personal accounts get 120 core hours or 60 hours of run time on a 2-core codespace each month, plus 15 GB of storage, according to the feature page. Hours are measured in cores, so bigger machines consume the allowance faster. Usage beyond the quota is pay-as-you-go.
Can an organization pay for its members' codespaces?
Yes. The page says organization admins can enable usage and pay for it, including for private and internal repositories. Billing then sits with the organization instead of each developer. The page does not print organization rates, and it points to GitHub sales or the organization pricing documents.
Does GitHub Codespaces include Copilot?
The Codespaces feature page does not say so. It lists GitHub Copilot as a separate product in the navigation, described as GitHub's AI coding agent. Check the Copilot plan terms for what is included and what it costs, because the codespace page makes no AI claim.
Can I use Codespaces from a tablet?
The page says you can code from any device and names a browser on an iPad as an example. The environment runs on a remote machine, so the tablet only needs a browser. Performance and keyboard comfort were not tested for this review.
Does GitHub Codespaces work with code that is not on GitHub?
The page describes codespaces as native to GitHub and starts them from GitHub repositories. Code on another Git service would need to be mirrored or moved first. Teams on other hosts should compare tools that do not depend on one repository host.