Many teams run infrastructure changes from laptops, from a separate Atlantis server, or through a paid platform such as Spacelift or env0. GitLab can do the core of it: store state, show the plan in the merge request, apply after approval, and check for drift. One system less to run, one permission model.
Applies from laptops — or one more platform to pay for and run, next to GitLab.
State, plan in every merge request, apply after approval and drift checks — in GitLab CI.
Every infrastructure change reviewed and recorded where your code already lives.
apply from their laptops, and you find out about changes afterwards.| Option | What it is | Trade-off |
|---|---|---|
| Laptop applies | Each engineer runs plan and apply locally | No review, no record, credentials on laptops |
| Atlantis | Open-source pull-request automation, self-hosted; a CNCF sandbox project1 | Free and proven — but one more server, with its own permissions |
| Spacelift, env0 and similar | Commercial IaC platforms | Rich features; another vendor, another bill, another login |
| GitLab | State backend, CI pipelines and merge-request approvals you already run2 | Fewer advanced platform features; everything in one place |
gitlab-tofu wrapper, pinned to an OpenTofu version.3apply runs only after merge, from protected branches.One include per project: format, validate, security checks, plan, apply.
State from S3, Atlantis or your platform moved into GitLab, with a plan showing no changes.
Who can plan, who can apply, which environments are protected; cloud credentials per environment.
Scheduled plans with alerts to the owning team.
Short guide for engineers and a session with your team.
The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.
Projects, environments, current workflow and permissions; fixed price.
Template, state, access rules on one pilot project.
Remaining projects in batches; old server or platform switched off at the end.
Fixed price after the measurement in step 1. Paid by milestone.
Coming from Terraform Cloud? See Terraform Cloud → OpenTofu + GitLab.
No. It is open source, free and widely used. Teams move to GitLab mainly to run one service less and to keep permissions in one place.
No. Premium adds enforceable approval rules; on Free we restrict who can apply through protected branches and roles.
Yes, the same pipeline works with either. We default to OpenTofu because it is open source.
Laptops, Atlantis or a platform — and how many projects. Enough for a price range.