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.
| Spacelift | HCP Terraform | Writ |
|---|
| Source and hosting | Closed source, as SaaS. Self-hosted with the Enterprise plan | Closed source, as SaaS. Terraform Enterprise is self-managed | Apache 2.0, on your own host. No hosted service |
|---|
| Price | Free for 2 users. Starter starts at $399 a month | Free to 500 managed resources, then from $0.10 a resource a month | Free. No limit on users, runs, or resources |
|---|
| OpenTofu | Yes | Runs Terraform. Its pages don’t mention OpenTofu | OpenTofu 1.13.9 only. No Terraform |
|---|
| Policy | OPA, from the Starter plan | Sentinel and OPA, in Standard and Premium. Free has one policy set of up to five policies | OPA, at the plan and again before the apply |
|---|
| Drift checks | Business plan and up | Standard and Premium | On a schedule. No alerts yet |
|---|
| Audit log | Enterprise plan | Premium plan | A 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 CIWhat 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 limitsWhat 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