- Home
- Coding Playgrounds
- Eclipse Che
Eclipse Che
Eclipse Che · Brussels, Belgium · founded 2004
What it is
Eclipse Che runs development IDEs in Kubernetes and lets users create workspaces from a Git repository or a sample. Online use requires only a browser, and available IDEs include Visual Studio Code and JetBrains IDEs. Workspaces are defined with Devfiles, YAML files that can be versioned alongside application source code. GitHub, GitLab, and Bitbucket identities can connect through OAuth, while teams can share a development setup through a URL. Che can run on public or private Kubernetes clusters and supports self-hosted deployment. Workspace access uses OIDC authentication, with Kubernetes RBAC controlling authorization. Enterprise environments can use air-gapped networks, enterprise TLS certificates, proxies, and FIPS. Code is cloned to persistent storage by default, but other workspace file changes disappear when a workspace stops unless saved on a persistent volume. Eclipse Che is free and open source, with a listed price of free. Community support is available through Slack, chat, and a mailing list.
For and against
For
- Free and open source
- Browser access to development workspaces
- Visual Studio Code and JetBrains IDEs
- Deployable on public or private Kubernetes
- Supports enterprise and air-gapped environments
Against
- Workspace changes can disappear without persistent storage
- Requires OIDC authentication for workspace access
- Kubernetes deployment adds infrastructure requirements
The verdict
Eclipse Che provides configurable, shareable development workspaces with broad Kubernetes and enterprise deployment support. Teams should plan persistent storage and authentication before adopting it.
Who it suits
It suits development teams that want browser-accessible IDE workspaces managed through Kubernetes. It is also relevant to organizations needing self-hosting, Git integrations, persistent storage, or enterprise deployment controls.
Plans and prices
Eclipse Che
No pricing or usage limits stated on the pages reviewed
Read 9 Oct 2026 · eclipse.dev
On the record
- Authentication and authorization
- Workspace access requires authentication with OIDC, and Kubernetes RBAC checks whether a user may access a workspace.eclipse.dev · read 9 Oct 2026
- Browser access
- The product page says a browser is the only requirement for using Che online.eclipse.dev · read 9 Oct 2026
- Community support
- The project site links to community Slack, chat, and a mailing list.eclipse.dev · read 9 Oct 2026
- Enterprise environments
- The site says Che workspaces support air-gapped networks, enterprise TLS certificates, proxies, and FIPS.eclipse.dev · read 9 Oct 2026
- Git integrations
- Users can connect GitHub, GitLab, or Bitbucket identities using OAuth.eclipse.dev · read 9 Oct 2026
- IDE options
- The site identifies Visual Studio Code and JetBrains IDEs as IDEs available with Eclipse Che.eclipse.dev · read 9 Oct 2026
- Kubernetes deployment
- Eclipse Che can be deployed on public or private Kubernetes clusters.eclipse.dev · read 9 Oct 2026
- Maker
- The Eclipse Foundation describes itself as an international non-profit association supporting open-source collaboration.eclipse.org · read 9 Oct 2026
- Maker history
- The Eclipse Foundation says it was created in January 2004 as an independent not-for-profit corporation.eclipse.org · read 9 Oct 2026
- Persistence limit
- Workspace file changes are wiped when a workspace stops unless they are stored on a persistent volume; code is cloned to a persistent volume by default.eclipse.dev · read 9 Oct 2026
- Purpose
- Eclipse Che runs development IDEs in Kubernetes and lets users create workspaces from a Git repository or sample.eclipse.dev · read 9 Oct 2026
- Workspace configuration
- Development workspaces are defined with Devfiles, YAML files that can be versioned with application source code.eclipse.dev · read 9 Oct 2026
- Workspace sharing
- The site says teams can share a development setup using a URL.eclipse.dev · read 9 Oct 2026
