Host apps and websites, spin up Sandboxes, manage domains, run tests, deploy to any cloud, and automate delivery with pipelines, all in one platform. Configure everything through the UI, YAML, or code, or let Claude Code, Cursor, Copilot, and other AI agents operate Buddy directly through MCP or CLI, including deployments, infrastructure, and logs.
This is the 8th launch from Buddy Works. View more

Terraform Automation by Buddy
Launching today
Run Terraform and OpenTofu in Buddy with dedicated actions for planning, applying changes, and detecting infrastructure drift. Review readable resource diffs, require approval before destructive changes, and apply exactly the plan that was reviewed. Manage state in Buddy, queue runs to prevent concurrent applies, and automate scheduled drift checks to catch changes made outside Terraform or OpenTofu.







Free Options
Launch Team

Render: Get up to $100K in startup creditsCloud infrastructure for founders who want to move fast and NOT break things
Promoted




How do approvals work? Can I require two approvers for prod?
@darek_sztwiorok The approval step sits between Terraform Plan and Terraform Apply, so someone can review the diff before any changes are applied. You can require approval from specific users or groups, and prevent the person who started the run from approving it. You can also require approval only for risky plans, such as those that destroy resources.
Requiring two approvers isn’t possible yet, but we’re planning to add it soon. Good note, thanks!
Can I run different Terraform environments, like staging and production, with separate configurations?
@tprus Yes, you can manage staging and production using separate Terraform workspaces or state backends, with environment-specific variables and configurations. You can also use separate Buddy pipelines to control how changes are planned, approved, and applied in each environment. You will find more details here: https://buddy.works/docs/terraform/workspaces-and-environments
Applying exactly the plan that was reviewed closes a gap I’ve been bitten by. When drift detection finds a change made outside Terraform, does Buddy open a plan to revert it, or just alert?
@heysaloni It’s flexible and depends on how you configure your workflow. After drift is detected, you can either send yourself an alert or add a Plan action that will bring your infrastructure back to the state defined in your code.
Where is the state stored? Is it secure?
@bartshoot State can be stored in Buddy artifact with full access control and state locking to keep your state secure. You can also keep it in your own backend, such as S3 or GCS.