# Install terramate with Homebrew, Nix, winget

Managing Terraform stacks with change detections and code generations. Version 0.17.2 via Homebrew; verified 2026-07-31. Also installable with nix: nix profile install nixpkgs#terramate.

## Install

```sh
sudo av install brew:terramate
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install terramate
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#terramate
```

  Evidence: nixpkgs package indexes: pkgs/by-name/te/terramate/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- winget (92%):

```sh
winget install --id Terramate.CLI -e
```

  Evidence: Windows Package Manager source index: Terramate.CLI from https://cdn.winget.microsoft.com/cache/source.msix

## Package facts

- **Package key:** brew:terramate
- **Package manager:** Homebrew
- **Version:** 0.17.2
- **Source summary:** Managing Terraform stacks with change detections and code generations
- **Homepage:** <https://terramate.io/docs/>
- **Repository:** <https://github.com/terramate-io/terramate>
- **Last updated:** 2026-07-31T13:29:11Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- terramate-ls (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.17.2
## Project history and usage

Terramate is an open-source Infrastructure as Code orchestration and code-generation CLI for Terraform, OpenTofu, Terragrunt, Kubernetes, and CI/CD workflows.

### Project history

The public Terramate repository was created in September 2021. Its README describes Terramate CLI as an open-source orchestration and code generation engine for scaling IaC, with optional pairing to Terramate Cloud for managed observability, drift detection, asset management, policy, and notification features.

Terramate's project model is built around stacks. The README emphasizes breaking large infrastructure into smaller stacks, reducing duplicated configuration through generated HCL, JSON, or YAML, and orchestrating commands across stacks with a graph-based engine.

The official CLI docs describe Terramate as a daily IaC workload tool for managing stacks, maintaining a DRY codebase with code generation, planning and deploying with orchestration and change detection, and synchronizing data with Terramate Cloud.

### Adoption history

Terramate is newer than Terragrunt but has become a visible Terraform/OpenTofu orchestration package. Repository metadata showed several thousand stars by July 2026, and input package metadata lists Homebrew, Nix, and winget packages.

The README's onboarding claims are aimed at incremental adoption: existing Terraform, OpenTofu, or Terragrunt projects can start with a single command and without refactoring, while teams can adopt features individually to avoid hard lock-in.

### How it is used

Common CLI usage includes creating and listing stacks, running commands such as terraform init or terraform apply across all or changed stacks, generating repeated backend and provider configuration, and filtering execution by Git changes, tags, directories, or Terramate Cloud status.

The official change-detection docs explain the --changed workflow for running commands only in stacks affected by a commit, branch, or pull request. The code-generation docs describe generating stack files from blueprints to keep Terraform backend and provider configuration DRY.

### Why package nerds care

For package-manager users, Terramate is significant because it packages a higher-level IaC workflow engine as a single CLI. It is useful in dev shells and CI images where users already install Terraform, OpenTofu, or Terragrunt and want change detection, orchestration, and generated configuration without adopting a hosted CI product.

Its cross-platform package metadata, Go-based install path, and optional Cloud pairing make it both a local CLI package and an entry point into a larger IaC platform.

### Timeline

- 2021: Public Terramate repository created.
- 2020s: CLI docs establish stack management, code generation, orchestration, and change detection as core workflows.
- 2026: Homebrew, Nix, and winget metadata list Terramate CLI packages.

### Related projects

- Terraform and OpenTofu are primary IaC engines Terramate orchestrates.
- Terragrunt is explicitly supported as an existing project style that Terramate can onboard.
- Terramate Cloud is the optional managed service paired with the open-source CLI.

### Sources

- CLI reference: https://terramate.io/docs/cli/reference/cmdline/
- Change detection docs: https://terramate.io/docs/cli/change-detection/
- Code generation docs: https://terramate.io/docs/cli/code-generation/
- Docs: https://terramate.io/docs
- Input package metadata: source_facts.package-manager
- README: https://github.com/terramate-io/terramate#readme
- Repository metadata: https://api.github.com/repos/terramate-io/terramate


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: <project>/**/*.tm.hcl, <project>/**/*.tm
## Other Package-Manager Records

- Nix - terramate: normalized package name match | nixpkgs package indexes: pkgs/by-name/te/terramate/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- winget - Terramate.CLI: normalized package name match | Windows Package Manager source index: Terramate.CLI from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/terramate.yml](https://github.com/mxcl/pkgdb/blob/main/combined/terramate.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph