Introduction

Early access. Stacks is rolling out behind an organization flag. Runner minutes are metered but not yet billed.

Longbridge Stacks runs your OpenTofu the way you wish CI did: every change is planned, the plan waits for a human (unless you say otherwise), and the apply executes exactly the plan that was approved — never the branch tip.

• A Stack binds a Git repository, a path, and a branch to one OpenTofu version and exactly one state.
• A Run is one execution: a plan, then — for changes — an apply. Pull requests get plan-only Runs and a check on the PR; pushes to the tracked branch get Runs that can apply.
• Execution modes let each Stack choose how apply happens relative to merge — from the pull request branch before merge, on merge with a confirmation, automatically, or on demand.
• Dependencies wire Stacks into a graph: an upstream apply cascades to its dependents, and a dependent can read the upstream’s outputs.
• Hosted state speaks OpenTofu’s standard http backend, so any tofu CLI can use it — with locking, a full version history, and one-click restore. It works without buying anything else, and it isn’t hostage: tofu init -migrate-state moves you in or out any time.
• Run identity is the part your security team will like: each Run can present a short-lived OpenID Connect token to your cloud — AWS, GCP, Azure, or your own OpenBao/Vault — so your cloud credentials never rest with us. Plans can carry read-only trust and applies write trust.

Who it’s for

Teams who keep infrastructure in Git and want plan/approve/apply discipline without operating Atlantis themselves — and without per-user or per-resource pricing. Stacks, users, and hosted state are free; you pay for runner minutes, by runner tier.

What runs your code

Hosted Runs execute in a fresh, egress-restricted sandbox — one throwaway pod per Run — with a checksum-pinned OpenTofu from our curated catalog. It’s OpenTofu only; we don’t execute BSL-licensed Terraform. What contains a Run today, what its network can reach, and how state and secrets are protected are in Trust & isolation.

Where it is today

Early access on the eu-hel shard (Hetzner, Helsinki): hosted state, Git-driven Runs with approvals, PR plan checks, execution modes (including apply-before- merge), cross-Stack dependencies with cascade and output passing, and OIDC Run identity are live. Self-hosted runner pools and org policies (OPA) are on the roadmap.