arbitor
Sign in Install in 60 seconds
Import any tfstate in seconds

Stop waiting for locks.
Start applying in parallel.

A drop-in replacement for your Terraform state backend. Plans finish in seconds. Concurrent applies succeed safely. The arbitor server runs in your network — self-hosted, against a PostgreSQL you own.

Install in 60 seconds See it run
curl -fsSL get.arbitor.dev | sh
Accord · parallel applies
Two engineers. Same state. Both succeed.
no lock contention · no failed applies
terraform.tfstate → accepting connections
alice@northwind
us-east-1
aws_lb.api applying…
aws_lb_listener.https applying…
aws_target_group.api applying…
aws_security_group.web applying…
bob@northwind
us-west-2
aws_rds.primary applying…
aws_rds_param_group applying…
aws_security_group.db applying…
aws_db_subnet_group.main applying…
Both plans accepted. No lock contention.
no waiting
60s
install footprint
0
lock conflicts
1
container · 1 database
∞
parallel applies
Drop-in replacement

The same Terraform you already use.

Point your backend config at arbitor and you're done. No rewrites, no migration tool, no downtime. Same commands, faster results.

BEFORE
# main.tf
backend "s3" {
bucket = "tfstate"
dynamodb_table = "tflock"
}
AFTER
# main.tf
backend "http" {
address = "https://arbitor.internal/state"
}
One config change. No state rewrite.
IMPORT EXISTING STATE
arbitor states import -n NAME FILE # from a local file
arbitor states import -n NAME --pull # from terraform state pull
arbitor states import -n NAME --s3 s3://... # from S3
Bring existing tfstate files. No starting from scratch.
~/infrastructure — arbitor
$ arbitor plan
Reading state from postgres://state.internal/arbitor
Refreshing 3 changed resources only
 
Plan: 2 to add, 1 to change, 0 to destroy.
+ aws_lb_listener.api_https
+ aws_target_group.api
~ aws_lb.api
 
Plan complete.
$ arbitor apply
Acquiring resource locks (3)... done
Applying alongside 1 concurrent operation
Apply complete. Resources: 2 added, 1 changed, 0 destroyed.
How it works

One container. Your database. Done.

The arbitor server is a drop-in replacement for your Terraform state backend. Point your backend config at it and you're done. State is stored in a PostgreSQL you own — not in S3, not on a vendor's servers.

Engineer A terraform apply CI / CD pipeline runs Engineer B terraform apply ARBITOR State backend drop-in for S3 + DynamoDB PostgreSQL your database state
Self-hosted
Runs entirely on your infrastructure.
Your data
State and infra metadata stay in your PostgreSQL.
No backdoor
Outbound license check only. No inbound access required.
01
Deploy
Run the arbitor server in a container. Point it at your PostgreSQL. Done in 60 seconds.
02
Connect
Update backend config in your existing Terraform. Or import an existing tfstate with one command.
03
Apply
Run terraform plan and apply as you always have. Just faster, with no locks.
Deployment

Run it where it has to run.

Some teams can't put state on someone else's servers — not for any vendor, not for any reason. Arbitor ships in two shapes so the answer is always yes.

YOUR NETWORK ARBITOR
Self-hosted
Run the arbitor server inside your own perimeter. State and infrastructure metadata stay in a PostgreSQL you operate. The only outbound traffic is a small periodic license check — no inbound access to your network required. Air-gapped license available on Enterprise.
Self-hosting guide
CLOUD REGION YOURS
Private Cloud
Dedicated stack on dedicated hardware. Pick the region, or bring your own cloud account. Nothing is co-mingled with another customer at any layer.
Private Cloud
What you get

Everything Terraform should be.

Six capabilities your current state backend can't give you. No new tools to learn — same Terraform, faster, safer.

Plans in seconds
Only changed resources refresh. Skip everything you didn't touch.
Accord parallel applies
Two engineers, same state, both succeed. No lock contention.
Upstream protection
Other engineers' work stays scoped. Out-of-scope changes blocked.
Visual dependency map
See blast radius before you apply. Understand what touches what.
Self-hosted
The arbitor server runs in your network. State stored in PostgreSQL you own.
Resource-level locking
Lock individual resources, not entire states. Fine-grained control.
Free Community tier

Replace your state backend in 60 seconds.

Self-hosted: arbitor runs in your network, against a PostgreSQL you own. No credit card. No catch.