Сведения о выставлении счетов для GitHub Codespaces

About GitHub Codespaces pricing

Note that GitHub may apply a temporary authorization hold for the value of the usage-based costs in advance, which will appear as a pending charge in your account's payment method.

GitHub Codespaces is paid for either by an organization, an enterprise, or a personal account. The Free and Pro plans for personal accounts include free use of GitHub Codespaces up to a fixed amount of usage every month.

Organizations can choose whether codespaces created from their repositories will be user-owned or organization-owned. See "Choosing who owns and pays for codespaces in your organization." An organization pays for a codespace if all the following things are true.

• The organization has chosen for codespaces to be organization-owned.
• The organization has set a non-zero spending limit for GitHub Codespaces.
• The codespace is created from one of the organization's repositories, or from a fork of one of the organization's repositories. This includes public, private, and internal repositories.
• The user creating the codespace is a member or collaborator of the organization, and the organization has enabled GitHub Codespaces for this user. This can include all members and collaborators if the organization has chosen to enable Codespaces for all users. If Codespaces isn't enabled for a user, they can still create codespaces from public repositories in the organization, but the user will pay for these codespaces.

For more information about enabling GitHub Codespaces for users, see "Enabling or disabling GitHub Codespaces for your organization."

Otherwise use of GitHub Codespaces applies to the personal account of the person who created the codespace, and either consumes some of the monthly included usage for their personal account, or their account is billed according to their usage in excess of their included quotas.

The Free, Team, and Enterprise plans for organization and enterprise accounts do not include any free use of GitHub Codespaces.

Pricing for paid usage

A GitHub Codespaces instance (a "codespace") incurs charges for compute time, while it is active, and for the amount of disk space the codespace occupies, while it exists. The compute cost is proportional to the number of processor cores in the machine type you choose for your codespace, as shown in the following table. For example, the compute cost of using a codespace for an hour on a 16-core machine is eight times greater than a 2-core machine.

Component	Machine type	Unit of measure	Included usage multiplier	Price
Codespaces compute	2 core	1 hour	2	$0.18
Codespaces compute	4 core	1 hour	4	$0.36
Codespaces compute	8 core	1 hour	8	$0.72
Codespaces compute	16 core	1 hour	16	$1.44
Codespaces compute	32 core	1 hour	32	$2.88
Codespaces storage	Storage	1 GB-month	Not applicable	$0.07

For more information about the GB-month unit of measure, see "About billing for storage usage."

If you enable prebuilding of codespaces this will incur additional charges. See "About billing for Codespaces prebuilds."

About your bill for GitHub Codespaces

GitHub Codespaces is billed in US dollars (USD) according to the amount of compute time and storage space your codespaces use. Costs for GitHub Codespaces are always billed monthly, even if your account is otherwise billed annually.

Billing for GitHub Codespaces shares your account's existing payment method, and receipt. See "Viewing your subscriptions and billing date."

If you are an organization owner or enterprise owner, you can connect an Azure Subscription ID to your organization or enterprise account to enable and pay for GitHub Codespaces usage. See "Connecting an Azure subscription."

About billing for compute usage

The compute usage of a codespace is the length of time for which that codespace is active multiplied by the multiplier in the pricing table for the machine type of the codespace. Total compute usage is calculated by summing the time used by all codespaces billable to a particular account. These totals are reported to the billing service every hour, and are billed monthly.

As an example, if a codespace is active for 1 hour and 15 minutes, then the compute cost will be the hourly cost of the codespace, as determined by its machine type, multiplied by 1.25.

You can control compute usage by stopping your codespaces. For information, see "Stopping and starting a codespace." Codespaces are stopped automatically after a configurable period of inactivity. The timeout period can be configured by the user, or at the organization level. See "Setting your timeout period for GitHub Codespaces" and "Restricting the idle timeout period."

About billing for storage usage

For GitHub Codespaces billing purposes, storage comprises the disk space used by all of the codespaces and prebuilds in your account. This includes any files you use in a codespace, such as cloned repositories, configuration files, data loaded to the codespace (for example as input or output of the software running in the repository), and extensions, among others. Storage is billed for all of your existing codespaces, regardless of whether they are active or inactive with the exception of blocked usage due to exhausted included usage quota or reaching your spending limit. The storage billing for a codespace ends when it is deleted. However, deleting a codespace does not reduce your used storage amount for the current billing month as this is a cumulative figure.

Storage billing for containers based on the default image

When you use the default dev container configuration, your container is built from the default Linux image for codespaces. See "Introduction to dev containers."

Containers based on the default image are not counted as used storage, even if you add features in your dev container configuration. See "Adding features to a devcontainer.json file."

If you use the default image, the storage usage for your codespace will be based on the files in your repository, and any files you subsequently add to the codespace. If you use an alternative base image, then the resulting container and all of the files in the codespace will be counted as used storage.

