docs/content/codespaces/about-codespaces.md

title, intro, redirect_from, versions, type, topics

title	intro	redirect_from	versions	type	topics
About Codespaces	{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.	/github/developing-online-with-github-codespaces/about-github-codespaces /github/developing-online-with-codespaces/about-codespaces /codespaces/getting-started-with-codespaces/about-codespaces	free-pro-team *	overview	Codespaces

{% data reusables.codespaces.release-stage %}

About {% data variables.product.prodname_codespaces %}

{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.

A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.

Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.

A consistent environment

You can create a single codespace configuration that defines the environment (or dev container) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. For more information, see "Configuring {% data variables.product.prodname_codespaces %} for your project."

For help getting started with configurations for specific languages, see the Getting Started tutorials.

While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.

Fast and personal onboarding

With a dev container configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} Code drop-down menu, and selecting Open with Codespaces.

As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.

Developers can also personalize aspects of their codespace environment by using a dotfiles repository and Settings Sync. Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "Personalizing {% data variables.product.prodname_codespaces %} for your account."

Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.

A secure environment

{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Developers can contribute from anywhere, on any machine, including tablets or Chromebooks, and there is no need to maintain local copies of intellectual property. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "Managing access and security for your organization's codespaces."

Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as root.

Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "Managing encrypted secrets for {% data variables.product.prodname_codespaces %}", "Managing GPG verification for {% data variables.product.prodname_codespaces %}".

About billing for {% data variables.product.prodname_codespaces %}

{% data reusables.codespaces.about-billing-for-codespaces %} For more information, see "About billing for {% data variables.product.prodname_codespaces %}."

Joining the beta

A limited number of people will be invited to join the beta. To join the waitlist, see Sign up for Codespaces beta.

Contacting us about {% data variables.product.prodname_codespaces %}

If you encounter problems using {% data variables.product.prodname_codespaces %}, see "Troubleshooting your codespace."

If you still need help or have feedback about {% data variables.product.prodname_codespaces %}, use the Codespaces Feedback discussion.