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 ↗
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.




Plan, review and apply from one place, with the tools your teams already use.
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 ↗
Pick the tool and the version per workspace. Both run against any cloud or on-premises configuration.
Creating workspaces ↗
Every resource in the state as a dependency diagram. Inspect attributes, compare versions, roll back.
Terraform state ↗
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 ↗
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 ↗
Identity comes from the provider you already run. Permissions follow the team, not the person.
A team maps an identity provider group to a role in the organization, so people only see what their job requires.
Team management ↗
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) ↗
Your cluster, your registry, your agents. Nothing leaves the network you choose.
Publish, version and reuse internal modules and providers, with the usage snippet and README next to inputs and outputs.
Private registry ↗
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.yamlHelm on Kubernetes or Docker Compose. One release, your own domain.
Sign in through your identity provider; link GitHub, GitLab, Bitbucket or Azure DevOps.
Push to a branch, or point the Terraform CLI at the remote backend. Review the plan, approve, apply.
Teams map groups to roles; templates, policies and the private registry keep every workspace in line.
Everything on this page is documented end to end. Pick where you are.
Helm on Kubernetes or Docker Compose, with the values and secrets explained.
Deployment guide ↗Connect a GitHub, GitLab, Bitbucket or Azure DevOps repository, or push from the CLI, then plan and apply.
Creating workspaces ↗A CLI for day-to-day work and an API for everything else.
Terrakube CLI ↗API-driven workflow ↗These organizations support the project with free licenses and services.




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