Network lab continuity across ephemeral compute
Preserve EVE-NG, GNS3, or Containerlab labs across ephemeral compute, verify continuity before releasing high-resource capacity, and reconstruct on fresh hosts when needed.
Hybrid infrastructure. One operating contract.
Run governed infrastructure across hybrid environments through stable contracts, preflight validation and structured run records.
Network labs • HA platforms • hybrid networking • cloud recovery
A representative HybridOps run
PostgreSQL HA failback
hyops blueprint deploy \
--env production \
--ref dr/postgresql-ha-failback-onprem@v1 \
--executecontractresolved
preflightpassed
restoreverified
endpointpublished
recordwritten
<environment-root>/logs/module/<module_id>/<run_id>/
MIT-0 open source
29
Shipped blueprints
84
Runtime modules
52
Public ADRs
8
Execution targets
What you can run
Nine working scenarios across the catalogue. Eight are highlighted here.
Authoritative on-prem foundation
Stand up NetBox-backed IPAM, Proxmox SDN, and foundation services from a clean on-prem environment with deterministic state and repeatable rebuilds.
PostgreSQL HA failover and failback
Run PostgreSQL HA on-prem with Patroni and pgBackRest, restore the cluster into GCP during a DR event, and return it on-prem with checksum-verified application data.
Hybrid WAN edge and site extension
Use a Hetzner-hosted VyOS edge pair as the public WAN anchor, extend on-prem routes through site-extension tunnels, and exchange prefixes with a GCP hub over redundant BGP sessions.
RKE2 HA platform foundation
Bring up an HA on-prem RKE2 control plane and worker pool with a clean kubeconfig handoff, then layer GitOps and workloads on top without changing the delivery path.
Hybrid portal burst to GKE
Burst an authenticated portal web tier to GKE with GitOps, cloud-native secret delivery, and a controlled public cutover while authoritative identity and entitlement services remain upstream.
Reusable Proxmox SDN foundation
Deliver segmented VLAN-backed networking, optional host routing, NAT, and DHCP through one controlled Proxmox SDN path instead of hand-built bridge changes.
Managed PostgreSQL DR with Cloud SQL
Establish a managed Cloud SQL standby from the on-prem PostgreSQL HA source, promote it under control, and fail back into an isolated on-prem lane without touching the live service path.
Capabilities
The same operating model from initial validation through deployment, recovery, and teardown.
DR drills
Rehearsed failover and failback with structured run records, redacted logs, and a clear verification chain.
Controlled burst
Provision burst capacity only when signals and policy allow. Keep cloud spend event-driven.
Environment policy
Keep backends, approvals, connectivity expectations, and execution policy separate from the requested outcome.
Replaceable implementation
Change a versioned implementation without changing the operator contract.
Validation
Deterministic input merge with module-owned validators and preflight before execution runs.
Run records
Every run persists deterministic results, redacted logs, and published outputs that can back an incident review or audit.
Representative runtime record
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.
Execution model
A strict boundary between intent, policy, and implementation.
ModuleSpec + Profile
Intent from the module; policy and defaults from the profile
hyops apply
Merge inputs, validate the contract, and prepare execution
Driver + Pack
The driver executes the selected implementation pack in an isolated workdir
Run record
Redacted output, published values, and execution provenance
Blueprint declares the outcome
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.
Run records stay reviewable
Inputs
Merged with deterministic precedence, then validated.
Workdir
Packs are copied into an isolated workdir under the runtime root.
Run record
Stable paths with redaction by default and deterministic published outputs.
hyops blueprint deploy is the stable lifecycle entry point. The module runtime remains available for individual operations.
Choose how you run HybridOps.
Linux
macOS
Windows 11
Community
For: Evaluation, training, and first DR drills
- Community runtime and reference modules
- Linux, macOS, and Windows 11 setup
- Structured run records for every run
- No always-on cloud required
SME
For: Lean teams taking HybridOps into production
- Guided onboarding from Community
- Platform Copilot and full docs
- Academy implementation tracks
- DR drill review and rollout support
Enterprise
For: Regulated or multi-team programmes
- SME plus governance profiles
- Hardened rollout standards
- Audit-ready run records
- Training and enablement planning
Start here
Install Core and run a blueprint.
Use the Quick Start to install Core and prepare the runtime dependencies for your first target.
- Install on Linux, macOS, or Windows 11
- Pick a reference module and run hyops apply
- Inspect the run record: redacted logs, published outputs, and provenance
- Follow the quickstart runbook to extend the drill
Explore next