
Run coding agents on Kubernetes.
Launch your coding agents on your cluster with Okteto's built-in orchestrator. Agents come preconfigured with skills and connectors that already know how to use Okteto. Each agent runs under the access, quotas and policies defined by the platform team.
Agents off laptops, onto your cluster
On a laptop, an agent runs with the developer's credentials and competes for the same machine. On Kubernetes, each agent runs with scoped credentials and network policies, from the same versioned image. Agents run in parallel, keep running after the laptop closes, and leave logs and audit events the platform team can review.
Why run agents on Kubernetes
Light and secure agent sandbox
Decouple the agent sandbox from the application environment. The agent is a binary that edits code and talks to Okteto to test the application. A standard unprivileged container is enough for the agent sandbox. It is reusable, fast, and easier to maintain because it doesn't need your application dependencies.
How to run agents on Kubernetes
Bring your own software factory
Already launch agents with your own software factory? Install the Okteto skill in your agents to create their application environments through Okteto. Because the environment layer stays independent, moving between software factories and our built-in agent orchestrator is simple.
Install the Okteto skill in your agent
Verified before review
The agent tests its change against running services, then opens a pull request with a preview environment you can share as a URL. Reviewers, including product managers, open the running application instead of reading only the diff. Share the same URL with customers to get feedback on a prototype.

Trusted by platform teams
"Okteto has been a game changer for our engineering team. We can spin up full-stack environments in minutes, reducing the time spent troubleshooting dev setup."
"PRs with sharable preview URLs was a total game-changer since it allowed developers to review changes without dependency matching and config and enabled teams outside of engineering from product, design, and sales to participate in the development process. This allowed us to shift left."
For the whole team

