TTerramantle
Get Started Free
Disambiguation

Terramantle vs Terramate.

One letter apart, two different tools. If you landed here looking for one and found the other, this page sorts out which is which. Short version: Terramate orchestrates your Terraform, Terramantle distributes your modules. You can happily use both.

Two jobs

They solve different problems.

The names collide, the products do not. Terramate is an orchestration and automation platform for Terraform and OpenTofu. Terramantle is a registry for modules, providers, and state. Neither is a worse version of the other, they are answers to different questions.

Terramate
  • Orchestrates commands across stacks with a dependency graph.
  • Change detection, so you only run stacks that actually changed.
  • Drift detection and reconciliation.
  • GitOps workflows on top of your existing CI/CD.
  • Does not host or distribute modules.
Terramantle
  • Hosts and versions your modules and providers.
  • Hosts Terraform state with locking.
  • Keyless OIDC publishing, supply-chain scanning.
  • A dependency graph across repos for blast radius.
  • Does not orchestrate or run your Terraform.
Together

You can run both, and it makes sense to.

Because they occupy different layers, they compose cleanly. Terramate decides what to run and in what order; the stacks it runs pull their modules and providers from Terramantle, and write state to it. One handles execution, the other handles distribution. There is no conflict to resolve, and adopting one does not rule out the other.

Sorting out the confusion

Is Terramantle the same thing as Terramate?

No. They are different products, one letter apart, and they do different jobs. Terramate orchestrates your Terraform: stacks, execution ordering, change and drift detection, GitOps workflows. Terramantle is a registry: it hosts and distributes your modules, providers, and state. You can use both, they do not overlap.

Do they compete?

Not really. Terramate decides what to run and in what order across your stacks. Terramantle is where the modules and providers those stacks consume come from. A team could run Terramate for orchestration and pull its modules from Terramantle in the same pipeline.

Which one do I need?

If your problem is "running Terraform across many stacks is slow and I cannot see drift", that is Terramate. If your problem is "distributing and governing modules and providers across teams, with versioning and supply-chain scanning", that is Terramantle. If you have both problems, use both.

Does Terramantle do orchestration or drift detection?

No. Terramantle is deliberately a registry and state layer, not an execution platform. It does not run your Terraform, orchestrate stacks, or detect drift. If you want those, Terramate or a TACOS is the right tool, and Terramantle sits underneath supplying the modules.

Last reviewed