What is Burrito used for?

Burrito is a Kubernetes operator for Terraform that continuously plans and applies infrastructure code and shows state changes in a web UI. It is a good fit for Terraform automation without custom CI pipelines and detecting configuration drift in Kubernetes-based setups.

Is Burrito open source?

Yes. Burrito is open source under the Apache-2.0 licence. Its source code is on GitHub at padok-team/burrito and is written mainly in Go.

Yes. Burrito is open source, so the software itself is free to use.

Can I self-host Burrito?

Yes. Burrito can be self-hosted on your own server or infrastructure.

What is Burrito an alternative to?

Burrito is an open-source alternative to HCP Terraform, Spacelift, env0 and Scalr. Other open-source alternatives to HCP Terraform include Atlantis, Semaphore UI and OpenTofu.

Is Burrito actively maintained?

Yes. The most recent commit to Burrito was on 2 October 2026, and the latest release is v0.14.1, published on 29 September 2026. The project has 756 stars on GitHub.

Burrito: open-source alternative to HCP Terraform, Spacelift

About Burrito

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.

Key features

Continuous Terraform plans and applies
Drift detection for infrastructure state
Pull and merge request integration
Web UI for state changes
OpenTofu and Terragrunt support
Kubernetes operator deployment

Good fit for

→Terraform automation without custom CI pipelines
→Detecting configuration drift in Kubernetes-based setups

Built with: Go; Kubernetes
Tags: terraform; kubernetes; operator; tacos; infrastructure-as-code; opentofu; gitops; golang

Burrito: questions and answers

What is Burrito used for?: Burrito is a Kubernetes operator for Terraform that continuously plans and applies infrastructure code and shows state changes in a web UI. It is a good fit for Terraform automation without custom CI pipelines and detecting configuration drift in Kubernetes-based setups.
Is Burrito open source?: Yes. Burrito is open source under the Apache-2.0 licence. Its source code is on GitHub at padok-team/burrito and is written mainly in Go.
Is Burrito free?: Yes. Burrito is open source, so the software itself is free to use.
Can I self-host Burrito?: Yes. Burrito can be self-hosted on your own server or infrastructure.
What is Burrito an alternative to?: Burrito is an open-source alternative to HCP Terraform, Spacelift, env0 and Scalr. Other open-source alternatives to HCP Terraform include Atlantis, Semaphore UI and OpenTofu.
Is Burrito actively maintained?: Yes. The most recent commit to Burrito was on 2 October 2026, and the latest release is v0.14.1, published on 29 September 2026. The project has 756 stars on GitHub.