Okteto is an inner-loop development tool for Kubernetes. The core workflow is okteto up: it swaps a running pod’s container image for a language-appropriate development image, starts a bidirectional file sync between your working directory and the container, and opens an interactive shell plus port-forwards. You edit code locally, the container sees the changes instantly, and your app runs against real cluster dependencies without a Docker build, push, or redeploy on every iteration.
Development environments are described by an okteto.yml manifest that can reference existing Helm charts, Kustomize bases, Docker Compose files, or raw manifests, and declare a dev section per service that controls the sync, command, and forwarded ports. File synchronization is implemented on top of Syncthing, which gives it reasonable performance on large trees and across unreliable links. The okteto CLI is open-source and Apache-2.0 licensed; the company also sells a managed SaaS and a self-hostable product that layer on top with preview environments per pull request, multi-tenant namespaces, and SSO.
It occupies the same niche as Tilt, Skaffold, Telepresence, DevSpace, and Garden — all different takes on “stop waiting for CI and redeploys while iterating on a service inside a cluster”. Okteto’s distinguishing trait is the container-swap-plus-sync model rather than rebuilding images on every change.