DeployelmIntroductions to CI/CD and deployment platforms

GitOps and Kubernetes delivery

What is Garden? An introduction to the DevOps automation tool for Kubernetes apps

By the Deployelm editorial team · Published · Updated

Garden is a DevOps automation tool for developing and testing Kubernetes apps. It can spin up production-like environments on demand for development, testing and CI. It uses the same configuration and workflows across every stage of software delivery.

Tool
Garden
Made by
Garden
Official site
garden.io
Category
GitOps and Kubernetes delivery

Who makes Garden

Garden is made by Garden, which also operates Garden Cloud, the service that connects to project repositories.

The official website is linked below this page.

Official website: garden.io

What Garden is for

Garden is for developing and testing Kubernetes apps faster. Its central idea is that a production-like environment can be created on demand, so work is not limited to a few shared, long-lived environments. These environments can be used for development, testing and CI.

Using the same configuration and workflows across every stage of software delivery means a setup defined once applies from a developer's machine through to CI.

Garden documents several use cases: isolated on-demand preview environments, portable CI pipelines, local development with remote clusters, and jumpstarting an Internal Developer Platform.

Who Garden is for

The vendor names teams developing and testing Kubernetes apps, and developers. It is aimed at the inner loop of building and testing as much as at the delivery pipeline, so individual developers and the teams around them are both in scope.

Notable capabilities

Garden's capabilities cover environments, workflows and caching. Each is described below.

  • On-demand environments: Garden can spin up production-like environments for development, testing and CI.
  • Consistent configuration: the same configuration and workflows are used across every stage of software delivery.
  • Smart caching: builds and test runs are sped up through caching.
  • Workflows: these define CI-like sequences of Garden commands and script steps, and can be run from the command line, in CI pipelines, or triggered from PRs or branches via Garden Cloud.
  • Execution control: workflow steps can use when and skip fields to control execution, including error handling.
  • PR and branch triggers: Garden Cloud can monitor a project repository and trigger workflows on PR and branch updates.
  • Action versioning: Garden calculates a version for each action from source files, configuration and upstream dependencies to decide what to rebuild or re-run.
  • Team Caching: cache versions are stored in the Garden Cloud backend and shared across a team and CI runs. It is enabled automatically once a project is connected to Garden Cloud.

How Garden fits GitOps and Kubernetes delivery

Within GitOps and Kubernetes delivery, Garden works mainly before and around deployment. It covers building, testing and previewing Kubernetes apps in realistic environments, and it can run its workflows inside CI pipelines.

In the wider field of CI/CD and deployment platforms, this puts Garden closer to development and test automation than to release promotion. Because its workflows can run from the command line, from CI pipelines or from Garden Cloud triggers, teams can adopt it alongside existing CI rather than as a standalone replacement for it.

Frequently asked questions

What is Garden used for?

Garden is used for developing and testing Kubernetes apps. It can spin up production-like environments on demand for development, testing and CI, and it speeds up builds and test runs through smart caching.

Who develops Garden?

Garden is made by Garden. The official website is https://garden.io/.

How do Garden workflows run?

Workflows define CI-like sequences of Garden commands and script steps. They can be run from the command line, in CI pipelines, or triggered from PRs or branches via Garden Cloud.

How does Garden decide what to rebuild?

Garden calculates a version for each action from source files, configuration and upstream dependencies. It uses that version to decide what to rebuild or re-run.

Does Garden support preview environments?

Yes. Garden documents isolated on-demand preview environments as a use case.

Sources. This introduction is based on the vendor's official pages, checked on 21 November 2026 (Asia/Dhaka):

Deployelm is independent and is not affiliated with Garden. Product names belong to their owners. Features change; confirm details on the official website.