What problems does Che solve?

When every developer configures their own local environment, differences in operating system versions, tool versions, and dependencies cause "works on my machine" failures. Che uses devfiles, declarative YAML files that define the exact tools, runtimes, and dependencies for a project. Every developer who opens the same repository gets an identical environment.

New team members must install tools, clone repositories, configure credentials, and troubleshoot build failures before writing their first line of code. With Che, a new developer opens the dashboard URL, pastes the team’s repository link, and has a fully configured workspace within minutes.

Local development environments store credentials on individual laptops. Che centralizes credential management through OAuth integration with Git providers and Kubernetes RBAC. Developer tokens are stored as Kubernetes Secrets on the cluster, not on individual machines.

Even teams that start with consistent environments drift as developers install different extensions, update tools independently, or modify configurations. Che rebuilds the workspace container from the devfile on each start, so the base toolchain is always consistent. The /home/user directory persists across restarts by default, preserving personal preferences and shell history without affecting the standardized tools and runtimes.

Complex projects with multiple microservices, databases, and build tools can overwhelm laptop hardware. Che runs workspaces on cluster infrastructure with configurable CPU, memory, and storage limits. Developers get the resources they need without upgrading their hardware.

Organizations in regulated industries need to control where code is developed and how it is accessed. Che runs entirely within your Kubernetes cluster and supports air-gapped environments with no internet access. In air-gapped deployments, all workspace traffic stays within your network boundary.