Home›Services›OpenTofu pipelines in GitLab

Run OpenTofu from merge requests — in the GitLab you already have

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.

from $4,000 · fixed price Measured first, then fixed price and dates Works on GitLab Free, Premium and Ultimate
The problem

Applies from laptops — or one more platform to pay for and run, next to GitLab.

What we do

State, plan in every merge request, apply after approval and drift checks — in GitLab CI.

The result

Every infrastructure change reviewed and recorded where your code already lives.

Is this you?

The options, honestly

OptionWhat it isTrade-off
Laptop appliesEach engineer runs plan and apply locallyNo review, no record, credentials on laptops
AtlantisOpen-source pull-request automation, self-hosted; a CNCF sandbox project1Free and proven — but one more server, with its own permissions
Spacelift, env0 and similarCommercial IaC platformsRich features; another vendor, another bill, another login
GitLabState backend, CI pipelines and merge-request approvals you already run2Fewer advanced platform features; everything in one place

How it works in GitLab

What you get

Pipeline template

One include per project: format, validate, security checks, plan, apply.

State moved

State from S3, Atlantis or your platform moved into GitLab, with a plan showing no changes.

Access rules

Who can plan, who can apply, which environments are protected; cloud credentials per environment.

Drift checks

Scheduled plans with alerts to the owning team.

Handover

Short guide for engineers and a session with your team.

How it goes

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.

  1. Step 1 · 1–3 days

    Measure

    Projects, environments, current workflow and permissions; fixed price.

  2. Step 2

    Build

    Template, state, access rules on one pilot project.

  3. Step 3

    Roll out

    Remaining projects in batches; old server or platform switched off at the end.

What we need from you

  • Maintainer access to the GitLab groups in scope.
  • Cloud credentials per environment (or permission to create them).
  • A list of who may apply where.

Not included

  • Rewriting your IaC code.
  • Features specific to commercial platforms, such as built-in cost estimation — we tell you in week one if you rely on them.
from $4,000

Fixed price after the measurement in step 1. Paid by milestone.

What changes the price

  • Number of projects and environments.
  • Where state lives today.
  • Approval rules you need.

Coming from Terraform Cloud? See Terraform Cloud → OpenTofu + GitLab.

Questions teams ask

Is Atlantis bad?

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.

Do we need GitLab Premium?

No. Premium adds enforceable approval rules; on Free we restrict who can apply through protected branches and roles.

Does this work with Terraform instead of OpenTofu?

Yes, the same pipeline works with either. We default to OpenTofu because it is open source.

Often done together

Tell us how you run plan and apply today

Laptops, Atlantis or a platform — and how many projects. Enough for a price range.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. Terraform is a trademark of HashiCorp, an IBM company. Spacelift and env0 are trademarks of their owners.
  1. CNCF: Atlantis project page
  2. GitLab docs: GitLab-managed OpenTofu state
  3. GitLab: OpenTofu CI/CD component
  4. GitLab Docs: Merge request approval rules
Book a 30-minute call