For information on how to check whether a codespace was built from the default dev container image, see "Getting the most out of your included usage."

Reporting storage usage

Codespace storage is reported in GB-months. Your billing month runs from a fixed day in one month until the same day in the next month. In most cases the day of the month is determined by the day you started on your current GitHub plan. Your GB-month storage is calculated as follows. Once every hour, the storage used by all of your currently active and stopped codespaces is assessed. This figure is then divided by the number of hours in the current billing month: total storage size / hours this month. The result is added to the running total for codespace storage for the month.

For example, if you have one codespace that uses 100 GB of storage and has existed for one hour you will have used 100 / (24 * 30) = 0.1388 GB-months of storage in a 30-day month. If your use of GitHub Codespaces during a 30-day month consists of two 100 GB codespaces that both existed for three full days then there will be 24 * 3 hourly reports for the storage of these codespaces, giving a total of (24 * 3) * 200 / (24 * 30) = 20 GB-months.

For each hourly report, the storage usage for the previous hour is calculated in seconds. As a result, you won't be charged for a full hour of storage if a codespace did not exist for the full 60 minutes. At the end of the month, GitHub rounds your storage to the nearest MB.

Organization owners can:

• List the currently active and stopped codespaces for your organization. See "Listing the codespaces in your organization." In addition to the cost of these codespaces, the cost of GitHub Codespaces for the current month may include costs for codespaces that existed earlier in the current month but have since been deleted.
• See the total GitHub Codespaces compute and storage usage for your organization for the current month to date. See "Viewing your GitHub Codespaces usage."
• Configure your organization settings to manage the cost of GitHub Codespaces. See "Managing the cost of GitHub Codespaces in your organization."

To estimate the costs for usage-based billing, you can use the GitHub pricing calculator.

About billing for Codespaces prebuilds

A prebuild assembles the main components of a codespace for a particular combination of repository, branch, and devcontainer.json configuration file. It provides a quick way to create a new codespace. For complex and/or large repositories in particular, you can create a new codespace more quickly by using a prebuild. See "About GitHub Codespaces prebuilds."

GitHub Actions costs for prebuilds

Prebuilds are created and updated by running a GitHub Actions workflow on a GitHub-hosted runner. You can configure how you want prebuild updates to be automatically triggered. For information, see "Configuring prebuilds."

As with other workflows, while prebuild workflows are running they consume GitHub Actions minutes included with your account, if you have any, or they incur charges for GitHub Actions minutes. For more information about pricing for GitHub Actions minutes, see "About billing for GitHub Actions." There is no associated Codespaces compute cost for creating or updating prebuilds.

You can track usage of prebuild workflows and storage by downloading a usage report for your account. See "Viewing your GitHub Codespaces usage."

Storage costs for prebuilds

In addition to GitHub Actions minutes, you will also be billed for the storage of prebuilds associated with each prebuild configuration, for a given repository and region. Storage of prebuilds is billed at the same rate as storage of codespaces.

The storage cost for a prebuild in a single region will be similar to the storage cost that will be incurred for storing a single codespace created from that prebuild. The storage cost for the generated codespace may be more than the cost for the prebuild if, for example, the updateContentCommand and postCreateCommand commands are used during codespace creation to download more files to the dev container.

The total storage costs associated with a prebuild configuration will depend on the following factors.

• The price of storage per GB (see the table earlier in this article)
• The size of the generated prebuild in GB
• The number of regions in which the prebuild is available (because a copy of the prebuild is stored in each region)
• The number of older versions of the prebuild that are retained

The storage cost for the prebuilds generated by a prebuild configuration is therefore calculated as: price per GB * size (GB) * regions * versions.

You can check how many GB-months of storage has been used by prebuilds by reviewing the current billing data for your personal or organization account. See "Viewing your GitHub Codespaces usage."

If you create prebuilds for a forked repository, the storage cost of those prebuilds is subtracted from your monthly included storage, while available. If you have used all of your included storage, and you have set up billing, your personal account will be billed. This is true even when the codespaces you create for a fork are paid for by the organization that owns the parent repository. See "How billing is handled for forked repositories."

Controlling the cost of prebuilds

To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of previous versions of each prebuild that are retained. See "Configuring prebuilds."

To limit the storage costs associated with prebuilds, you can choose to create prebuilds only in selected regions, and you can specify the number of older versions of prebuilds that will be retained. See "Configuring prebuilds."

If you delete a prebuild configuration, all the associated prebuilds are deleted, reducing your storage consumption from that point onward. See "Managing prebuilds."

Prebuilds can be updated multiple times during a billing month. Each update may change the size of the prebuild, which affects your storage charges. For details of how storage is calculated during a billing month, see "About billing for storage usage" earlier in this article.

Cost of codespaces created from prebuilds

Use of codespaces created using prebuilds is charged at the same rate as regular codespaces.

Setting a spending limit

