Test better, deliver faster.
Let's get started.
Free
Start now, no credit card needed
PLAN DETAILS
- Up to 3 users per organization
- Includes 200 compute minutes & 32GB layer cache for Remote Container Builder
- Cache retention: 7 days
- Log retention: 10 days
- UI Insights retention: 30 days
FEATURES
- *NEW* Accelerate container builds with the Fully managed and integrated Remote Container Builder
- *NEW* Track build trends & logs in the Builds dashboard
- *NEW* Invite users to Garden Cloud organizations for easy collaboration
- Use one tool for rapid development and CI automation
- Integrate your builds, deploys and tests in one framework: the Stack Graph
- End "works on my machine" problems with production-like environments for every stage
- Accelerate end-to-end testing by running tests in on-demand, realistic environment
- Iterate faster on code by live syncing code into running containers and environments
- Codify your in-house practices with templates, custom commands and workflows
- Integrate with platforms and tools including Docker, Kubernetes, Terraform, Pulumi, custom scripts and more
Support
- Community support from Discord
- Free tutorials, videos and guides
- Garden is built on an open core
Team
Starting at $50/month per user
PLAN DETAILS
- Includes 1000 build minutes/month per user & 128GB layer cache for Remote Container Builder
- Cache retention: 30 days
- Log retention: 30 days
- UI Insights retention: 90 days
Everything in Free, plus:
Support
- Community support from Discord
- Free tutorials, videos and guides
Enterprise
A powerful solution for platform teams
PLAN DETAILS
- Unlimited users
- Unlimited access to Remote Container Builder with pricing tailored to your usage needs
- Fully configurable & unlimited retention
Everything in Team, plus:
Support
- Hands-on onboarding support and training with our team of experts support and training with our team of experts
- Multiple SLA options options
- Dedicated account manager
FAQ
What's the difference between Garden Free, Team, and Enterprise?
All of Garden’s plans are built around the open source Garden Core CLI, with a web dashboard collecting insights and providing a space to collaborate.
All plans also include Garden’s Remote Container Builder, which provides on-demand compute resources for building environments.
The Team and Enterprise tiers are priced per seat and bundled with more monthly build minutes than free plans, and offer longer retention for logs, cache, and UI insights.
All plans also include Garden’s Remote Container Builder, which provides on-demand compute resources for building environments.
The Team and Enterprise tiers are priced per seat and bundled with more monthly build minutes than free plans, and offer longer retention for logs, cache, and UI insights.
How does pricing work?
Garden is priced per seat, starting at $50/user per month. Each plan comes bundled with a monthly allotment of build minutes, and additional compute can be purchased ala carte.
What are Build Minutes?
Container Builder allows you to perform container builds on high-performance build instances that we manage for you. Build minutes are the minutes of non-idle time counted per builder instance. A builder instance is not idle when it performs one or more container builds in a given minute. Different sizes of builder consume different amounts of minutes: as a general rule, the consumed minutes equals to the number of minutes used by the Builder multiplied by the number of CPUs.For example:
- a small (1vCPUx2GB) builder running for 1 minute consumes 1 Build Minute.
- a XL (16vCPUx32) GB builder running for 1 minute consumes 16 Build Minutes.
**Multi-platform builds**
We currently support building for linux/amd64 and linux/arm64 platforms. When running Garden commands that simultaneously execute builds on multiple platforms, one native build instance for each platform will be utilised, and Build Minutes are counted separately for each builder instance.
- E.g. running a 2 minute build for linux/amd64 and linux/arm64 on a 16vCPUx32GB builders, will consume 2 * 16 * 2 (# of minutes * # of CPUs * # of platforms) = 64 Build Minutes.
**Build Minutes limits**
The total sum of Build Minutes accrued monthly in the UTC time zone counts towards the organization-wide limit for Build Minutes, defined in the currently active plan. When the number of utilised minutes exceeds the number of minutes included in the plan, Garden will fall back to performing the build locally.
Under the Team plan, the organization's total Build Minutes allocation is calculated as 1,000 Build Minutes per user. These minutes are collectively pooled and may be arbitrarily distributed among all users. For instance, an organization with seven users under the Team plan will have a total of 7,000 Build Minutes available. The allocation of these minutes is flexible, allowing one user to utilize 4,000 minutes while the remaining users share the balance as needed.
### What is considered a cache hit
A cache hit occurs when Garden Core queries Garden Cloud to check if an action has been executed before and an action result is retrieved from the org-wide cache. Actions that affect the cache-hit count can be, but are not limited to, Test actions or Run actions. Cache-hits count towards the monthly organization-wide limit for Cache-hits.
- a small (1vCPUx2GB) builder running for 1 minute consumes 1 Build Minute.
- a XL (16vCPUx32) GB builder running for 1 minute consumes 16 Build Minutes.
**Multi-platform builds**
We currently support building for linux/amd64 and linux/arm64 platforms. When running Garden commands that simultaneously execute builds on multiple platforms, one native build instance for each platform will be utilised, and Build Minutes are counted separately for each builder instance.
- E.g. running a 2 minute build for linux/amd64 and linux/arm64 on a 16vCPUx32GB builders, will consume 2 * 16 * 2 (# of minutes * # of CPUs * # of platforms) = 64 Build Minutes.
**Build Minutes limits**
The total sum of Build Minutes accrued monthly in the UTC time zone counts towards the organization-wide limit for Build Minutes, defined in the currently active plan. When the number of utilised minutes exceeds the number of minutes included in the plan, Garden will fall back to performing the build locally.
Under the Team plan, the organization's total Build Minutes allocation is calculated as 1,000 Build Minutes per user. These minutes are collectively pooled and may be arbitrarily distributed among all users. For instance, an organization with seven users under the Team plan will have a total of 7,000 Build Minutes available. The allocation of these minutes is flexible, allowing one user to utilize 4,000 minutes while the remaining users share the balance as needed.
### What is considered a cache hit
A cache hit occurs when Garden Core queries Garden Cloud to check if an action has been executed before and an action result is retrieved from the org-wide cache. Actions that affect the cache-hit count can be, but are not limited to, Test actions or Run actions. Cache-hits count towards the monthly organization-wide limit for Cache-hits.
Do you offer special deals for startups or nonprofits?
Yes! We offer reduced per-user pricing for early-stage companies and nonprofits. Simply get in touch with us to learn more.