Codespaces usage is billed for all accounts on the Team and Enterprise plans, and does not include any entitlements. Individual accounts are not currently billed for Codespaces usage.
Codespaces usage is billed according to the units of measure in the following table:
|Product||SKU||Unit of measure||Price|
|Codespaces Compute||2 core||1 hour||$0.18|
|4 core||1 hour||$0.36|
|8 core||1 hour||$0.72|
|16 core||1 hour||$1.44|
|32 core||1 hour||$2.88|
|Codespaces Storage||Storage||1 GB-month||$0.07|
Codespaces are billed in US dollars (USD) according to their compute and storage usage.
The total number of uptime minutes for which the Codespaces instances are active. Compute usage is calculated by the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
Uptime is controlled by stopping your codespace which can be done manually or based on period of inactivity. For more information, see "Closing or stopping your codespace".
For Codespaces billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. At the end of the month, GitHub rounds your storage to the nearest MB.
Your Codespaces usage shares your account's existing billing date, payment method, and receipt. To view all the subscriptions for your account on GitHub.com, see "Viewing your subscriptions and billing date."
To estimate the costs for consumptive services, you can use the GitHub pricing calculator. For more information, go to https://github.com/pricing/calculator.
Note: You must set a spending limit before you can use Codespaces.
By default, your organization or enterprise will have a Codespaces spending limit of $0, which prevents new codespaces from being created or existing codespaces from being opened. To allow your users to create codespaces in your organization, set the limit to a value higher than $0.
For information on managing and changing your account's spending limit, see "Managing your spending limit for Codespaces."
If you hit a spending limit, you will no longer be able to create or resume your codespaces. You can still export any work in progress changes to a new branch.
The type of machine a user chooses when they create a codespace affects the per-minute charge for that codespace, as shown above.
Organization owners can create a policy to restrict the machine types that are available to users. For more information, see "Restricting access to machine types."
Codespaces can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace.
For example, a user in a private organization can fork a repository within that organization, and can subsequently use a codespace billed to the organization; this is because the organization is the owner of the parent repository, which can remove the user's access, the forked repository, and the codespace.
Usage is billed and reported on every hour. As such, you pay for any usage when a repository is within your organization. When a repository is transferred out of your organization, any codespaces in that repository are removed as part of the transfer process.
If a user is removed from an organization or repository, their codespaces are automatically deleted.