Jumpstart your Internal Developer Platform
Why use Garden to build your Internal Developer Platform (IDP)?
When developing microservices, the cognitive load for a new developer to a team or project is very high. Not only does a developer need to set up their developer environment with the tools and scripts they'll need to contribute, they also need to coordinate with other teams to pull in any remote microservices they may call when testing a new feature or API.
The stack might contain a pre-configured Helm chart for a database, Terraform modules for infrastructure, Kubernetes manifests for services, and more, that teams can compose together to suit their needs. With Garden, you define any number of resources as infrastructure-as-code and services, then deploy them as one group, with one command: garden deploy.
Key features
Visualize your microservice stack, centralize logs, and view command history with the Garden dashboard
Pluggable repositories with remote sources
Create re-usable templates with Config Templates
If you're already familiar with Garden and just want to get going, click any of the links above to set up your features.
Navigate to Examples for a selection of pre-configured stacks you can use to quickly explore relevant features.
Resources
Pull in any number of remote repositories to collaborate across teams by setting up Remote Sources
Use Config Templates to vend development environments to all your developers
If you're coming from Docker Compose, visit our Migrating From Docker Compose guide
Join our Discord community 🌸 for access to Garden's dedicated Community Engineers and our AI chatbot 🤖 trained on our docs.
Further Reading
Examples
Last updated