Terramate

What Is Terramate?

Terraform sprawl is a problem most infrastructure teams recognise once they hit it. A project that started as a handful of .tf files grows into dozens of environments, each with near-identical backend configuration copied and pasted between directories. Someone eventually asks a reasonable question: why does updating a provider version require editing the same block in forty places? Terramate was built as a direct answer.

The timing matters too. HashiCorp's 2023 licence change on Terraform, which pushed the community fork OpenTofu into existence, left many teams re-evaluating not just which IaC engine to run but how to orchestrate it. A new generation of CI/CD and orchestration tools emerged in that gap. Terramate is one of the few built from the start to treat Terraform and OpenTofu as equals, rather than bolting OpenTofu support onto an existing Terraform-only product.

The company was founded in Berlin in 2023 by Sören Martius and Marius Tolzmann, who had previously run a separate company, Mineiros GmbH, working in the same infrastructure-as-code space. Terramate GmbH is a distinct legal entity from Mineiros, registered with €25,000 in share capital, and has since raised funding from investors including Fly Ventures, Crowberry Capital, D11Z.Ventures, SIBB, and NAP Berlin.

Terramate ships two things. The Terramate CLI is open source under the Mozilla Public License 2.0, and it handles code generation, orchestration, and change detection entirely on your own machine or CI runner — no cloud account required. Terramate Cloud is the optional paid layer on top, adding observability dashboards, DORA metrics, drift alerts, and incident management. Critically, everything the CLI generates is plain Terraform or OpenTofu HCL, so nothing about your actual infrastructure code becomes locked to Terramate.

Key Features

Code Generation That Kills Copy-Paste

Terramate's compiler generates HCL, JSON, or YAML from reusable templates and "globals" — values you can define once and override at any level of your project's directory hierarchy. Instead of manually keeping backend blocks or provider configuration synchronised across dozens of environments, you define the pattern once and let Terramate produce consistent, native code everywhere it's needed. Because the output is standard Terraform syntax, nothing downstream needs to know Terramate was involved.

Stacks as the Unit of Deployment

A Terramate stack is any directory containing a small configuration file, typically representing one deployable unit of infrastructure with its own state and backend. Splitting a monolithic Terraform project into stacks reduces blast radius when something breaks, speeds up CI runs by only touching what changed, and gives teams clearer ownership boundaries. Stacks aren't tied to a specific environment strategy either — Terramate works alongside Terragrunt projects without forcing a rewrite.

Dependency-Aware Orchestration

Real infrastructure has dependencies: a networking stack has to apply before the application stack that references its outputs. Terramate models these relationships as a directed acyclic graph, with explicit after, before, wants, and wanted_by directives controlling execution order. Combined with output sharing between stacks, this removes a category of manual coordination that otherwise falls on whoever runs the deployment by hand.

Git-Native Change Detection

The --changed flag scans Git history to identify exactly which stacks were affected by a commit, including changes to shared modules that ripple into multiple stacks. Running plans and applies only against affected stacks keeps CI pipelines fast even as a repository grows into hundreds of stacks, a scaling problem that flat Terraform projects handle poorly.

CI/CD Pipeline Integration

Terramate doesn't ship its own hosted runners; instead it slots into whatever CI/CD system a team already runs, most commonly GitHub Actions. A typical setup calls the Terramate CLI from a workflow step, using --changed to plan and apply only the stacks a pull request actually touched, then posts results back as a pull request comment. For teams that have already invested in a specific pipeline tool, this is a meaningfully lower-friction adoption path than migrating to a new hosted orchestration platform wholesale.

Drift Detection and Cloud Observability

Terramate Cloud layers observability on top of the CLI's orchestration: scheduled drift checks, an asset inventory, DORA metrics, and incident management, available from the Teams plan upward. This is where Terramate is currently narrower than some rivals — Cloud support today covers Terraform and OpenTofu, with Pulumi, CloudFormation, and Kubernetes manifests listed as roadmap items rather than shipped features.

Pricing

Terramate's pricing is genuinely public, which is refreshing in a category where "contact sales" is often the default answer. The Community tier is free forever, covering up to two users and 1,000 managed resources with 30-day data retention and Discord-based community support — a real starting point, not a crippled trial.

