What it does
Garden is a CLI automation tool for developing and testing containerized applications, especially Kubernetes stacks. Project configuration describes build, deploy, test, and run actions plus their dependencies; Garden can then execute that graph from a developer machine or CI. Its caching considers upstream dependencies, and sync mode lets developers update running services without repeating a full image build and deployment. Garden Core is open source, while some shared caching and remote build features use the separate Garden Cloud backend.
One project graph for development and CI
Garden's configuration describes how components are built, deployed, and tested, including dependencies between them. The quickstart begins with Docker and the Garden CLI, then uses an example project; a local Kubernetes installation is optional if the first goal is only to build images. For a deployment, garden deploy --sync builds and deploys the example to Kubernetes and opens the development console. The project includes unit and integration tests, which can be run from that console or with the CLI's test command.
Garden's action graph is useful when a test depends on several services: it can reuse a cached build or test result when the relevant inputs and upstream actions have not changed, then rerun downstream work when an upstream dependency changes. That same configuration can be called in CI to create preview environments or run tests, rather than keeping a separate set of development and pipeline instructions.
The Cloud boundary matters
Garden Core is a standalone CLI and the repository is licensed under MPL-2.0. The quickstart connects the project to Garden Cloud for team-wide caching and the Remote Container Builder, and requires an account for those features. A local Kubernetes deployment also requires a cluster; Garden documents a build-only path when Kubernetes is unavailable. Current pricing and plan boundaries for Garden Cloud were not established in the pages reviewed, so treat its hosted features separately from the open-source CLI.
Strengths
- The action graph links builds, deployments, and tests so downstream work can be reused or rerun according to dependency changes.
- Garden configuration can be used for local development and CI, including sync-mode development and preview environments.
- The CLI integrates with Kubernetes, containers, Terraform, Pulumi, and local scripts through providers and action types.
Watch out for
- The documented quickstart requires Docker; deploying the example additionally requires Kubernetes.
- Team-wide caching and the Remote Container Builder require connecting the project to Garden Cloud and creating an account.
Best for
- Kubernetes teams creating repeatable preview environments and integration-test stacks
- Platform engineers standardizing build, deploy, and test workflows across services
- Developers who want dependency-aware caching and live synchronization while testing a multi-service application
Sources
- What is Garden | Garden Docs (Oct 26, 2026)
- Quickstart | Garden Docs (Oct 26, 2026)
- GitHub - garden-io/garden: Automation for Kubernetes development and testing (Oct 26, 2026)