Run governed infrastructure across hybrid environments through stable contracts, preflight validation and structured run records.
Network labs • HA platforms • hybrid networking • cloud recovery
hyops blueprint deploy \
--env production \
--ref dr/postgresql-ha-failback-onprem@v1 \
--executeWorking scenarios across the catalogue, each backed by an end-to-end reference path.
Move new or existing network labs onto high-resource execution capacity that can be released after continuity state is preserved and verified, then reconstruct on fresh hosts when needed.
Reference implementation: EVE-NG, GNS3, and Containerlab across on-premises and Google Cloud compute.
Establish authoritative infrastructure data, segmented network state, and foundation services through one governed path with deterministic rebuilds.
Reference implementation: NetBox IPAM and Proxmox SDN across a clean on-premises environment.
Exercise verified backup, cloud failover, and controlled return through isolated recovery lanes with checksum-validated application data.
Reference implementation: PostgreSQL HA with Patroni and pgBackRest across on-premises and GCP.
Establish a resilient public edge, extend on-premises routes through redundant tunnels, and exchange prefixes with a cloud hub under one governed WAN control plane.
Reference implementation: A VyOS edge pair on Hetzner with GCP hub routing and BGP.
Bring up a highly available on-premises control plane and worker pool, publish a clean operator handoff, and layer workloads without changing the delivery contract.
Reference implementation: RKE2 with a GitOps-ready kubeconfig and workload path.
Burst an authenticated web tier into cloud capacity with governed secret delivery and a controlled public cutover while upstream authority services remain in place.
Reference implementation: GKE with GitOps and cloud-native secret delivery.
Apply one governed contract to segmented networking, optional host routing, address services, and API-only multi-node delivery.
Reference implementation: Proxmox SDN with VLAN-backed networking, NAT, and DHCP.
Establish a managed cloud standby from an on-premises HA source, promote it under control, and return through an isolated lane without touching the live service path.
Reference implementation: PostgreSQL with Cloud SQL across on-premises and GCP.
The same operating model from initial validation through deployment, recovery, and teardown.
Drivers run in isolated workdirs and persist reviewable output under the runtime root. Redaction is default.
<runtime-root>/logs/module/<module_id>/<run_id>/
driver_meta.json
driver_result.json
inputs_runtime.json
workspace_policy.json
backend_binding.json
stdout.redacted
stderr.redactedDocs and runbooks describe the wiring. The operating surface stays stable even when the implementation behind it changes.
A strict boundary between intent, policy, and implementation.
Policy, ordered stages and required evidence are explicit. Executor details stay outside the operator request.
api_version: hybridops/v1
kind: BlueprintSpec
blueprint_ref: dr/postgresql-ha-failback-onprem@v1
mode: hybrid
metadata:
outcome: On-prem PostgreSQL HA is restored from backups and publishes standard DB connection outputs.
policy:
fail_fast: true
evidence_required: true
steps:
- id: postgresql_restore
action: deploy
requires: [postgres_ha_vms]
- id: postgresql_backup_config
requires: [postgresql_restore]
- id: postgresql_dns_cutover
requires: [postgresql_backup_config]The shipped blueprint carries the complete module references, inputs, authority requirements and verification path.
`hyops blueprint deploy` is the stable lifecycle entry point. The module runtime remains available for individual operations.
For: Evaluation, learning, and initial DR drills
For: Lean teams adopting HybridOps in production
For: Regulated or multi-team programmes
Use the Quick Start to install Core and prepare the runtime dependencies for your first target.