Digger Rebrands to OpenTaco

Digger Rebrands to OpenTaco

Today, we're rebranding the Digger project to OpenTaco - an Open Toolkit for terraform automation. The company behind the OpenTaco project, however, continues to remain Digger (Digger HQ on Github). This will gradually be incorporated in all of the Digger project's existing marketing material and repositories, to reflect the same.

The decision to rebrand wasn't taken lightly. Over time, we've heard the same question again and again: is there an open-source, fully self-hostable TACOS tool built for the Terraform and OpenTofu ecosystem? OpenTaco is our answer to that.

While tools like Atlantis, and even Digger as it exists today, have paved the way for PR-based Terraform automation, we've learned from users that there are unavoidable limitations that are often encountered at scale, particularly around modularity, state management, and team-wide workflows.

OpenTaco aims to build on that foundation, offering a modern, scalable architecture designed so that teams never have to start with one tool and graduate to another. It's built to grow with you, from your first Terraform plan to your ten thousandth.

What does an Open Toolkit really mean?

What does an Open Toolkit really mean?

Simply put, it means that users need not use anything else with Terraform/OpenTofu to manage their infra.

The Open Toolkit is MIT licensed and allows users to use any version of Terraform/OpenTofu that they want to, aimed to make reduce the fragmentation in the community.

What Happens to Existing Digger users?

What Happens to Existing Digger users?

What Happens to Existing Digger users?

TL;DR No changes to your current setup. All existing Digger users will continue to get the same Terraform automation experience out of the box, nothing changes in how your automation works.

You’ll simply start seeing a new interface: OpenTaco, which replaces Digger Pro. You can log in right away using your existing Digger credentials, no new sign-up or setup required.

Ok, so whats new?

Ok, so whats new?

Ok, so whats new?

One of the most significant additions in OpenTaco is Units: a new way to organize and manage your Terraform or OpenTofu automation.

With Units, users now have the option to have their Terraform state managed by OpenTaco. It works as a drop-in replacement for the standard backend setup, fully compatible with both Terraform and OpenTofu CLIs. You can use it out of the box, with the same familiar workflow:

terraform {

cloud {

hostname = “your-hostname”

organization = “your-org”

workspaces {

name = “your-workspace-name”

}

}

}

  • Once configured, you can log in just as you would with Terraform Cloud:

terraform login otaco.app

Why We Built It

Why We Built It

Managed state has been one of the most requested features since Digger’s early days. But we also heard from users who prefer the simplicity and control of an S3 or GCS backend. So instead of forcing a choice, we built Units on top of a separate service called Statesman, which internally uses the same bucket layout as your existing backend.

That means when you self-host OpenTaco, you don’t have to migrate or restructure your state. Just point it to your existing bucket, and everything continues to work.

What are we trying to accomplish here?

What are we trying to accomplish here?

1. Encouraging more Terraform and OpenTofu usage, not less.

We want to make it easier, faster, and cheaper for users to run Terraform or OpenTofu, at any scale. The more infrastructure as code gets written, the more we all benefit.

2. Reducing fragmentation.

The community shouldn’t have to pick sides between Terraform and OpenTofu. Our vision is to provide one open, self-hostable platform where users can choose whichever they prefer and still work seamlessly together.

We’re not fully there yet, but OpenTaco is a step toward that future.

3. Enabling a Jevons paradox moment for infrastructure.

The easier and cheaper it becomes to run Terraform, the more infrastructure will be created. AWS provider downloads recently crossed 5 billion, and most of that growth came in the last few years. As AI agents and automation tools start generating more Terraform than humans ever have, we need resilient, open infrastructure to support it.

Try it now and let us know what you think. The engine is battle tested, the new stuff is, well, new. We’d love feedback on it all!

Join our Slack community

Get exclusive content and become a part of the OpenTaco community

Join our Slack community

Get exclusive content and become a part of the OpenTaco community