Garden
Garden is an open-source Kubernetes-native development and CI/CD platform. Garden Core, a declarative CLI and engine, models a project as a graph of Build, Deploy, Test, and Run actions powered by pluggable providers (kubernetes, local-kubernetes, container, exec, jib, helm, terraform, pulumi). Garden Cloud / Garden Enterprise add a hosted control plane for remote container builds, ephemeral preview environments, team dashboards, team-wide caching, secrets, RBAC, audit, and SSO. The CLI integrates with any CI system and IDE; teams use Garden to standardize how dev, preview, staging, and prod environments are built and deployed.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Garden the way a machine reads it — 13 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Garden scores 20.9/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Garden
Each block below is one kind of artifact we hold for Garden. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Garden Core CLI
Open-source command-line tool and engine that turns a Garden project configuration into a graph of Build, Deploy, Test, and Run actions and executes them locally or against remo...
Garden Kubernetes Provider
Provider that connects Garden to remote Kubernetes clusters for builds (in-cluster), deploys (manifests, kustomize, helm), tests, and runs. The primary integration surface for p...
Garden Local Kubernetes Provider
Provider optimized for local Kubernetes distributions (minikube, kind, k3s, Docker Desktop) so developers can run the same Garden project against a workstation cluster.
Garden Container Provider
Provider for building, tagging, and publishing OCI container images used by other Garden actions.
Garden Exec Provider
Provider that runs arbitrary local commands as part of the Garden action graph, used for scripts, tooling, and shelling out to systems Garden does not natively model.
Garden Jib Provider
Provider that builds Java container images using Jib without a Docker daemon, integrated into the Garden action graph.
Garden Terraform Provider
Provider that lets Garden invoke Terraform stacks as part of an environment, wiring outputs into downstream Garden actions.
Garden Pulumi Provider
Provider that lets Garden invoke Pulumi programs as part of an environment, wiring outputs into downstream Garden actions.
Garden Cloud / Enterprise
Hosted Garden control plane providing remote container builds, ephemeral preview environments, team-wide caching, secrets management, RBAC, SSO, audit logging, and dashboards on...
Scroll within the panel for all 9 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Garden Io Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Garden Io Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Garden — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/garden-io · machine-readable index on apis.io