Codespaces Reviews

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.

From my experience, the best features Codespaces offers are instant development environment setup. I can easily start a fully configured environment in minutes. This is the biggest advantage it offers. Deep GitHub integration is very convenient to open pull request branches and a repository directly into the ready-to-use workspace. With cloud-based development, I can work from almost any device without depending heavily on local environment setup. It works seamlessly with VS Code, and the transition feels natural, and productivity stays high. Port forwarding and terminal access make testing APIs and microservices much easier during backend development.

Out of all these features, for me, the biggest impact comes from the instant environment setup with dev container configurations in Codespaces. In backend and microservices projects, setting up dependencies, Docker services, environment variables, databases, and specific tool versions locally can take a lot of time. With Codespaces, everything is already predefined, so I can start coding almost immediately. I probably use that feature the most because it speeds up switching between multiple projects, eliminates most local environment issues, and makes onboarding and collaborations much smoother. Personally, it saves me several hours every month that would otherwise go into setup, troubleshooting, or configurations management.

Codespaces is primarily hosted on Microsoft Azure infrastructure. In our case, the underlying cloud provider is effectively through Azure.

From an improvement perspective, Codespaces is very strong overall, but a few areas where it could improve are the following. First, cost optimization and visibility. For larger teams, costs can grow quickly. More detailed cost tracking, alerts, and optimization recommendations would help. Second, performance consistency. Sometimes startup times or resource performance can vary depending on the workspace size or network conditions. Third, offline or hybrid capabilities. Since it is cloud-dependent, limited connectivity can affect productivity. Better offline synchronization options would be very useful. For backend teams, especially, enhanced enhancements around scaling heavier workloads and optimizing Docker-based environments would also add a lot of value.

One additional improvement is around long-running development sessions and enterprise-scale workflows. For example, better persistence and recovery options after inactive sessions or reconnects would improve the experience for developers working on larger projects. More optimized handling for heavy IDE extensions and Docker workloads would help teams working with complex backend systems. Overall, the platform is already very productive, but enhancements around performance optimizations, enterprise governance, and large-scale collaboration would make it even stronger for advanced engineering teams.

I have been using Codespaces for the last eight months.

My advice for the team evaluating Codespaces would be to start with a small project first to standardize your dev container configurations and workflow before scaling organization-wide. Invest time in properly configuring dev containers, Docker setups, and dependencies early. That is where the most of the long-term productivity gain comes from. Use it especially for onboarding distributed teams and microservices projects where environment consistency matters a lot. Integrate it closely with your CI/CD and GitHub workflows to get the most value from the platform. Keep local fallback options available for developers who may occasionally face connectivity or performance constraints. I would rate this product nine out of ten.

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.

It's a good tool. I have used several others, including Google's own virtual environment, but that's very costly and takes much time to set up. If you don't delete it, you get exponential bills. I prefer Codespaces because it gets activated in seconds and has all the pre-dependencies which any developer could need, such as Docker and Python. They have already installed the basic libraries and Linux commands, so it's ready to go.

It's not expensive. It's very cheap compared to others such as Google. Google's same service is much more expensive because it will install the pre-dependencies and takes a longer time to activate. Codespaces has a much better alerting system than Google's. It will give you a mailing alert on your GitHub and email when you have used your budget around 70% or 50%. You can set it and it will automatically give you updates.

I think there should be a scheduler option if you want to run it, similar to Google Cloud, where you can specify how long you want to keep your scheduling active. If you want to use it as a server or for a temporary time duration, you should be able to schedule it so the server will be activated between specific durations and auto-deactivate to save costs.

Sometimes, at the initial stages, there is a lack of instances. It takes more time to create the instance, but now it's much faster to activate your Codespaces and delete it. The earlier Git Codespaces billing setup on GitHub was much simpler. You could easily see how much credit you have, how much you have used, and your balance. Now they have changed it, and it's confusing to understand how much Codespaces time you have, how much you have used, and how much they are charging.

I've been using it for the past one and a half years.

I haven't come across any issues because I don't use it as my real environment. I use it when necessary. Sometimes, at the initial stages, there is a lack of instances. It takes more time to create the instance, but now it's much faster to activate your Codespaces and delete it. The earlier Git Codespaces billing setup on GitHub was much simpler. You could see how much credit you have and how much you have used. That was easier to understand, but now they have changed it, and it's confusing to understand how much Codespaces time you have and how much they are charging.

Positive

When I started using Codespaces, I was still learning Google cloud computing. I did not have much information about how cloud works. After discovering Codespaces, my cloud journey became much easier in terms of understanding how to build projects and actively deploy them in a production environment. Codespaces was the second or third option I learned about, and then I stuck to it. I haven't tried any new solution because it was perfect for my needs.

It's a good tool. I have used several others, including Google's own virtual environment, which is very costly and takes much time to set up. If you don't delete it, you get exponential bills. I prefer Codespaces because it gets activated in seconds and has all the pre-dependencies which any developer could need, such as Docker and Python. They have already installed the basic libraries and Linux commands, so it's ready to go.

