Overpass
Custody. Relationships. Drift. Impact. Transactions.
- Problem
- Infrastructure change without durable, readable state.
- Input
- Accepted Terraform or OpenTofu state the product already holds.
- Outcome
- Inventory, proven relationships, impact, drift, and a gated state transaction.
- Availability
- In development. Hosted custody is enabled per early-access partner.
by OpsDevCode
Job
Keep stored infrastructure state readable — inventory, dependency, and gated change — without treating live cloud observation as a software-delivery problem.
Overpass understands infrastructure from state it holds: inventory, proven relationships, impact from that stored reachability, drift against that understanding, and gated state transactions.
Those capabilities are implemented in the Overpass runtime. This is not live-cloud discovery, not a cloud apply engine, and not generally available. Hosted custody is enabled per early-access partner.
Overpass supplies policy-evaluable infrastructure truth from accepted Terraform or OpenTofu snapshots and proven dependency edges. Policy interprets those facts. Overpass does not continuously evaluate policy, and it does not remediate — an authorized executor does.
Current state
Implementation-backed and in development. Inventory, relationships, impact, drift, and commit exist against stored state. Do not treat Overpass as live-cloud authority or as generally available.
Owns
- Terraform and OpenTofu state custody
- Infrastructure inventory from stored state
- Relationships proven from stored state
- Impact from stored reachability, not predicted outage
- Drift against stored understanding
- Gated state transactions that do not apply cloud resources
Boundaries
- Software delivery lifecycle (Repave)
- Engineering economics (Toll)
- Cross-domain intelligent experience (Dispatch)