Open-source HCP Terraform alternatives

OpenTofu is an open-source infrastructure tool for creating, modifying and versioning resources with safety and efficiency in mind. You describe infrastructure in a high-level configuration language, so a blueprint of your environment can be versioned and shared like other code. It can work with established cloud and service providers and with custom in-house platforms. It is written in Go and released under the MPL-2.0 license. It is widely understood as a community continuation of Terraform's open-source code.

Its key features are infrastructure as code, execution plans that preview what an apply will do, a resource graph that parallelizes work on independent resources, and change automation that applies complex changesets with little manual effort. Nightly builds are available. The community uses GitHub Discussions, the opentofu channel on the CNCF Slack, regular community meetings and a Technical Steering Committee.

Semaphore UI is a web interface for managing DevOps tooling when running commands from a terminal no longer scales. It lets teams run Ansible playbooks, Terraform and OpenTofu code, and Bash and PowerShell scripts from a shared place with controlled access and notifications about failed tasks.

Work is organized into projects, with reusable task templates that can be run on demand or on a schedule. Inventories describe the target hosts, and variable groups hold environment variables and secrets for tasks to use. An API allows automation, and a Postman collection plus documentation are provided. Its repository topics place it in the same space as AWX and Jenkins.

Semaphore is written in Go and licensed under MIT. The most common installation method is Docker, but it is also available as a Snap, as Debian or RPM packages, as a plain binary, or as a pre-built virtual machine from marketplaces such as AWS, DigitalOcean and Vultr. An online demo is available for trying it out.

Atlantis is a self-hosted application written in Go that automates Terraform through pull requests. It listens for pull request events delivered by webhooks, runs terraform plan, import and apply on a server, and then comments the output back on the pull request.

Moving these steps into the review flow makes Terraform changes visible to the whole team and lets engineers who are not operations specialists collaborate on infrastructure. It also helps standardize how Terraform is run, since everyone's changes go through the same remote workflow rather than from individual laptops. The project documents a getting-started guide, full documentation and release downloads, and community help comes through Slack.

Atlantis is licensed under Apache-2.0 and you run it yourself, which is why it is often grouped with Terraform automation and collaboration tools. It suits platform and SRE teams managing infrastructure as code with a Git-based review workflow.

Burrito is a TACoS (Terraform Automation and Collaboration Software) Kubernetes operator, summed up by its authors as Argo CD for Terraform. It targets the lack of built-in tools for managing state drift in Terraform, the difficulty of building CI/CD pipelines for it, and the lack of an easy way to see how state changes.

It plans your Terraform code continuously and runs applies when needed, offers a pull request or merge request integration so teams do not have to write Terraform pipelines, and presents state modifications in a simple web UI. The topics also list OpenTofu and Terragrunt support. Documentation is published at docs.burrito.tf, and conference talks and blog posts describe the design and the challenges it solved.

The project is still pre-release, so minor versions can introduce breaking changes before 1.0, and users should install tagged releases rather than the main branch. Burrito is written in Go, licensed under Apache-2.0, runs inside your own Kubernetes cluster and is maintained by Theodo Cloud.