// the find
tilt-dev/tilt
Define your dev environment as code. For microservice apps on Kubernetes.
Tilt is a dev environment orchestrator for Kubernetes-based microservice stacks. You define your services in a Tiltfile (Starlark/Python-ish DSL), run `tilt up`, and it watches files, rebuilds images, and syncs changes to your cluster — with a terminal UI showing status across all services. It's aimed at teams who already live in Kubernetes and are tired of writing bespoke watch scripts.
Live Update is the genuinely good part: it syncs changed files directly into running containers without a full image rebuild, which makes the edit-reload loop actually fast for interpreted languages. The Tiltfile DSL is expressive enough to handle real multi-service dependencies without becoming a maze — you can express 'build B after A is healthy' cleanly. Integration test coverage is unusually thorough for a dev tooling project; the /integration directory has end-to-end tests for live update, CRDs, job failures, namespace flags, and more. Extensions ecosystem (tilt-extensions repo) means common patterns like Helm, Docker Compose, and kind registry setup are already packaged and don't need to be hand-rolled.
The Starlark config language looks approachable but has a steep learning curve once you hit anything non-trivial — error messages from Tiltfile evaluation are often cryptic and don't point you to the line that matters. It's deeply coupled to having a local Docker daemon and a working kubeconfig; if your team uses remote clusters or non-standard auth (OIDC, exec plugins), you'll spend time debugging Tilt's assumptions before you debug your actual code. Now under Docker Inc. ownership, which raises obvious questions about long-term direction — the repo is active but the strategic roadmap is opaque. Resource consumption is non-trivial: running Tilt alongside a multi-service local cluster will saturate a laptop that would otherwise handle it fine.