A contract-driven runtime for governed infrastructure operations across hybrid environments.
| 80 runtime modules |
28 reference blueprints |
52 public decision records |
8 supported targets |
An individual control system can complete its work while the wider operation remains incomplete: an authority may be stale, a dependency unavailable, a result unverified, or teardown unfinished.
HybridOps Core governs that cross-system transition through a stable operator contract across environments, lifecycle stages, and implementation changes. Native platforms remain authoritative for their own resources; Core governs whether the wider operation may advance.
A ModuleSpec defines intended capability. A Profile carries environment policy. A Driver binds execution. A versioned Pack carries implementation assets. A Blueprint composes modules into a dependency-aware lifecycle. The runtime resolves these contracts, performs preflight, executes the selected implementation, publishes outputs, and writes a structured run record.
Core governs across these handoffs:
- contract resolution: deterministic input merge, validation, dependency ordering, and environment policy
- controlled execution: driver-based dispatch through versioned implementation packs and isolated workdirs
- preflight and verification: required conditions and module probes around execution
- run records: non-secret execution records with metadata, outputs, and redacted logs
HybridOps is exercised through complete platform paths rather than isolated configuration examples.
- Authoritative on-prem foundation: source-of-truth network and platform foundation
- PostgreSQL HA recovery cycle: backup continuity, failover, failback, and controlled cutover
- Kubernetes HA platform foundation: highly available cluster foundation with GitOps delivery
See the full reference scenario library.
For installation, workstation setup, target initialisation, and first-run guidance, see the Quickstart.
Inspect a shipped blueprint locally:
hyops blueprint validate --ref onprem/authoritative-foundation@v1
hyops blueprint plan --ref onprem/authoritative-foundation@v1See the authoritative foundation blueprint or browse the Blueprint Index.
flowchart LR
spec["ModuleSpec / spec.yml<br/>intent contract"]
cli["hyops apply<br/>merge and validate"]
driver["Driver<br/>execute in workdir"]
record["Run record<br/>redacted output"]
profile["Profile<br/>policy and defaults"]
pack["Pack<br/>implementation assets"]
spec --> cli
profile --> cli
cli --> driver
pack --> driver
driver --> record
This boundary keeps intent, policy, implementation, and execution records separate. Blueprints add explicit ordering, required preflight evaluation, and guarded lifecycle operations around the same runtime path.
Run records are written under stable paths such as:
~/.hybridops/logs/module/<module_id>/<run_id>/
~/.hybridops/logs/init/<target>/<run_id>/
- Python >= 3.11
- Module-specific execution dependencies are documented with the relevant module and runbook
HybridOps Core is the public reference implementation for ongoing work in platform engineering and infrastructure automation.
See Research and External Review for published papers, implementation maps, and external technical reviews.
- Full docs and reference scenarios: docs.hybridops.tech
- Public site: hybridops.tech
- Contributing: CONTRIBUTING.md
- Security: SECURITY.md
- Reference model: Anuket CNTT