Coder Community Edition
CoderReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
185 reviews
from
External reviews are not included in the AWS star rating for the product.
Browser-Based IDE Is a Game Changer, Though Sometimes Slower Than Desktop VS Code
What do you like best about the product?
Having an IDE in the browser is a real game changer for me.
What do you dislike about the product?
At times, it feels slower than the desktop version of VS Code.
What problems is the product solving and how is that benefiting you?
In our team, we have multiple host setups. Having the IDE in the browser enables us to use the same setup across different developer workstations, which makes it easier to stay consistent regardless of the machine we’re working on.
Easy to Use with Great Integrations, But Palantir Connection Concerns
What do you like best about the product?
I appreciate Coder for its ease of use, which helps me orchestrate my AI agents and code quicker. The many integrations are cool, allowing me to use different tools I like and test out others. The initial setup was really easy with good documentation.
What do you dislike about the product?
I don't really like the connection to Palantir. Palantir is not a cool company and spies on people. The connection should be at least loosened if not cut.
What problems is the product solving and how is that benefiting you?
I use Coder to orchestrate my AI agents and code faster. It lets me use different tools I like and try out others.
Flexible Deployment Modes Let Us Run Coder On-Prem and Cut Cloud Costs
What do you like best about the product?
i especially like Code for the deployment modes, i can run Coder on our on-Premise hardware and avoid Cloud costs
What do you dislike about the product?
the installation is fairly complex, but that may be caused due to the complexity of the topic and seems unavoidable
What problems is the product solving and how is that benefiting you?
we have completely solved the problem of setting up development boxes for different groups of developers through standardization
Efficient Dev Environment with Minor Setup Hiccups
What do you like best about the product?
I appreciate that Coder provides a virtual workspace that allows me to connect and work from wherever I am. Setting it up once gives me a dev environment for both myself and my AI agents, which is a huge time-saver. It also means I can rely on one powerful computer instead of needing multiple machines. This convenience and efficiency make Coder a valuable tool for my work.
What do you dislike about the product?
The setup is once but there are tricky parts, especially with port forwarding. For database connections, I usually need Coder to connect to different ports, and port forwarding wasn’t straightforward for anything other than the web like port 3000.
What problems is the product solving and how is that benefiting you?
I set up Coder once for a virtual workspace, saving time on configuring multiple environments. It allows me to work from anywhere and manage a single powerful computer instead of many.
Strong Kubernetes Self-Hosted Devbox Experience, Prefer OSS Over SaaS
What do you like best about the product?
Coder is great. We tested the self-hosted option on Kubernetes, and it delivered a strong devbox experience that helped us speed up development and refine our workflow.
What do you dislike about the product?
I’m not a fan of SaaS, so for us the OSS version works just fine.
What problems is the product solving and how is that benefiting you?
DevEx and speed are strong, and the overall agility helps with improving the developer lifespan.
Coder Makes AI Dev Secure, Reproducible, and Fast with Pulumi Templates
What do you like best about the product?
As a freelance software architect working across multiple client environments, the biggest win with Coder is how it eliminates the "works on my machine" problem for AI-assisted development. I define a workspace template once in Pulumi (with the exact Node.js/TypeScript toolchain, NestJS scaffolding, and pre-installed MCP servers I need), and every new workspace spins up identical and ready-to-code in under a minute. Being able to treat dev environments as real infrastructure code — in TypeScript, same language as the projects themselves — means I version-control templates alongside the rest of my IaC and review changes in PRs.
What I didn't expect going in: running Claude Code inside an isolated Coder workspace is a security game-changer. I can give the agent broad filesystem and shell access to work autonomously without touching my local machine or risking client code leaking somewhere it shouldn't be. When a task is done, I tear the workspace down and there's nothing lingering.
Integrations are the other standout. It works with whatever editor a client mandates (VS Code, JetBrains, browser-based), plugs into existing Git providers, and the Pulumi-based templates slot cleanly into the rest of my infrastructure stack.
Performance-wise, running workspaces on beefy cloud instances instead of my laptop cut TypeScript build times by roughly 30% on the larger monorepos, and battery life on long flights is suddenly a non-issue.
What I didn't expect going in: running Claude Code inside an isolated Coder workspace is a security game-changer. I can give the agent broad filesystem and shell access to work autonomously without touching my local machine or risking client code leaking somewhere it shouldn't be. When a task is done, I tear the workspace down and there's nothing lingering.
Integrations are the other standout. It works with whatever editor a client mandates (VS Code, JetBrains, browser-based), plugs into existing Git providers, and the Pulumi-based templates slot cleanly into the rest of my infrastructure stack.
Performance-wise, running workspaces on beefy cloud instances instead of my laptop cut TypeScript build times by roughly 30% on the larger monorepos, and battery life on long flights is suddenly a non-issue.
What do you dislike about the product?
The initial template authoring has a learning curve — if you're coming in without Terraform or Pulumi experience, expect to spend a day or two getting comfortable before your first template is production-ready. The docs are thorough but lean toward reference-style, so I ended up reading example templates on GitHub to piece together best practices.
The Pulumi provider (which I use because my other IaC is already in TypeScript) is auto-generated from the Terraform provider, which works well overall but occasionally lags a release behind on newer features — not a blocker, just something to be aware of if you want the latest capabilities the moment they ship.
Cost predictability is the other thing worth flagging. Because workspaces run on your own cloud infrastructure, your actual spend depends heavily on how disciplined your team is about stopping idle workspaces. Auto-stop policies help, but I'd love to see more granular budget alerts and per-workspace cost attribution in the dashboard.
The Pulumi provider (which I use because my other IaC is already in TypeScript) is auto-generated from the Terraform provider, which works well overall but occasionally lags a release behind on newer features — not a blocker, just something to be aware of if you want the latest capabilities the moment they ship.
Cost predictability is the other thing worth flagging. Because workspaces run on your own cloud infrastructure, your actual spend depends heavily on how disciplined your team is about stopping idle workspaces. Auto-stop policies help, but I'd love to see more granular budget alerts and per-workspace cost attribution in the dashboard.
What problems is the product solving and how is that benefiting you?
Coder solves two problems that were eating into my billable hours as a freelance architect juggling multiple clients.
First, environment drift. Every client has a different stack – Node.js versions, database tooling, cloud CLIs, internal packages – and keeping all of that coexisting on one laptop was a constant source of friction. With Coder, I define each client's environment as a Pulumi template and spin up a dedicated workspace per project. Switching contexts is now a 30-second workspace switch instead of a half-hour of docker juggling.
Second, and more importantly, safe autonomy for AI coding agents. I run Claude Code heavily, and running it inside an isolated Coder workspace (instead of on my local machine) lets me give the agent much broader permissions – long-running refactors, full test-suite runs, dependency upgrades – without worrying about what happens if something goes sideways. The workspace is ephemeral, the blast radius is contained, and client code never leaves its designated environment.
The concrete benefit: I can run 2–3 agent sessions in parallel on separate workspaces, each working on independent tasks. Work that used to be strictly sequential is now parallel, and cloud build times are about 30% faster than my laptop. The compute cost is a rounding error compared to the billable hours it frees up.
First, environment drift. Every client has a different stack – Node.js versions, database tooling, cloud CLIs, internal packages – and keeping all of that coexisting on one laptop was a constant source of friction. With Coder, I define each client's environment as a Pulumi template and spin up a dedicated workspace per project. Switching contexts is now a 30-second workspace switch instead of a half-hour of docker juggling.
Second, and more importantly, safe autonomy for AI coding agents. I run Claude Code heavily, and running it inside an isolated Coder workspace (instead of on my local machine) lets me give the agent much broader permissions – long-running refactors, full test-suite runs, dependency upgrades – without worrying about what happens if something goes sideways. The workspace is ephemeral, the blast radius is contained, and client code never leaves its designated environment.
The concrete benefit: I can run 2–3 agent sessions in parallel on separate workspaces, each working on independent tasks. Work that used to be strictly sequential is now parallel, and cloud build times are about 30% faster than my laptop. The compute cost is a rounding error compared to the billable hours it frees up.
Effortless Remote Dev Environments, Complex Setup
What do you like best about the product?
I mainly use Coder as a dev environment for working remotely, which keeps everything consistent across machines. It eliminates practical headaches, like setting up local environments and dependencies, and solves version conflicts. I like how much friction it removes from everyday development, making life easier. The workspace templates turn environment setup into a one-time effort. For onboarding, these templates reduce the time for a new developer to get started without much hassle, skipping long setup documents. The control Coder gives in resource management is really helpful.
What do you dislike about the product?
Mostly fine for me, except for the initial setup and configuration. I feel it's a bit complex and less intuitive.
What problems is the product solving and how is that benefiting you?
I use Coder for consistent dev environments across machines, eliminating local setup headaches like dependencies, version conflicts. It solves the 'it works on my machine' issue, and makes onboarding easy with workspace templates, reducing setup time for new devs.
Easy Setup with Intelligent Coding Suggestions
What do you like best about the product?
I like Coder for the ease it brings to writing code. The IntelliAssist feature is particularly helpful, providing suggestions on how to write code based on constructs. I also find the cloud IDE to be valuable.
What do you dislike about the product?
I think Coder needs to bring in a differentiating factor.
What problems is the product solving and how is that benefiting you?
I use Coder's IntelliAssist for code suggestions based on constructs. The cloud IDE makes coding easy.
Effortlessly Manages Secure Agent Operations
What do you like best about the product?
I appreciate Coder's AI Governance because it allows me to securely run agents and maintain audit logs easily. It saves time, money, and reduces development headaches. The initial setup of Coder was very easy, which I found beneficial.
What do you dislike about the product?
N/A
What problems is the product solving and how is that benefiting you?
Coder helps me securely run agents, saving time, money, and reducing developer headaches. Its AI Governance allows me to use agents easily while maintaining audit logs.
Coder: Streamlining Development with Standardized Environments
What do you like best about the product?
I really appreciate how Coder improves developer productivity by minimizing environment-related issues, allowing us to focus more on coding rather than setup and troubleshooting. I like the centralized management of workspaces, as it ensures better governance, visibility, and compliance. Coder standardizes environments using templates, which solves the 'it works on my machine' problem and helps with faster onboarding. Additionally, the auto start and stop features, along with workspace lifecycle management, optimize cloud costs and prevent resource wastage. Auto start and stop are especially helpful because they eliminate idle resource costs without needing manual intervention, starting the workspace automatically when I log back in.
What do you dislike about the product?
Though containers is idle workspace for developers but there are times when developers might need Windows OS bases VM workspace, which does not work well. We have highlighted this and Coder engineering team seems to be working on it to resolve this.
What problems is the product solving and how is that benefiting you?
Coder improves productivity by standardizing environments, preventing 'it works on my machine' issues. It speeds up onboarding and allows us to focus on coding. Features like auto start and stop reduce cloud costs and resource wastage, while centralized workspace management enhances governance and compliance.
showing 141 - 150