DEV.co
Open-Source DevOps · terrateamio

terrateam

Terrateam is an open-source GitOps platform that automates Terraform, OpenTofu, and Pulumi deployments through GitHub pull requests. It handles large-scale infrastructure-as-code workflows with monorepo support, policy enforcement, and cost estimation, available as both a self-hosted and hosted SaaS offering.

Source: GitHub — github.com/terrateamio/terrateam
1.2k
GitHub stars
71
Forks
OCaml
Primary language
MPL-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryterrateamio/terrateam
Ownerterrateamio
Primary languageOCaml
LicenseMPL-2.0 — OSI-approved
Stars1.2k
Forks71
Open issues171
Latest release20260706-1312-514a437 (2026-07-06)
Last updated2026-07-06
Sourcehttps://github.com/terrateamio/terrateam

What terrateam is

Written in OCaml, Terrateam integrates with GitHub to orchestrate IaC provisioning via pull request comments. It provides tag-based configuration, parallel execution with smart locking, OPA/Rego policy enforcement, drift detection, and a stateless self-hostable architecture designed for monorepos with complex workspace dependencies.

Quickstart

Get the terrateam source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/terrateamio/terrateam.gitcd terrateam# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Large-scale monorepo Terraform management

Handles thousands of workspaces across a single repository with tag-based configuration, dependency coordination, and cross-environment apply strategies without manual complexity.

Multi-tool infrastructure orchestration

Unified GitOps interface for mixed IaC stacks (Terraform, OpenTofu, Terragrunt, CDKTF, Pulumi) with consistent policy, cost, and approval workflows across all tools.

Self-hosted infrastructure automation with compliance

Organizations requiring full control over state, secrets, and runners can deploy Terrateam on-premises with OPA policies, RBAC, and OIDC integration for regulated environments.

Implementation considerations

  • Requires GitHub organization/repository setup and OAuth/token configuration; default deployment uses Docker Compose—assess whether self-hosting or SaaS aligns with your compliance posture.
  • Tag-based configuration model requires upfront planning of workspace taxonomy and policy rules; monorepo migrations may need significant `.terrateam/config.yml` design work.
  • Stateless design means state files and secrets remain external (your Terraform backend and GitHub Secrets); ensure backend and secret-manager integration is production-ready before pilot.
  • Policy enforcement via OPA/Rego requires learning Rego syntax; consider training or hiring expertise if custom policy logic is needed beyond built-in approval workflows.
  • Parallel execution relies on smart locking; verify your Terraform state backend supports concurrent operations and state locking (S3 + DynamoDB, Terraform Cloud, etc.).

When to avoid it — and what to weigh

  • Simple single-workspace deployments — If you manage only a few environments or simple Terraform configurations, the overhead of GitOps orchestration and policy engines will likely exceed operational benefit.
  • Non-GitHub version control systems — Terrateam is GitHub-native; no support for GitLab, Bitbucket, or other VCS platforms is mentioned in available documentation.
  • Minimal operational overhead requirement — Self-hosting requires Docker Compose, runner management, and integration with your GitHub installation—not a turnkey solution for teams avoiding infrastructure operations.
  • Proprietary IaC tools or custom CLIs only — While it claims to work with 'any CLI,' primary testing and documentation focus on Terraform, OpenTofu, and major tools; custom or proprietary provisioners may require custom integration work.

License & commercial use

Terrateam is licensed under MPL-2.0 (Mozilla Public License 2.0), a weak copyleft OSI-approved license. Source code modifications must be shared, but MPL-2.0 is file-scoped and allows proprietary derivative works if only modified files are shared.

MPL-2.0 permits commercial use of the software itself without royalty. However, enterprise features (RBAC, centralized configuration, Gatekeeper approval workflows) are explicitly reserved for the hosted SaaS and self-hosted Enterprise Edition under separate licensing. Verify licensing terms with the Terrateam team before assuming all features are available for your intended commercial deployment.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitStrong
Assessment confidenceHigh
Security considerations

State and secrets remain external (user-managed backends and GitHub Secrets); Terrateam does not expose or store sensitive data internally. Self-hosting requires securing runner environments and GitHub token scope. RBAC and OIDC integration are available in Enterprise Edition; open-source version lacks built-in role enforcement. No public security audit or CVE history available; assess threat model and code review before production deployment in regulated environments.

Alternatives to consider

Terraform Cloud/Enterprise (HashiCorp)

Native, managed Terraform state, runs, and policy engine (Sentinel). Vendor-managed but tightly integrated; less monorepo-friendly and primarily Terraform-only.

Atlantis (open-source)

Lightweight, self-hostable Terraform PR automation. Simpler deployment and no OCaml dependency, but lacks native policy engine, cost estimation, and monorepo-scale features.

Spacelift (commercial SaaS)

Multi-tool orchestration, policy engine, and UI similar to Terrateam. Managed SaaS removes self-hosting burden but introduces vendor lock-in and higher cost at scale.

Software development agency

Build on terrateam with DEV.co software developers

Evaluate Terrateam for your infrastructure-as-code strategy. Start with the hosted SaaS free tier or deploy self-hosted in Docker Compose. Join the Slack community for setup guidance and best practices.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

terrateam FAQ

Can I use Terrateam with non-GitHub repositories?
No. Terrateam is GitHub-native and integrates via pull requests and GitHub checks. Support for GitLab, Bitbucket, or other VCS platforms is not mentioned in available documentation.
What happens to my Terraform state files?
Terrateam does not manage state; it orchestrates Terraform operations. Your state files remain in your external backend (S3, Terraform Cloud, etc.). Terrateam is stateless by design.
Is the open-source version feature-complete for self-hosting?
The open-source version includes core automation, policy enforcement, and UI. Enterprise features (RBAC, centralized configuration, Gatekeeper) are reserved for Hosted SaaS and Enterprise Edition licensing.
Can I use Terrateam with tools other than Terraform?
Yes. Terrateam supports OpenTofu, Terragrunt, CDKTF, Pulumi, and any CLI-based provisioning tool. Primary testing and documentation focus on Terraform and OpenTofu.

Software developers & web developers for hire

From first prototype to production, DEV.co delivers software development services around tools like terrateam. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source devops and beyond.

Ready to scale your Terraform workflows?

Evaluate Terrateam for your infrastructure-as-code strategy. Start with the hosted SaaS free tier or deploy self-hosted in Docker Compose. Join the Slack community for setup guidance and best practices.