By default, all accounts have a GitHub Codespaces spending limit of $0 USD. This prevents new codespaces being created, or existing codespaces being opened, if doing so would incur a billable cost to your personal, organization, or enterprise account. For personal accounts, if you have access to create a codespace, you can do so as long as the account has not reached the limit of its monthly included usage. For organizations and enterprises, the default spending limit means that, to allow people to create codespaces that are billed to the organization, or its parent enterprise, the limit must be changed to a value above $0 USD.

For information on managing and changing your account's spending limit, see "Managing the spending limit for GitHub Codespaces."

If your personal, organization, or enterprise account reaches its spending limit, you will no longer be able to create or resume codespaces that are billable to that account. However, you can still export any work-in-progress changes to a new branch. For more information, see "Exporting changes to a branch."

Viewing projected usage for an organization

Organization owners and billing managers can view an estimated total usage cost for GitHub Codespaces for the organization, for the current monthly billing cycle. See "Viewing your GitHub Codespaces usage."

The projected usage shown on the billing page for an organization is calculated based on the total cost for Codespaces compute and storage usage incurred during the previous seven days, prior to the current day. This is projected forward for the remainder of the billing month to give you an idea of how much the total cost might be for the current billing cycle.

The calculation used for this estimate is:

<cost for the previous 7 full days>/7 * <days remaining in the billing month, including the current day> + <cost already accrued in this billing month>

The projected usage does not take into account information such as whether GitHub Codespaces is still enabled, the number or size of codespaces that currently exist, or your prebuild settings. For this reason, if all of the organization's codespaces and prebuilds were deleted today, the projected usage for the billing month would still show a figure higher than the accrued usage. However, after seven days have elapsed, with no further Codespaces usage, the projected usage will be the same as the currently accrued usage.

Limiting the machine types for organization-owned codespaces

By default the machine type with the lowest valid resources is used when a codespace is created. However, users may be able to choose a machine type with more resources. They can do this either when they create a codespace, or they can change the machine type of an existing codespace. See "Creating a codespace for a repository" and "Changing the machine type for your codespace."

If a machine type that has more resources is chosen, this will affect the per-hour charge for that codespace, as shown in the table earlier in this article.

Organization owners can create a policy to limit the choice of machine types available to users for codespaces that are billed to an organization or enterprise account. See "Restricting access to machine types."

Limiting the number of organization-owned codespaces

Organization owners can limit the number of codespaces that people can create, where the organization will be billed for the codespace. This can help to reduce storage charges for the organization. See "Restricting the number of organization-billed codespaces a user can create."

How billing is handled for forked repositories

Usage of codespaces created from a forked repository will be billed to your personal account unless the upstream (or parent) repository is in an organization that has allowed you - as a member, or outside collaborator, of the organization - to use codespaces at the organization's expense.

For example, consider a member, or outside collaborator, of an organization that has allowed billing for codespaces for that user. If the user has permission to fork an organization-owned private repository, they can subsequently create and use a codespace for the new repository at the organization's expense. This is because the organization is the owner of the parent repository. Note that the organization owner can remove the user's access to the private repository, the forked repository, and therefore also the codespace. The organization owner can also delete the parent repository which will also delete the forked repository. See "Managing the forking policy for your repository."

If you create prebuilds for a forked repository, the storage cost of those prebuilds is subtracted from your monthly included storage, while available. If you have used all of your included storage, and you have set up billing, your personal account will be billed. This is true even when the codespaces you create for a fork are paid for by the organization that owns the parent repository.

How billing is handled when a repository is transferred to another organization

Usage is calculated every hour. An organization pays for usage of codespaces created from any repository owned by the organization, where the organization settings permit the organization to be billed. See "Choosing who owns and pays for codespaces in your organization." When a repository is transferred out of your organization, ownership and billing responsibility for any codespaces associated with that repository will change accordingly.

How billing is handled for GitHub Codespaces templates

You can get started on a new project by creating a codespace from a template. Codespaces created from templates aren't initially associated with a repository, but you can publish the codespace to a repository owned by your personal account. See "Creating a codespace from a template."

Any organization can maintain a template repository for use with GitHub Codespaces. As with any other repository in an organization, a codespace created from a template repository is billed to the organization if the organization has set a spending limit for GitHub Codespaces and allowed the user creating the codespace to do so at the organization's expense. Otherwise, the codespace is billed to the user who creates the codespace.

If a user publishes a codespace created from a template, the codespace is published to a new repository owned by the user's personal account. If the codespace is currently billed to an organization, ownership and billing of the codespace transfer to the user who created the codespace.

A managed user account cannot be the billable owner of a codespace. Therefore:

• A managed user account can only create a codespace from a template if the codespace is billed to an organization.
• A managed user account cannot publish a codespace created from a template to a new repository.

See "About Enterprise Managed Users."

What happens when users are removed

If a user is removed from an organization or repository, their codespaces are automatically deleted.