terrateam.io

What it is

Terrateam is a GitOps-native infrastructure orchestration tool from Stategraph. It focuses on bringing IaC changes for Terraform, OpenTofu, Pulumi, CDKTF, Terragrunt, and similar tools into the Pull Request workflow. It runs plans inside PRs, shows cost changes, performs policy and security checks, and applies changes once team approval requirements are met. The goal is to make infrastructure changes visible, auditable, and governed.

Core capabilities

In terms of features, Terrateam covers PR automation, parallel plans, monorepo/workspace execution, custom workflows and hooks, drift detection, directory-level RBAC, approval gates, OPA/Conftest policy checks, Checkov security scanning, Infracost cost estimation, and audit logs. It emphasizes being “unopinionated,” making it adaptable to different repository structures and team processes. For integrations, it supports GitHub/GitLab, CODEOWNERS, OIDC, Slack Connect, and deployment to AWS, GCP, Azure, or self-managed environments. The crawled text indicates that it uses MPL-2.0, is “Built in the open,” and offers Self-Hosted OSS.

Deployment and pricing

Deployment options are fairly comprehensive: Cloud Hosted, Private Cloud, and Self-Hosted. Self-hosting supports Docker Compose, Kubernetes, and air-gapped environments. Pricing is straightforward: Cloud Free is $0/mo and has no limits on users, runs, concurrency, or private runners; Pro is $224/mo and adds drift detection, email support, and more; the Enterprise technical plan is $563/mo and includes API access, CODEOWNERS, RBAC, Gatekeeper, centralized configuration, and 365-day audit retention; the procurement-supported version is $1,087.50/mo. Self-Hosted OSS is free, while paid self-hosting is $13,050/yr.

Pros, cons, and who it’s for

Its strengths are its open-source orientation, a free tier without core usage limits, flexible deployment models, and governance capabilities covering approvals, policy, auditing, and cost control. It is well suited to platform engineering, DevOps, security and compliance teams, as well as organizations managing large Terraform monorepos. The main limitation is that key governance features such as RBAC, centralized configuration, API access, and Gatekeeper require Enterprise or paid self-hosting. It also depends heavily on the GitHub/GitLab PR model, so teams that are not already using GitOps will need to adjust their workflows.

Access from China

The crawled text does not provide information about network accessibility from mainland China, payment methods, or local support, so this remains unknown. If access or payment is restricted, alternatives such as Atlantis, Terraform Cloud/Enterprise, Spacelift, env0, and Scalr may be worth evaluating. For organizations with strict compliance requirements, its self-hosting and air-gapped capabilities are significant advantages.