It's not expensive. It's very cheap compared to others such as Google. Google's same service is much more expensive because it will install the pre-dependencies and takes a longer time to activate. Codespaces has a much better alerting system than Google's. It will give you a mailing alert on your GitHub and email when you have used your budget around 70% or 50%. You can set it and it will automatically give you updates.

I give Codespaces an eight and a half out of 10.

I definitely recommend it for students who are learning and want to test their applications. It's very simple to start, and your whole codebase would be ready to use. You can comment on it, edit it, and everything can be done very smoothly.

I use different tools based on my needs and try to explore them to get in touch with new technologies. I have used Loveable and Note LLM. I try connecting with new things as they go live. I use Codespaces frequently, approximately 15 days in a month.

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.

We see benefits from Codespaces in terms of onboarding new team members; it is very simple. We use dev containers and have the dev containers definition in a repository, and with that, it is not zero-click, but kind of one or two clicks and people are ready.

The integration with Visual Studio Code in Codespaces helps a lot with our development process in general. We also use Cursor, which is a fork of VS Code, and that integration works great.

We are using a port forwarding feature in the product. We see benefits from the port forwarding feature in Codespaces, including for cloud-native application development and local testing. This helps developers to develop in the cloud, but still also being able to test locally what they have.

We track metrics on development time saved using Codespaces. It is not the responsibility of my team, so I know we do, but I don't have any insights. We use Cursor.

I am not the best person regarding the negative sides of Codespaces. As I mentioned, our team provides different tools for developers, so we are not so deep in every tool. From time to time, we got some feedback from developers about their usage patterns, but I just don't have any numbers and don't have any summary.

Regarding the issues that they report most frequently, there is definitely no one single issue from the top of my head. There are some small wishes, but I cannot remember anything specific.

I would call the stability of Codespaces an eight. I rate it eight and not ten because if you go to githubstatus.com and check history for all issues GitHub has, all of those issues affect the availability of this product. Sometimes it is just two or three hours a day where they are totally unreachable, and it might happen like five times a month. That is far from ten.

I would give scalability for Codespaces a ten. It is pretty well, so I rate scalability a ten.

I don't have much experience with technical support from GitHub.

Neutral

The deployment and installation of Codespaces is not the responsibility of my team. We have a dedicated team for that.

We found the price of Codespaces is acceptable for us.

It is hard for me to say about collaboration efforts in this case. I am in a team who is responsible for CI, so we try to touch everything we suggest to our developers, but I am not their direct user of Codespaces. We have a solution for Codespaces in the cloud. I rate this review an eight overall.

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.

The main benefits I have seen from using Codespaces include easy management of comments about particular sections. The review functionality of the pull requests is very handy, as not only can you give comments, but you can also suggest replacements for sentences with different words. This speeds up the process because when you have 50 remarks and someone has already indicated to change a word for another, it's just one click to apply the change. I find there is good visualization for the comments, and you can display them, fold them, or unfold them, depending on how you approach your task. There's also a mini map of the article you're writing with blue spots to show where the comments are located. Many thoughtful user experience tricks help you move along faster.

With Codespaces, I had a comparison with WordPress, and in WordPress, collaboration was very limited. It was really difficult to keep track of editing the same document by two people, and there was no collaboration. The work is much more collaborative with Codespaces. It's dynamic, allowing you to focus on certain sentences or chapters in an article, helping to break down the content and get feedback from team members. Before that, it was mostly solo work, and someone had to provide comments in Word or something, requiring manual application of changes. There was no real-time collaboration.

I don't recognize what compute resources are in relation to my projects in Codespaces.

I'm looking at Codespaces to help myself express what I mean regarding pre-configured environments. I don't think they were pre-configured. When I created an environment, we had a list of extensions that my team decided to use. These were the main things that I had to configure to ensure we are on the same page, including spell checking and so on.

My issues with Codespaces were mostly due to my inexperience with GitHub, and I did not understand certain aspects. I think there was a learning curve. As a beginner, you can get lost in the user interface because of the many screens, buttons, and functionalities geared towards power users, making it difficult to find particular icons you're looking for. Initially, it was intimidating, and I had to learn conventions such as how to interpret certain document displays when changing branches. There's one particular issue where if you commit without a title for a commit, you get a message that opens a document, preventing you from committing until you close that message. It was frustrating not knowing I had to close it, thinking the commit process was ongoing.

I don't have much criticism because these functionalities have purpose, and as I get to use more advanced features, they come in handy. I look forward to that. However, for a beginner, it is intimidating to search for options when many are available. Additionally, I did not participate in any training or use training material, instead relying on advice from experienced users, which also explains my stumbling at times.

I don't feel I lack any specific features or functionalities in Codespaces. I'm not yet familiar with all extensions and how to fully utilize them. Currently, I have basic spell-checking extensions, which are not very intelligent; they just include some basic word lists. It's sufficient for me.

I have been working with Codespaces for approximately a year and a half.

