When to use Che
Che is designed for teams that need consistent, secure, and centrally managed development environments on Kubernetes. Not every team requires a cloud development platform, so evaluate your development workflow against the use cases below.
Teams that benefit from Che
Che is a strong fit when your team faces one or more of these situations:
-
New developers join regularly and need to be productive on day one.
-
Builds fail because of differences between developer machines.
-
Your organization requires credentials to stay on cluster infrastructure, not on individual machines.
-
Development must happen within a controlled network boundary, including air-gapped environments.
-
Projects have complex dependency chains that are difficult to reproduce consistently across developer machines.
What Che provides for the enterprise
- On-site control
-
Che runs within your Kubernetes cluster. When deployed on-site, your source code and credentials stay within your own infrastructure.
- Air-gapped deployment
-
Che operates in disconnected environments with mirrored container images and internal extension registries.
- Native Kubernetes integration
-
Che uses Kubernetes RBAC, OAuth, networking, and storage directly. No additional identity or access management layer is required.
- Open devfile standard
-
Workspace definitions use the devfile format, an open standard maintained by the devfile.io community.