My main use case for Codespaces is in backend development and quick project onboarding. Day-to-day I use it to spin up a ready-to-use development environment for Java and microservices projects without spending time on local setup, and developing and testing REST APIs, running microservices and Docker, and doing quick bug fixes and code reviews directly from GitHub. In a recent project, I worked on a visa module migration project where we moved APIs and data-handling logic to improve performance and scalability using Codespaces. It helped a lot because I could instantly spin up the complete backend environment with all dependencies, MongoDB configurations, and Docker services already pre-configured. During peak development, it was especially helpful for parallel testing across multiple branches without environment conflicts. Codespaces fits really well into fast-paced development workflows where teams work across multiple repositories and microservices. For me, the biggest value is consistency and speed. Instead of spending time troubleshooting local environment issues, I can directly focus on development. It also works well for temporary tasks such as hotfixes, pull request reviews, or validating changes from different branches, because creating a fresh, isolated environment is very quick. Another benefit is flexibility. I can continue work from different machines without needing a heavy local setup, which is useful when traveling or using a secondary device.
We give flexibility to our developers regarding the use cases for Codespaces, and we don't push them to use them; we give them a choice what they can use. Some of our developers use them and are happy with Codespaces. We are using Codespaces for remote work.
Majorly, I use Codespaces for deployment purposes, validating my codes, and building Docker containers and exporting them to the Google Cloud registry by authentication. I feel it's very easy to deploy my Docker container and validate if it's working fine before building it. Before actual production, I use Codespaces to validate my containers, validate my application, and then push it to my Google Cloud registry for deployment to production. I've used it as a customer with a billing account. When my free tier expired, I got charged on that basis and paid the bill. I haven't used the full chat support. I don't think I have needed such support because my use case was not heavily dependent on Codespaces. I just use it to test my productions, and then my whole production happens on Google infrastructure. I use it as a test case, so it's not a hefty amount I get from Codespaces.
Technical Writer at a manufacturing company with 10,001+ employees
Real User
Top 20
Jul 1, 2025
I use Codespaces for publishing articles. We have a portal with specialists in publications, and we have a structure for adding new articles in Markdown. I use Codespaces mostly for Markdown articles, and I have used GitHub for publishing some Markdown material on a few occasions. It's mostly focused on Markdown, but I appreciate the Codespaces environment.
Co-Founder & Chief Technology Officer at Livecycle
Real User
Top 5
Nov 25, 2024
We use Codespaces as a remote working environment as it provides a consistent working environment and compatibility across devices. Initially, I started using it because I was working on an Apple Silicon device, and my tools weren't compatible with that architecture. The remote environment offered by Codespaces was a solution to this issue.
Senior Solution Architect at Teras Solutions Limited
Real User
Mar 7, 2024
We used the solution to integrate it into the CI/CD process, streamline the editing and updating of code, and make the environments a little more streamlined and accessible.
Codespaces enhances developer collaboration through seamless integration with existing codebases and automatic setup. Its robust feature set, designed for efficiency, also promotes a local-like experience with Visual Studio Code.Codespaces offers a remote development environment tailored for repository management, CI/CD integration, and deployment processes. With quick setup enabled by pre-installed dependencies, it supports flexible workflows like coding, branching, and merging, as well as...
My main use case for Codespaces is in backend development and quick project onboarding. Day-to-day I use it to spin up a ready-to-use development environment for Java and microservices projects without spending time on local setup, and developing and testing REST APIs, running microservices and Docker, and doing quick bug fixes and code reviews directly from GitHub. In a recent project, I worked on a visa module migration project where we moved APIs and data-handling logic to improve performance and scalability using Codespaces. It helped a lot because I could instantly spin up the complete backend environment with all dependencies, MongoDB configurations, and Docker services already pre-configured. During peak development, it was especially helpful for parallel testing across multiple branches without environment conflicts. Codespaces fits really well into fast-paced development workflows where teams work across multiple repositories and microservices. For me, the biggest value is consistency and speed. Instead of spending time troubleshooting local environment issues, I can directly focus on development. It also works well for temporary tasks such as hotfixes, pull request reviews, or validating changes from different branches, because creating a fresh, isolated environment is very quick. Another benefit is flexibility. I can continue work from different machines without needing a heavy local setup, which is useful when traveling or using a secondary device.
We give flexibility to our developers regarding the use cases for Codespaces, and we don't push them to use them; we give them a choice what they can use. Some of our developers use them and are happy with Codespaces. We are using Codespaces for remote work.
Majorly, I use Codespaces for deployment purposes, validating my codes, and building Docker containers and exporting them to the Google Cloud registry by authentication. I feel it's very easy to deploy my Docker container and validate if it's working fine before building it. Before actual production, I use Codespaces to validate my containers, validate my application, and then push it to my Google Cloud registry for deployment to production. I've used it as a customer with a billing account. When my free tier expired, I got charged on that basis and paid the bill. I haven't used the full chat support. I don't think I have needed such support because my use case was not heavily dependent on Codespaces. I just use it to test my productions, and then my whole production happens on Google infrastructure. I use it as a test case, so it's not a hefty amount I get from Codespaces.
I use Codespaces for publishing articles. We have a portal with specialists in publications, and we have a structure for adding new articles in Markdown. I use Codespaces mostly for Markdown articles, and I have used GitHub for publishing some Markdown material on a few occasions. It's mostly focused on Markdown, but I appreciate the Codespaces environment.
We use Codespaces as a remote working environment as it provides a consistent working environment and compatibility across devices. Initially, I started using it because I was working on an Apple Silicon device, and my tools weren't compatible with that architecture. The remote environment offered by Codespaces was a solution to this issue.
We used the solution to integrate it into the CI/CD process, streamline the editing and updating of code, and make the environments a little more streamlined and accessible.
We use the solution as a repository. We develop the code, push it into different branches, and merge it with the main branch.