We never had any questions that needed escalation to GitHub technical support.

Negative

We previously used WordPress and then decided to switch to another option. I was not a part of the evaluation or comparison, and I don't have in-depth knowledge of the tools; I just learned to use the tool I was provided.

I don't have much time to discuss any other product or solution I am currently working with. I don't think I can offer advice or recommendations since I never implemented Codespaces myself. I'm just a user. However, I can tell people who want to adopt and start using it that it is easy to learn and works well. On a scale of 1-10, I rate Codespaces a 9.

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.

Currently, Codespaces is just used as a developer environment, and we don't specifically use it to aid in AI projects.

The capability to open and develop an environment quickly and consistently is a significant benefit. The integration with Visual Studio Code offers a good and fast user experience that feels like a local experience. 

The developer experience is consistent, and its pricing makes sense since it optimizes the resources.

The main issue is related to state preservation on a disconnection. When I close the laptop and open it in a different place, the state of the environment disappears, and I need to rerun several commands. This context switch affects productivity.

I have been using Codespaces for about three years, ever since it was in beta.

Codespaces operates around seven out of ten for stability. While it works most of the time, there are instances when it becomes flaky.

I work in a relatively small team, so I would rate its scalability as eight out of ten.

I haven't needed to contact technical support, so I don't have experience with their service.

Positive

Before Codespaces, we used our in-house solution, which involved using a VM in the cloud with a code editor. It worked well, but Codespaces streamlined the experience, making the transition easy.

Setting up Codespaces was straightforward since we were already using Docker and complementary technologies.

We managed the implementation ourselves.

It's hard to tell the impact on ROI, as we would have used an alternative solution with similar capabilities if we hadn't chosen Codespaces.

Using Codespaces for a single station is cost-effective. However, I am not well-versed in the broader licensing considerations.

An in-house solution was evaluated, involving a cloud-based VM with a code editor.

Based on my experience, I would recommend Codespaces. 

I rate the solution eight out of ten.

We use the solution as a repository. We develop the code, push it into different branches, and merge it with the main branch. 

Codespaces' most valuable feature is the repository, which helps the developers to work together. Its data commands are also useful. 

We get merge conflict errors and need to resolve them. 

I have been using the product for ten years. 

Codespaces is scalable. 

I haven't reached out to the technical support yet. 

I faced difficulty setting up the tool as a junior developer. However, once you become senior and gain experience, you won't face problems. The tool's deployment takes five minutes to complete. 

I rate Codespaces a nine out of ten. 

Codespaces help increase the efficiency in coding with the AI features.

The product allows us to implement feature-related changes or improvements on time. Whenever I write a section of the code or create a new code, it automatically integrates with the former code. It helps me remember what I am trying to implement, even if I forgot some details.

The product indicates incorrect statistics. Once, I compared its statistics result for a data set with that from Google. The main part of the answer provided by Codespaces was inaccurate. They should improve this particular feature.

I rate the product’s stability an eight out of ten. It has some inaccuracies, and it stops working sometimes.

I rate the product’s scalability a nine out of ten.

We use Copilot as well. However, we use Codespaces more often.

The initial setup is easy. We deployed it on the cloud. The process takes little time. It gets configured after installing an AWS plug-in on an integrated development environment. It is an easy-to-use tool.

I am using the product’s free version.

I rate Codespaces an eight out of ten. You should have a higher knowledge of the project you are working on. You should only depend on it partially, as it produces inaccurate results. It is still in a phase of constantly being tested, trained, and improved.

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.

The most valuable features of the solution are Copilot and Advanced Security.

Codespaces is a stable solution.

I rate the solution's customer service an eight out of ten. I rate the solution's technical support a five or six out of ten because the environment wasn't live. It's not like I was experiencing an outage with the problems I was having. So, it was a little less urgent for them.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

From what I've seen, the solution doesn't seem like it's overly expensive for what you get.

The coding experience because of GitHub integration is going to be largely the same because GitHub is a standardized platform. All the developers know they like it, and that's why it's popular. They wanted the enterprise to have an offering that integrates with user accounts with Active Directory.

If they onboard a developer as a contractor or just from a vendor perspective or somebody internal, and if that person leaves, code doesn't leave with them. They're not taking it on their own GitHub subscription and then uploading it. It also gives us the extra security of controlling the code that we own.

The setup has nothing to do with the GitHub function in and of itself. It's integrating it with identity providers, in Active Directory, and single sign-on and multifactor authentication. Those were some challenges, but the GitHub experience is good. It's just a matter of locking down the subscription and deployment according to the security group requirements.

Codespaces handles large projects or high-complexity applications very well. It hasn't gone live yet, so I can't vouch for that in this organization. Based on what I know of the structure of it, it's top-notch. Based on what I've seen in the setup, it seems like GitHub is able to handle complex projects and large deployments.

The solution is deployed in the cloud. The solution's infrastructure's maintained by GitHub, and we just maintain the repository. I would recommend Codespaces to other users.

Overall, I rate the solution a nine out of ten.