Terrateam

Terrateam (now rebranded Stategraph) is an open-source pull-request automation platform for DevOps teams running Terraform, OpenTofu, CDKTF, Terragrunt, or…

  • Development
  • Infrastructure
  • Other
  • Productivity
  • Tools & Utilities
Terrateam (now rebranded Stategraph) is an open-source pull-request automation platform for DevOps teams running Terraform, OpenTofu, CDKTF, Terragrunt, or Pulumi. It listens for pull requests on GitHub or GitLab, runs plan for each changed directory and comments the output back, then applies changes via an apply comment or on merge, with plans and applies running as jobs in your own CI using your own cloud credentials.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

70/100 Good

Maintained
100last commit 5 days ago
Popular
621,327 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
88no serious findings, 2 minor, CI, tests

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
1,327
Open issues
114
Last commit
2026-11-16
Latest release
3.2.34
License
MPL-2.0
Activity
steady

Checked 5 days ago - source: GitHub (terrateamio/terrateam)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 2 CPU core(s), 20 GB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install and check the oiq command Use the provided Linux/macOS install script, or Homebrew (a macOS package installer) on macOS, to install OpenInfraQuote as the oiq command, then run oiq --version. If it does not print a version, the program is not on your PATH (a list of folders your computer searches for programs), so commands that call oiq will fail. source
  • Docker needs two files in the same folder For the Docker example, make sure Docker is installed and running, and keep prices.csv and tfplan.json in the folder where you run the command. If either file is missing or named differently, Docker cannot pass it into the container and the cost check stops early. source
  • Fill prices.csv with valid pricing rows The prices.csv file tells OpenInfraQuote which resources to match and what their cost is, using the column format shown for examples like Amazon RDS. Without the rows you need, the tool has no pricing data and cannot produce useful prices. source
  • Docker Compose quickstart Clone the repository and start the stack from the docker directory with 'docker compose up -d', then follow the self-hosted guide linked from the README to connect your GitHub or GitLab instance and cloud provider credentials. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I self-host the open-source edition of Terrateam?

Run it with Docker Compose. An Enterprise build is also available and uses a license key.

Does the self-hosted Terrateam server execute Terraform plans and applies?

No. Plans and applies run on your own GitHub Actions or GitLab CI runners, with Terraform, OpenTofu, the stategraph CLI, Terragrunt, Pulumi, CDKTF, or any command-line tool.

Can I keep my existing Terraform state backend when self-hosting?

Yes. You can start Orchestration against your existing state backend and move the state into PostgreSQL later.

How is an apply triggered in a Terrateam pull request workflow?

The apply runs when the pull request is merged or when a stategraph apply comment is posted. Policy checks, cost estimates, and approvals are handled in the review.

Answers sourced from github.com, terrateam.io

Community

Collected 49 days ago - public community threads