Spin up your development environment with one command. Your services are continuously built and tested as your code changes. Use the same toolset to develop containers, functions, and anything tomorrow might bring.
Develop and test rapidly whether your cluster is local or remote. Use shared dev clusters to scale out your dev environment as needed.
Develop in your private namespace, sharing build caches and test results with your team and CI.
Garden lets you run integration tests as part of the 'inner loop' of your development cycle, without stubbing or mocking services.
Catch bugs the moment they're introduced, not after waiting for a CI pipeline to finish. Then run exactly the same workflows in CI after you push your code.
Say goodbye to complicated bash scripts, manual stepping through READMEs and other unstructured workflows.
With the stack graph, each part of your system fully codifies its dependencies, and how to build, test and deploy itself—in a consistent, structured manner.
Garden then compiles the graph from your specs, even across multiple repositories.
With Garden, you can develop as rapidly against remote clusters as you can locally.
Use the editor you like, while Garden handles the heavy lifting in a remote development cluster. No more 'works on my machine': standardize the way your team develops code without sacrificing flexibility. Share a build cache and test results with the rest of your team, as well as your CI system.
Garden supports and works alongside industry-standard tooling—while remaining decoupled and pluggable—so you don’t need to worry about lock-in, compatibility, or future-proofing.
Garden imposes no runtime libraries, gateways or production systems.
Simply configure your stack graph next to your code, and enjoy improved developer experience, quality and collaboration across your organization.