Open source Control plane for OpenTofu

Plan, approve, and apply OpenTofu on your own server.

Writ is an open-source control plane. It plans the commits you or your CI job send it, waits for your team to approve, and applies that exact plan. No cloud keys in CI or on laptops.

Version 0, and OpenTofu 1.13.9 only. What Writ isn’t, yet

writ.example.com/ui/plans/d76f644db169d07f240be36ef1722635
The control UI’s page for one plan, as a reviewer sees it: pending, 0 of 1 approvals, an Approve this plan button, and a summary of the changes.The control UI’s page for one plan, as a reviewer sees it: pending, 0 of 1 approvals, an Approve this plan button, and a summary of the changes.
  • Apache 2.0
  • You host it
  • One Go binary
  • No limit on users, runs, or resources

A control plane between your Git repository and your cloud

Today a CI job or a laptop runs tofu apply with keys that can change production. With Writ, they ask a server you host, and it does the run.

What goes wrong without one

You review code, not a plan

A merge request approval says the code can merge. It doesn’t tie the apply to the plan you read.

The job holds the keys

In plain CI, the job that runs tofu holds the cloud credentials, the state, and the plan. A merge request can change what that job runs.

Plans print secrets

tofu plan and tofu apply print secrets. A log that keeps their output shows them to everyone who can read it.

How it works: plan, approve, apply

Writ runs OpenTofu for you, on a server you host. Your CI job and your laptop only ask.

If a newer plan replaced the approved one, or the state moved, Writ refuses the apply. You plan and approve again.

1. The plan your teammate reads
OpenTofu 1.13.9 plan of app@prod  + random_pet.name (create)  + terraform_data.note (create)  + terraform_data.secret (create)  + module.cert.tls_private_key.key (create)Plan: 4 to add, 0 to change, 0 to destroy.Outputs that change: pet.
2. alice made the plan, so only bob can approve it
alice $ writ approve --remote 927b69ec7af23641c68c3ce3cce370ecerror: denied: gitlab acme/infra #1849401 (alice) made plan 927b69ec7af23641c68c3ce3cce370ec and cannot approve it: it needs 1 approval from someone elsebob $ writ approve --remote 927b69ec7af23641c68c3ce3cce370ecApproved plan 927b69ec7af23641c68c3ce3cce370ec for prod (app): 1 of 1 approvals (gitlab acme/infra #1849401 (bob)), approved.
3. The apply of the plan bob approved
OpenTofu apply of app@prod  terraform_data.note: create complete  terraform_data.secret: create complete  random_pet.name: create complete  module.cert.tls_private_key.key: create completeApply: 4 added, 0 changed, 0 destroyed.State version 1 of app@prod.

Output of TestTofuApproveApply, 2026-11-16. The prompts alice $ and bob $ are added to show who ran each command. How approvals work

See what’s waiting, what ran, and what drifted

The control UI comes with writ serve. It shows the same plans your terminal does.

Plans waiting for approval, applies in progress, failed runs, and drifted stacks, for each environment.

writ.example.com/ui/
The control UI’s overview: stat cards for plans waiting for approval, applies, failed runs, and drift, two alerts, and the plans waiting for approval.The control UI’s overview: stat cards for plans waiting for approval, applies, failed runs, and drift, two alerts, and the plans waiting for approval.

One plan: who made it, how many approvals it needs, and every change. A secret shows as (sensitive).

writ.example.com/ui/plans/d76f644db169d07f240be36ef1722635
The control UI’s page for one plan, as a reviewer sees it: pending, 0 of 1 approvals, an Approve this plan button, and a summary of the changes.The control UI’s page for one plan, as a reviewer sees it: pending, 0 of 1 approvals, an Approve this plan button, and a summary of the changes.

A stack’s drift check: what changed outside OpenTofu, and what the code would change.

writ.example.com/ui/stack?stack=app&env=dev
The control UI’s page for the stack app in dev: drifted, with one change outside OpenTofu and five that the code would change.The control UI’s page for the stack app in dev: drifted, with one change outside OpenTofu and five that the code would change.

