Skip to content
GantryCD

Overview

GantryCD is a control plane for teams running OpenTofu across repositories, environments, and cloud accounts. It is built around three pillars:

  • An OpenTofu execution platform. GantryCD plans, applies, refreshes, and destroys infrastructure on runners you control. Each run receives short-lived credentials and the settings defined for its stack.
  • Centralized control for infrastructure operations. Stacks, access, cloud connections, variables, reviews, and deployment history live in one place. Teams follow the same process without sharing broad credentials.
  • Dependency-aware operations at scale. GantryCD maps relationships between stacks, shows the effect of a change, and can start downstream deployments after their dependencies change.

Most changes follow the same path:

  1. A change reaches a tracked branch or pull request.
  2. A runner creates an OpenTofu plan.
  3. The team reviews the result and any required checks.
  4. GantryCD applies the saved plan after approval.

The main terms used in this guide are:

  • A stack connects a repository and OpenTofu directory to its state, variables, cloud access, and runner choice.
  • A deployment is one attempt to plan, apply, refresh, or destroy a stack.
  • A run is one command within a deployment.

Continue with Core concepts, then read Stacks and Deployments for the main workflow. The rest of the guide is grouped by the work you are doing. For larger setups, the Terraform provider and stacks-of-stacks pattern keep GantryCD configuration in code.