HybridOps documentation¶
HybridOps turns infrastructure operations that cross multiple systems into a single reviewable lifecycle. It resolves declared intent against authority, policy and dependencies; checks readiness before execution; coordinates changes through native platforms; verifies the resulting state; and retains a structured run record.
The native platforms remain authoritative for the resources they own. HybridOps provides the stable operating contract across them.
Operating path: declared intent → resolved contracts and policy → verified readiness → controlled execution → validated state → run record
Start here¶
| What you want to do | Start here |
|---|---|
| Install Core and inspect a shipped operation without changing infrastructure | Quickstart |
| Follow a complete, worked operating lifecycle | Reference Scenarios |
| Run a supported procedure | Runbooks |
| Find a capability and its design, operating and verification material | Capability Map |
| Inspect shipped capabilities and multi-step lifecycles | Module Index and Blueprint Index |
| Understand the governing contracts and design decisions | Contracts and Architecture Decision Records |
Representative paths¶
| Outcome | Worked reference scenario |
|---|---|
| Govern infrastructure from an explicit authority | Authoritative On-Prem Foundation |
| Recover a service and return it safely | PostgreSQL HA DR Cycle |
| Extend networking across sites and providers | Hybrid WAN Edge and Site Extension |
| Adopt or operate a high-resource network lab across ephemeral compute | Network Lab Continuity Across Ephemeral Compute |
| Build and operate a highly available Kubernetes platform | RKE2 HA Platform Foundation |
Reference scenarios are repeatable technical case studies from HybridOps-controlled environments. Each identifies the implementation exercised, the state verified and the resulting operating record. Externally adopted deployments are documented separately when supported by third-party evidence. Browse the wider Reference Scenarios library or use the Capability Map to trace a capability to its design, procedure and verification material.
Contributing¶
Found a documentation problem or want to discuss an implementation? Open a HybridOps Core issue with the public page link and the correction, observed behaviour or supporting evidence. For proposed changes and review conventions, see Contributing.