Terramate

The Origin of Terramate: In 2020, we built an Internal Developer Platform (IDP) for one of Europe’s fastest-growing startups. By the time we handed it over, their engineering team had grown from 5 to 250 people. What we learned was eye-opening: Building on top of IaC was far more time-consuming and complex than it should have been. This inspired us to create Terramate—a platform designed to eliminate the inefficiencies we encountered and help teams scale IaC efficiently and confidently. Read more about why we built Terramate (1st comment)

Why did we build Terramate? Infrastructure as Code (IaC) tools like Terraform and OpenTofu have transformed how teams manage infrastructure. But even with their power and maturity, they leave significant gaps that make scaling IaC challenging and resource-intensive: ❌ Lack of standards for managing complex environments ❌ Limited orchestration for dependencies and changes ❌ No built-in automation for GitOps workflows ❌ Poor visibility and observability across repositories and teams ❌ Lack of self-service options for developers The result? Teams spend time and money building home-grown solutions or adopting costly platforms—only to face maintenance rabbit holes, limited flexibility, and security risks. That’s why we built Terramate. Terramate eliminates these gaps by providing: ✔ Scalable IaC orchestration ✔ Full visibility and observability ✔ Built-in governance, policies, and misconfiguration detection ✔ Seamless self-service capabilities for developers We created Terramate to save teams from the endless cycle of wasted time and resources , enabling them to focus on what truly matters: delivering value. Read more about why we started Terramate in our latest blog article (see 1st comment)

Don’t forget to tune in for today’s: Terraform Tuesdays – Apply When? | Livestream Debate! 🚨 Hosted by Ned Bellavance, with Sören Martius (Terramate) and Malcolm Matalka (Terrateam) debating the eternal question: When do you run terraform apply? Before or after merge? How do you handle PRs, and is GitOps for IaC even a good idea? Join us live at 7 AM PST / 4 PM CET!

Having had interactions with several #Terraform / #OpenTofu users lately I would like to share that it is NOT a sin to …     ⛓️💥 Split monolithic setups into smaller self-contained pieces. This will help you from many angles be it the blast radius of changes or analyzing issues when something goes side-ways. Refactoring setups is not only allowed but a must when your configuration grows. No difference to application code.   🙋 Ask more experienced #Terraform #OpenTofu user for feedback on your setup and get recommendations on improvements. Nobody gets it right from the start and it is good to share experiences and learn from each other.       🛠️ As the setup grows, orchestration becomes a challenge. However, nobody forces you to exclusively orchestrate your setup with vanilla #Terraform #OpenTofu. If you do not want to go to Hashicorp Cloud Platform there are several alternatives that can make your life easier. My favorite is #Terramate. It makes sense to take a step back and reflect if the approach and tool is fitting or used for the sake of using the tool you know well. Looking to the side helps as the Terraform ecosystem is huge.

Terramate was featured in the latest episode of #Terraform #Tuesdays 💪🏼🙇♂️ In this 30-minute video, Ned Bellavance shows how to use Terramate CLI to break up a #Terralith into multiple smaller stacks while staying in native Terraform using stacks, orchestration and code generation. Here's a quick overview of what Ned is discussing in the video: 👉 Terralith Problems 👉 Terramate CLI Overview 👉 Original Configuration 👉 Adding Terramate Stacks 👉 Generate Provider and Backend Configuration 👉 Variable Values 👉 Sharing Outputs 👉 Using the Terramate CLI 👉 Detecting Changes with Git 👉 Terramate Summary & Final Thoughts Stay tuned for the next Episode in January, which will cover Terramate Cloud in detail! Link to video 👉 https://lnkd.in/eCiPkBkf

Ned Bellavance did a fantastic deep dive on Terramate CLI. A great starter, especially when you want to "have your cake and eat it, too", i.e. split your state in your Terralith while still being in one repo. Link in 1st comment.

When should you run terraform apply: before or after merge? It’s a debate that feels eternal, but… Ned Bellavance has joined forces with Malcolm Matalka (Terrateam) and Sören Martius (Terramate) to finally settle this age-old question. RSVP and join this live debate next Tuesday, December 17th, at 7 AM PST / 4 PM CET!

Managing failed Terraform, OpenTofu, or Terragrunt stacks during orchestration has often meant restarting the entire CI/CD pipeline—leading to long wait times and unnecessary resource usage. Terramate’s stateful orchestration now makes it possible to rerun only failed or drifted stacks, either locally or in any CI/CD, with a single command: terramate run --status drifted|failed|skipped --tofu apply This approach integrates directly into existing Terraform, OpenTofu, or Terragrunt projects without requiring migrations or complex configurations, making stack orchestration more focused and efficient.

Improved Change Detection for Terragrunt in Terramate 🚀 Terramate enhances change detection for Terragrunt modules by tracking file() usages in Terragrunt files. When files referenced by Terragrunt change, Terramate automatically marks the related stacks as changed. This highly requested feature simplifies managing dynamic configurations in Terragrunt-based projects. This update is now available in v0.11.4. Read more about change detection in our Terramate Documentation (see 1st comment) 👇