Hosted backend
If you want a managed service rather than operating the backend yourself, KiloLock Cloud is the same idea hosted for teams that do not want to run PostgreSQL, backups, tokens, and access control themselves.
Open-source and self-hostable
Own your state.
Open-source Terraform/OpenTofu state backend you can self-host.
KiloLock is a self-hosted HTTP backend for Terraform and OpenTofu, backed by PostgreSQL. Use vanilla Terraform today. Add queryable history, conflict visibility, and smarter locking workflows when you need them.
Overview
Start with a normal backend. Keep full control of your state.
The low-risk path is intentionally simple: point Terraform or OpenTofu at KiloLock as an HTTP backend and keep working. The deeper KiloLock features are there when query, history, conflict visibility, or smarter locking workflows become useful.
Open source and self-hostable
The core project is open source, self-hostable, and meant to stay understandable to operators who want direct control over where their state lives.
Built for large states
KiloLock is shaped by the reality that some infrastructure really does remain one large shared state, and that backend tooling should help teams inspect and coordinate it more carefully.
Why KiloLock exists
Because some teams outgrow blob storage long before they outgrow Terraform.
Standard remote state backends do an important job, but they tend to treat state as one file to fetch, lock, and write back wholesale. That model is workable for many teams, yet it becomes increasingly awkward when the state is large, shared, and operationally important.
KiloLock exists to make that terrain calmer: PostgreSQL-backed state instead of only flat snapshots, queryable history instead of blind blob inspection, and foundations for narrower coordination without pretending that every advanced workflow is already finished.
What it tries to improve
- Visibility into current and historical state.
- Repair and inspection workflows around specific resources.
- Safer coordination patterns for large shared states.
- A path beyond one global lock, without hype.
What it does not claim
KiloLock is not presented as a complete replacement for every Terraform platform or as a promise that parallel apply is universally solved. The project is deliberately narrower and more technical than that.
Links
Project, documentation, and hosted path
Engineering Notes
Small technical writing, kept close to the project.
My suggestion is to keep this section lightweight: short technical notes, one clear idea per piece, and a tone closer to project documentation than product marketing. For now, these are placeholders you can replace by hand later.
Draft placeholder
Why PostgreSQL-backed state changes what you can inspect
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere, nibh vitae lacinia interdum, justo ipsum fermentum neque, non gravida orci nisl vitae lectus. Suspendisse potenti. Cras sed ante at sem pretium posuere.
Draft placeholder
What “without the global lock” actually means
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi eget odio non lorem malesuada semper. Donec feugiat, neque quis posuere varius, turpis justo porta massa, vitae malesuada risus leo eget nibh.
Draft placeholder
Query workflows, repair paths, and operator-first state tooling
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed at justo ut purus aliquet convallis. Aliquam erat volutpat. Quisque luctus, lorem quis pretium luctus, augue nisi tristique ligula, vitae gravida arcu arcu nec risus.