Every apply Writ started, with its plan and who asked for it.

writ.example.com/ui/runs
The control UI’s list of runs: one applying, one applied, and one failed, each with its stack, plan, and who started it.The control UI’s list of runs: one applying, one applied, and one failed, each with its stack, plan, and who started it.

You can approve a plan in the control UI. To apply one, use writ apply --remote or your CI job.

Screenshots of the control UI against a dev control plane with demo stacks, 2026-11-16.

What changes when Writ runs OpenTofu

No cloud keys in CI or on laptops

Your CI job sends a commit and holds no credentials. Writ takes the plan role you configure for a plan, so make it read-only. Only an apply gets the apply role: an approved one, or one overridden by someone you allow, with the reason recorded.

Roles are AWS roles today.

Roles and credentials
WhoCloud credentialsYour state
Your laptopnone, only a sessionno state key
Your CI jobnone, only its OIDC tokenno state key
Writ, for a planplan rolereads only
Writ, for an applyapply rolelocks and writes

Secrets stay out of what Writ stores and shows

One mask covers the plan you read, the apply’s output, and the errors. You see that a secret changed without seeing it.

The mask is a filter. The docs list the cases it can’t catch.

Secrets and the mask
Part of a plan in the control UI: a replaced resource whose keepers show {"secret":"(sensitive)"} before and after, marked sensitive value changes.Part of a plan in the control UI: a replaced resource whose keepers show {"secret":"(sensitive)"} before and after, marked sensitive value changes.

Drift checks on a schedule

Writ plans each stack on a timer. It marks what changed outside OpenTofu, and what your code would change.

You see drift in the control UI and the API. Writ doesn’t notify anyone yet.

Drift checks
A stack’s drift check in the control UI: drifted, with one change outside OpenTofu and five that the code would change, each with its address and action.A stack’s drift check in the control UI: drifted, with one change outside OpenTofu and five that the code would change, each with its address and action.

Policy checks every plan, twice

You write rules in Rego. Writ checks each plan when it’s created and again before the apply. No approval gets past a mandatory deny.

There’s no writ policy test yet. Use conftest.

Policy
Policy: denied, so this plan cannot be approved or applied.  deny: [examples] tls_private_key.key: an RSA key needs 4096 bits, and this one has 2048

Output of TestTofuPlanByCommit, 2026-11-15, with lines cut.

Agents plan. People approve.

With writ mcp, your coding agent plans a commit and reads the plan and its policy verdict. It never holds a cloud credential, and it can’t approve or apply.

Use Writ with an agent
$ claude mcp add --scope project writ -- writ mcpAdded stdio MCP server writ with command: writ mcp to project config

Output of Claude Code 2.1.318, 2026-11-10.

The approved plan is exactly what appliesAn approval is for one plan id, and the apply runs the plan Writ kept. Approvals
Sign in with your identity providerwrit login signs you in from a terminal, by device code or through a browser. Sign in
Bring what you already runwrit import bulk writes resource and import blocks for cloud objects you already have. Import many objects
Your state can stay where it isA stack on backend "s3" keeps its bucket. Stacks on S3

Writ, Spacelift, or HCP Terraform?

The paid control planes do this job as a hosted service, priced by plan. Writ does it on your own host, with nothing metered.

SpaceliftHCP TerraformWrit
Source and hostingClosed source, as SaaS. Self-hosted with the Enterprise planClosed source, as SaaS. Terraform Enterprise is self-managedApache 2.0, on your own host. No hosted service
PriceFree for 2 users. Starter starts at $399 a monthFree to 500 managed resources, then from $0.10 a resource a monthFree. No limit on users, runs, or resources
OpenTofuYesRuns Terraform. Its pages don’t mention OpenTofuOpenTofu 1.13.9 only. No Terraform
PolicyOPA, from the Starter planSentinel and OPA, in Standard and Premium. Free has one policy set of up to five policiesOPA, at the plan and again before the apply
Drift checksBusiness plan and upStandard and PremiumOn a schedule. No alerts yet
Audit logEnterprise planPremium planA row before each answer, in your database, except health checks, server discovery, and rate-limited requests. Nothing reads it yet

