Open-source and self-hosted
KiloLock OSS is a self-hosted Terraform and OpenTofu HTTP backend with a PostgreSQL-backed state model, query workflows, and an optional state-engine lane for deeper coordination.
The intended low-risk adoption path is simple: use it as a backend first. Then move into query, repair, self-hosting, and advanced workflows only when you need them.
If you are here to use KiloLock, the documentation is the main destination.
Summary
KiloLock OSS is the open-source backend and self-hosted core. It covers backend protocol handling, state storage, query workflows, refresh and drift workflows, repair-oriented tooling, and the server-side foundations for more advanced orchestration.
The practical first use is still ordinary: configure a standard HTTP backend, run terraform init, and keep using Terraform or OpenTofu. Users do not need to adopt the whole KiloLock model on day one.
Today
Use it as a drop-in Terraform/OpenTofu backend first.
Run locally with Docker Compose or follow the fuller self-hosted bootstrap path.
Inspect resources, dependencies, versions, and drift through PostgreSQL-backed state data.
Use per-resource history, rollback-oriented flows, and operator repair workflows.
Documentation
The OSS page now has a proper documentation surface. Search the docs here, or open the full docs library with sidebar navigation, reference pages, runbooks, and architecture notes.
Use the full docs route for the sidebar navigation, searchable reference pages, runbooks, and architecture notes.