Announcement · Turf 1.0
Turf™ is a self-hosted, autonomous infrastructure-as-code tool, built on OpenTofu™. It deploys the stack an AI factory runs on and keeps it that way, with an agent overseeing.
Turf is free for noncommercial use under PolyForm Noncommercial 1.0.0. Companies can evaluate Turf free for 60 days and license it for production at turf.build/licensing.
What Turf is
Turf’s operating model is the Terraform® plan: every change is planned, reviewed and approved before it runs, the engine carries it out and the agent oversees it, so governance and autonomy are the same feature. Turf takes an AI factory from pools of inventory to a GPU cluster that has passed NVCRE certification, on managed Kubernetes® or bare metal, and runs day 2 on the provider’s runbook: re-certify on change, replace a failed node, upgrade, retire.
Under the plan is Turf’s new engine, built for the scale and the multi-round shape of that stack. It runs on Restate — in Restate’s words, “a lightweight runtime to turn AI agents, workflows, and backend services into durable processes”: every step of a run is journaled as it happens, so an interrupted run resumes where it stopped, a plan waiting for approval holds no process, and a rollout outlives the conversation that started it. On top, agents drive the plan over MCP, and the provider’s own control plane does the same. NVIDIA has shipped AI Cluster Runtime (AICR) 1.0 and says itself that it is “not a cluster provisioner or lifecycle management system”: you bring the cluster and the deployment tooling. Turf is what takes the cluster the rest of the way.
The plan tells the agent what is possible; the agent decides what happens.
Four things, each shown rather than claimed.
Durable per-resource state instead of one file and one lock. Layered stacks, a cluster and then the runtime on it, converge in one run and tear down in the right order. An interrupted run picks up where it stopped; a plan waiting for approval holds no process.
watch a stack converge →Reviewed and approved before it runs. Policy with the tools you already have: the plan exports for OPA, and a hard-mandatory rule stops it before the apply. Agents drive the plan over MCP, and so does the platform you already run.
a policy the agent can’t approve its way past →Terraform providers and modules, Ansible® playbooks, Helm® charts, each as it is. Day 2 as planned Terraform actions, with lifecycle triggers and failure handling.
what each one carries →A golden recipe, one convergence loop, day 2 on the runbook: a neocloud from pools of inventory to NVCRE certification and a served model, on managed Kubernetes or bare metal. Seventeen pages, free.
read the paper →The same engine runs every stack, on a workstation or in the cluster.
Nothing in this stack is written from nothing. Terraform providers and modules, Ansible playbooks and Helm charts already cover it, and Turf runs each as it is.
7,388 providers and 24,728 modules on the public registry reach clouds, bare-metal services, switch fabrics, storage arrays and Kubernetes. Modules package them into golden recipes.
4,568 collections on Ansible Galaxy cover what no API reaches: drivers, firmware, kernel settings, switch operating systems, Kubernetes on bare metal. A playbook runs as a Terraform action.
18,096 charts on Artifact Hub are how the runtime ships: the GPU Operator, NVSentinel, KAI Scheduler, Kubeflow Trainer. A chart installs as a Terraform resource.
Counts as of Metal to Tokens, October 2026. Day 2 is Terraform actions too: a lifecycle trigger runs the host playbook after a node is created, waits on a Kubernetes condition, or re-certifies after a change, and a failure halts the run or taints the resource, as the trigger says.
encryption block with a passphrase or key
protects the statefile; migrating an existing state is a no-op run.mise.toml beside the
configuration pins the tools a plan calls, and the engine refuses one you haven’t trusted./turf:guide,
/turf:up and /turf:destroy, and six guided journeys, from
deploying AICR to day-2 node maintenance, a product that installs itself, promotion across
environments, a TACO as the control plane, and guardrails. Any MCP client connects in one
command.turf setup and a Claude Code plugin, so the connect step is one command inside
the agent; driving Turf from other agents over the network; provider skills that encode a
provider’s own rules; and the saved-planfile round-trip, which shipped in 1.3.
A download, no form, no login. Free for noncommercial use. Commercial use, including a company’s internal use, requires a license, and companies evaluate Turf under a free 60-day pilot on a standard contract.
NVIDIA, AI Cluster Runtime, NVCRE, NVSentinel and KAI Scheduler are trademarks or product names of NVIDIA Corporation, referred to here only to describe interoperability. Turf is not affiliated with, endorsed by, or sponsored by NVIDIA. Restate is a product of Restate Software, Inc. and Restate GmbH, named here to describe what Turf is built on; Turf is not affiliated with or endorsed by Restate. All other marks belong to their owners.