Terraform offers multiple workflows to manage infrastructure as code, but choosing the right one is key to achieving efficiency, scalability, and security. In this session, we’ll take a deep dive into the three core Terraform workflows — CLI-driven, VCS-driven, and API-driven — and explore how each fits different organizational needs and team structures.

We’ll start by breaking down what each workflow looks like in practice, from individual developer usage to large-scale automation. Using real-world examples and live demos, we’ll walk through how to configure and operate these workflows, what trade-offs to expect, and how to evolve from one to another as your infrastructure and team maturity grow.

This talk builds on my blog post “Which Terraform Workflow Should I Use? VCS, CLI, or API?” and expands on it with new content inspired by attendee feedback and hallway conversations from HashiConf 2025. We’ll review a comparison matrix highlighting differences in setup effort, maintenance overhead, security posture, and architectural complexity — helping you map Terraform workflows directly to your organization’s operational model.

By the end of the session, platform engineers, DevOps practitioners, and infrastructure architects will have a clear framework to evaluate and choose the most suitable Terraform workflow for their environment. Whether your goal is to empower developers with self-service infrastructure, standardize deployments through version control, or fully automate provisioning via APIs, this session provides practical guidance to balance flexibility, control, and compliance.

This has been one of the most popular sessions at HashiConf — and this year, it returns with updated insights, deeper technical examples, and fresh community-driven perspectives to help teams get the most out of Terraform’s workflow ecosystem.