We use cookies to make your experience better.
Gitpod and Coder both provide developers with reproducible, powerful, cloud-based developer environments or workspaces, but they differ dramatically in their target audience: While Gitpod appears to be focused on individuals or small teams, Coder is focused on making cloud development available to the enterprise.
Here's how to choose the best fit for your development team.
Today most developers have their IDEs on their local machines. There is a growing interest in moving development workspaces and IDEs to the cloud, which solves some key problems for organizations while also offering advantages for the developer:
start coding on day one — developers often spend hours or days setting up a development environment on a local machine before they can make their first commit. With cloud-based workspaces, fully configured workspaces are available for developers to start contributing immediately.
secure source code — individual devices remain the least secure endpoint in the software development pipeline. With local development, source code and data are cloned to individual workstations, creating security risks. With cloud-based workspaces, source code and data remain within the organization’s infrastructure.
less drift — dependency and configuration drift in the development environment results in broken environments and builds, i.e., the classic “it works on my machine” problem. Reproducible, cloud-based developer workspaces ensure that everyone is working with the same basic configuration.
greater compute power — cloud development eliminates the need to focus on local hardware. Need more processing power? Add more cores to your instance—or a GPU.
remote access — because development environments are in the cloud, developers can access them securely from wherever they are.
Gitpod is very focused on the developer experience. Getting started with Gitpod is easy. In fact you can launch a new workspace for a project by navigating to https://gitpod.io/#repo-url. Like Coder, they developed (and open-sourced) a fork of VS Code suited for the web browser. Using a familiar IDE makes it simpler for developers to transition to remote development, since they do not need to learn new shortcuts, extensions, etc. Gitpod also supports different IDEs beyond VS Code in the web browser. Developers can choose between VS Code (Web), VS Code (Local), and beta support for IntelliJ IDEs to write code.
Gitpod’s opinionated model for development environments can work well for new projects and small teams building web applications. All workspaces are ephemeral, run in containers, and new workspaces can be created for each task (feature, bugfix, code review) a developer does.
While Gitpod has a self-hosted option, it has limited administrative features, and features from their SaaS (e.g prebuilds) have not been supported. Coder, on the other hand, is focused primarily on self-hosted deployments and empowering developers at enterprises.
One example is multi-cluster support. With Coder, multiple workspace providers can be deployed so developers can develop remotely with low-latency wherever they are on the globe. This is particularly useful for organizations that may have teams of developers that are geographically distributed. Coder also supports other enterprise-grade features such as built-in single-sign-on, an audit log, configurable workspace resources, quotas, and usage metrics.
Coder supports different types of infrastructure. While Coder can run on Kubernetes, it is not required. Coder also runs on Docker and has support for AWS EC2-based workspaces. More infrastructure variety will be added in 2022.
Enterprises can confidently deploy Coder at scale in their organization, measure its adoption, and configure their deployment to match requirements for different teams.
With that being said, the developer experience with Coder is not an afterthought. Coder supports multiple IDEs, custom applications, full Linux desktop, container development, GPU support, REST access, CLI access, and personalization to enable developers and teams to move their existing workflows to remote workspaces.
Coder | Gitpod | |
---|---|---|
Try in seconds (cloud) | ✅ | |
Cloud version | ✅ | |
Self-host (Docker) | ✅ | |
Self-host (Kubernetes) | ✅ | ✅ |
Self-host (Multi-region) | ✅ | |
Organizations/teams | ✅ | Beta |
SSO Support | ✅ | Custom quote |
Usage metrics | ✅ | |
Audit log | ✅ | |
Configurable workspace resources and limits | ✅ | |
GitHub, GitLab, Bitbucket integration | ✅ | ✅ |
Use VS Code IDEs | ✅ | ✅ |
Use JetBrains IDEs | ✅ | Beta |
Custom apps and IDEs | ✅ | |
Docker in workspaces | ✅ | ✅ |
GPUs in workspaces | ✅ | |
Configure workspace images and templates | ✅ | ✅ |
Workspace pre-builds | ✅ | |
Workspace snapshots | ✅ | |
CLI | ✅ | ✅ |
REST API | ✅ | |
Collaboration | via third-party IDE extensions |
✅ |
When NOV needed to support multiple remote IDEs for data scientists on their infrastructure, Coder was the answer.
Gitpod has a free self-hosted plan with limited features. With complete feature support, Gitpod costs $35/user/month after 10 users. Coder costs a flat $35/user/month after a 60-day trial.
With hosted (SaaS) workspaces, Gitpod has a number of different plans but costs roughly $39/user/month for teams.
It takes around 5 minutes to self-host Coder with Docker, see our documentation. You can also request a demo of Coder.
Gitpod is also easy to try, you can try their SaaS or self-host with Kubernetes.
$ docker run --rm -it -p 7080:7080 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v ~/.coder:/var/run/coder \ codercom/coder:1.30.0
Learn more about our projects and our commitment to the open source community.
code-server: the heart of Coder
code-server is the primary open source project we maintain. It allows developers to use a browser to access remote dev environments running VS Code. Coder builds upon the success of code-server and adds features designed for enterprise teams including support for additional IDEs and advanced security features.