Above that sits the Teams plan, a flat $449 per month covering unlimited users and up to 5,000 resources, with 90-day retention and 24-hour email and chat support through a dedicated Slack channel. A flat price regardless of headcount is simpler to budget than the per-seat or concurrency-based models used by some competitors, though it does mean a five-person team and a fifty-person team pay the same amount. Enterprise pricing is custom, adding RBAC, SAML 2.0 SSO, audit logs, a 4-hour support SLA, and a dedicated account manager.

Against Spacelift, a fellow European IaC platform, Terramate's flat-fee Teams tier trades some pricing flexibility for predictability, while Spacelift's concurrency-based model can scale cost more precisely with actual usage.

EU Compliance & Privacy

Terramate GmbH is headquartered in Berlin and subject to GDPR as a data controller and processor. Its Cloud product offers a genuine choice at account creation: an EU data residency region in Belgium, or a US region in Ohio. Once selected, all synced stack, preview, and deployment data stays within that region, and the company does not support mixing locations within a single account.

Teams that need the strongest possible data control have a more complete answer in the open-source CLI. Because code generation, orchestration, and change detection all run locally, an organisation can use Terramate's core capabilities without touching Terramate Cloud, or Terramate's infrastructure, at all. One honest gap remains: at the time of writing, Terramate has not published SOC 2 or ISO 27001 certification for Terramate Cloud. Larger regulated buyers will likely want to see that certification before committing production infrastructure data to the hosted service.

Who It's Best For

Teams drowning in Terraform copy-paste across environments will get immediate value from Terramate's code generation and globals system, without needing to adopt Terramate Cloud at all.

Organisations migrating from Terraform to OpenTofu, or running both during a transition, since Terramate treats the two as first-class citizens rather than favouring one.

Small-to-mid infrastructure teams that want predictable, flat pricing rather than usage-based billing that's hard to forecast month to month.

Teams already using Terragrunt who want orchestration and observability layered on top without a disruptive rewrite of their existing stack structure.

Terramate is a weaker fit for organisations running Pulumi, CloudFormation, or Kubernetes manifests as their primary IaC tooling today, since Terramate Cloud's observability features don't yet cover those frameworks. Regulated enterprises that require SOC 2 or ISO evidence before onboarding a vendor should also factor in Terramate's early stage. A two-year-old company of under 20 people has a shorter track record than Terraform itself or established rivals.

The Verdict

Terramate solves a real, specific problem — Terraform code duplication and multi-stack orchestration — with an architecture that keeps you out of vendor lock-in by generating native, portable HCL. The free Community tier is generous enough to actually use, and the flat $449 Teams price is easy to budget against. What buyers need to weigh honestly is the company's youth: founded in 2023 with fewer than 20 employees, Terramate has a shorter track record and a narrower framework list than established alternatives like Spacelift. Teams specifically fighting Terraform or OpenTofu sprawl today will often find that trade-off worth making. Anyone needing multi-framework support or third-party compliance certification right now is better off waiting or looking elsewhere first.

Frequently Asked Questions

Is Terramate open source?

The Terramate CLI is open source under the Mozilla Public License 2.0 and can run entirely on your own machine or CI runner. Terramate Cloud, which adds observability, DORA metrics, and drift dashboards, is a separate proprietary SaaS product with its own paid tiers.

Does Terramate replace Terraform?

No. Terramate generates and orchestrates native Terraform and OpenTofu code rather than replacing it. Your infrastructure definitions remain standard HCL that runs with plain Terraform or OpenTofu, even without Terramate in the pipeline.

How much does Terramate cost?

Community tier is free for up to 2 users and 1,000 resources. Teams costs $449 per month flat for unlimited users and up to 5,000 resources. Enterprise pricing is custom and quoted directly by Terramate's sales team.

Where is Terramate Cloud data stored?

Customers choose a data residency location when creating a Terramate Cloud account: an EU region in Belgium or a US region in Ohio. All synced stack, preview, and deployment data stays within the chosen region.

How does Terramate compare to Terraform Cloud?

Terramate generates native Terraform and OpenTofu code and adds stacks, orchestration, and drift detection on top, while Terraform Cloud is HashiCorp's own state-management and run platform. It also supports OpenTofu, the community fork, which Terraform Cloud does not.