Build your software factory, not the plumbing.
Okteto gives platform teams the environment layer every internal platform needs: environments as code, remote builds and tests, secrets, endpoints, cost controls and governance. On your Kubernetes, ready for developers and coding agents.
Runs anywhere Kubernetes runs: EKS, GKE, AKS, Nutanix NKP or bare metal.
Every software factory needs an environment layer.
Agents can write the code. Something still has to build it, deploy it, test it and clean it up, safely and at scale. That part is where internal platforms stall.
Option 1
Build it yourself
Helm wrappers, namespace scripts, secret plumbing and cleanup jobs that only one person understands. It works until the tenth service, or the hundredth agent.
Option 2
A fat VM per agent
Every agent gets a privileged VM with dockerd, every image and every credential inside. Expensive, slow to start and nothing like your production setup.
Best option
Okteto as the environment layer
Plug proven building blocks into the portal, pipelines and agents you already run. Keep your agent vendor. Make the environment layer yours.
One platform for everyone who ships code.
Define environments once. Developers, coding agents, CI and reviewers all get the same production-like environments, under the same policies.
Developers.
Self-service, production-like environments in a click, with the IDE and tools they already use. No Kubernetes expertise required.
Coding agents.
A tiny sandbox with the Okteto CLI and a token. Okteto deploys, tests and cleans up in the cluster, for any agent: Claude Code, Codex, Cursor, Copilot or your own.
Reviewers and product teams.
A preview environment on every pull request, with a live URL anyone can open before the merge.
Test and release engineers.
Realistic environments with real data, tests that run inside the cluster and faster QA cycles before every release.
Building blocks for every environment.
Environments as code
The Okteto Manifest sits on top of your Helm charts, Kubernetes manifests or Docker Compose files and defines how to build, deploy, develop and test.
Remote builds, deploys and tests
Builds run in the cluster with BuildKit and smart builds skip images someone already built. Deploys and okteto test run remotely too, so sandboxes stay small.
Automatic HTTPS endpoints
Every HTTP service gets its own HTTPS URL with a wildcard certificate, so agents can exercise the app and people can review it from any browser, on any device.
External resources
Databases, queues, buckets and serverless functions your app depends on are provisioned with each environment, on your cloud, and torn down with it.
Building blocks to run it at scale.
Hundreds of environments an hour, from developers and agents, in one cluster. Okteto handles the parts that break first.
Secrets and credentials
Variables are injected only at deploy and test time, masked in the logs. OIDC for AWS and GCP, central registry credentials and scoped Kubernetes access.
Divert
Deploy only the services a task changes and route everything else to a shared environment. Forty microservices, one deploy, and no extra cluster to pay for or keep running.
Resource manager
Okteto measures what each container actually uses and right-sizes its CPU and memory requests automatically, so a busy cluster doesn't need to be three times the size.
Garbage collector
Idle environments go to sleep and are deleted later, on windows you configure for development and previews, so nobody has to remember to clean up after a task.
Visibility and control for the platform team.
Okteto Dashboard
One place for users, namespaces, nodes, running previews and secrets, with the controls to manage capacity, quotas and access.
Catalog
Publish pre-configured, launch-ready application environments that anyone on the team, or any agent, can deploy in a single click.
Preview environments
A full environment on every pull request, from GitHub, GitLab or any CI system, with a live URL, and removed on merge.
Platform insights
Usage data through the API: adoption, build and deploy times and where to optimize next. Run your platform like a product.
Platform teams build on Okteto
"DevX has transformed our development process, becoming a cornerstone of our platform. It's now recognized as being a first-class construct inside the organization. This was not even considered before Okteto. Now it's the first thought."
"DevX and a developer platform is the biggest initiative I'm trying to promote in my company. It’s all about having a centralized piece of infrastructure where you can go and create new services, understand knowledge bases and know where to see ownership of things."
Software factories
Use any agent vendor. Keep the environment layer independent.
Questions platform teams ask
No. Okteto is the environment layer underneath your portal, pipelines and agents. They call Okteto through the CLI and API to create, test and destroy environments.
Any agent that can run a command. The sandbox only needs the source code, the Okteto CLI and a token, so you can change agent vendors or sandbox runtimes without touching the environment layer. See how Okteto works with coding agents.
No. The Okteto Manifest builds on the Helm charts, Kubernetes manifests and Docker Compose files you already maintain. There is no second definition of your application to write.
Divert deploys only the services that change, the resource manager right-sizes requests to actual usage, and the garbage collector puts idle environments to sleep and deletes them on a schedule.
Yes. Okteto runs in your own cloud account (BYOC) or on your own Kubernetes clusters (Self-Hosted). Your code, images, environments and data never leave your infrastructure.
Under BYOC, Okteto operates only a monitoring and control plane, and it holds no customer data and no PII. Okteto is SOC 2 Type 2 audited and pen-tested every year.
Anywhere Kubernetes runs: managed clusters like EKS, GKE and AKS, Nutanix NKP, or your own clusters on bare metal. With BYOC on AWS or GCP, Okteto runs in your own cloud account.