They have what Writ doesn’t: a hosted service, support, Terraform, GitHub, and notifications. If you need one of those today, choose one of them.

Facts about Spacelift and HCP Terraform come from their pricing and docs pages, read 2026-11-16. The comparison page has each source, and adds Atlantis, OTF, Terrakube, env zero, and Scalr.

Running tofu from GitLab CI today? Read Writ compared with plain GitLab CI

What Writ isn’t, yet

  • Version 0. Until 1.0, a minor version can change behavior.
  • OpenTofu only. Writ runs OpenTofu 1.13.9 and no other version, and it doesn't run Terraform.
  • GitLab only. GitLab is the only Git host Writ reads, and its CI jobs are for GitLab CI.
  • AWS roles only. The plan and apply roles are AWS roles.
  • Not proven in a real cloud account. The tests run real OpenTofu and real providers against local stand-ins.
  • One node, on Linux. A second writ serve on the same database fails the other's work.
  • No notifications. You see plans, drift, and runs in the control UI and the API.
Status and limits

What you can check yourself

  • The code. Apache 2.0, one Go binary, with its records in your Postgres. The repository
  • The tests. The end-to-end tests run writ against OpenTofu 1.13.9 and real provider binaries. None of them reaches a real cloud. How it’s tested
  • The audit log. Writ writes a row before it answers a request, and the request fails if it can’t. Health checks, server discovery, and rate-limited requests leave no row. The audit log

Run it on your machine

writ serve --dev runs a control plane of your own, on loopback, with its records in SQLite.

  • You don’t need a cloud account.
  • You need Linux, minisign, Git, and OpenTofu 1.13.9.
  • The install script checks the release’s signature. Install has the other ways.
Install Writ and start the dev control plane
$ curl -fsSL https://github.com/mr-karan/writ/releases/download/v0.1.0/install.sh | sh$ export PATH="$HOME/.local/bin:$PATH"$ writ version$ writ serve --dev
In a second terminal, plan a commit and apply the plan
$ writ plan --remoteOpenTofu 1.13.9 plan of app@dev  + random_pet.name (create)Plan: 1 to add, 0 to change, 0 to destroy.It needs no approval. Apply it with: writ apply --remote 7ff2ad97b106fcbf4b4633baee25626a$ writ apply --remote 7ff2ad97b106fcbf4b4633baee25626aOpenTofu apply of app@dev  random_pet.name: create completeApply: 1 added, 0 changed, 0 destroyed.State version 1 of app@dev.

Output of a real run, 2026-11-16, with some lines cut. The quick start has the stack and every line.

Questions

Does Writ run Terraform?

No. Writ runs OpenTofu 1.13.9 and no other version.

Does it work with GitHub?

Not yet. GitLab is the only Git host Writ reads, and its CI jobs are for GitLab CI. Nobody has run those jobs on a real GitLab yet.

Should I move production to it?

Not yet. Writ is at version 0, and no test has reached a real cloud account. Status and limits lists what’s built, how it’s tested, and what’s missing.

What does it cost?

Writ is under the Apache 2.0 license, with no limit on users, runs, or resources. You pay for the host and the Postgres you run it on.

Where does my state live?

A new stack can use the http backend that writ serve serves, where each state is encrypted with its environment’s key and versioned. A stack on backend "s3" keeps its bucket.

How does it compare with Atlantis and the paid control planes?

The comparison page covers Atlantis, OTF, Terrakube, Spacelift, HCP Terraform, env zero, and Scalr, each with its source and date, and says what those tools have that Writ doesn’t.

Start with one stack.

Run Writ on your own machine first. It’s open source, and you don’t need a cloud account.