Infrastructure as code automation for Terraform and OpenTofu

The open source platform that runs, reviews and manages infrastructure as code at scale. Terraform and OpenTofu connect to it as a remote backend, so your code stays as it is. Platform teams govern workspaces, access and policies; application engineers plan, apply and read the result.

Release 2.34.2, November 15, 2026Apache 2.0 licensed

Everything you need to run infrastructure as code

Run

Plan, review and apply from one place, with the tools your teams already use.

Runs you can read before you apply

Every run shows the plan as a list of resource changes, with the console one click away. Approve it in the same view.

Workspaces and runs ↗
A completed run showing three resources to create, two to change and one to destroy

Terraform and OpenTofu

Pick the tool and the version per workspace. Both run against any cloud or on-premises configuration.

Creating workspaces ↗
Choosing between Terraform and OpenTofu when creating a workspace

Visual state

Every resource in the state as a dependency diagram. Inspect attributes, compare versions, roll back.

Terraform state ↗
State version shown as a diagram of VPC, subnets, gateway, instance and database

Templates and schedules

Templates define the steps a run executes, from plan and apply to custom workflows that call external tools. Schedules run them without anyone clicking.

Templates ↗Workspace scheduler ↗
Organization templates: Plan, Plan and Apply, Destroy and CLI variants

Run triggers

Chain workspaces that depend on each other. When one applies a change, Terrakube queues a run in the workspaces that consume its outputs, so a VPN never falls behind its VPC.

Run triggers ↗
Run triggers of a vpn workspace: it runs after vpc, and app and monitoring run after it

Secure

Identity comes from the provider you already run. Permissions follow the team, not the person.

Access control

A team maps an identity provider group to a role in the organization, so people only see what their job requires.

Team management ↗
Teams settings with an admin team and a developers team

Policies as code

Write Open Policy Agent policies once, keep them in Git, and attach them to the organization, a project, a tag or a workspace. Every plan is checked before apply: advisory policies warn, soft-mandatory ones wait for an override with a justification, hard-mandatory ones stop the run.

Policy governance (OPA) ↗
Policy checks of a run: one policy set passed, one advisory warning for missing tags, one soft-mandatory failure waiting for an override
Single sign-onAuthenticate with the identity provider your organization already uses.
Providers
  • Azure Entra ID
  • Google Cloud Identity
  • Amazon Cognito
  • GitHub
  • Keycloak
Protocols
  • OIDC
  • SAML
User management ↗
Dynamic credentialsCloud credentials issued at run time, nothing long-lived stored in the workspace.
Clouds
  • Amazon Web Services
  • Azure
  • Google Cloud
Secret stores
  • Vault
  • OpenBao
Dynamic provider credentials ↗

Host

Your cluster, your registry, your agents. Nothing leaves the network you choose.

Private registry

Publish, version and reuse internal modules and providers, with the usage snippet and README next to inputs and outputs.

Private registry ↗
A private module page with the usage block, version, source and inputs

Self-hosted anywhere

A Kubernetes cluster on any cloud or on-premises, or the whole platform with Docker Compose.

Deployment ↗
helm repo add terrakube-repo https://helm.terrakube.io
helm install terrakube terrakube-repo/terrakube \
  -n terrakube --create-namespace -f values.yaml
Private agentsRun jobs on self-hosted or ephemeral agents, in an environment you control.Ephemeral agents ↗
Open sourceRead the code, extend the platform, and start a development environment from the dev container in minutes.Development environment ↗

How it fits into your setup

  1. 01

    Install

    Helm on Kubernetes or Docker Compose. One release, your own domain.

  2. 02

    Connect

    Sign in through your identity provider; link GitHub, GitLab, Bitbucket or Azure DevOps.

  3. 03

    Run

    Push to a branch, or point the Terraform CLI at the remote backend. Review the plan, approve, apply.

  4. 04

    Govern

    Teams map groups to roles; templates, policies and the private registry keep every workspace in line.

Start with the documentation

Everything on this page is documented end to end. Pick where you are.

Install it

Helm on Kubernetes or Docker Compose, with the values and secrets explained.

Deployment guide ↗

Run your first workspace

Connect a GitHub, GitLab, Bitbucket or Azure DevOps repository, or push from the CLI, then plan and apply.

Creating workspaces ↗

Set up access

Dex connects your identity provider; teams map groups to roles.

User management ↗

Drive it from code

A CLI for day-to-day work and an API for everything else.

Terrakube CLI ↗API-driven workflow ↗

Supported by

These organizations support the project with free licenses and services.

JetBrainsGitBookDockerTuta

Open source, by engineers for engineers

Whether you are fixing bugs, adding features, improving the docs or sharing feedback, your input makes a difference.

Join us on Slack

Get involved