Preserve declared lab state, release high-resource capacity, and reconstruct network emulation environments on fresh local or cloud compute.
Reference implementation: EVE-NG, GNS3 and Containerlab across local, on-premises and Google Cloud execution environments.
Hybrid infrastructure. One operating contract.
Carry one infrastructure operation across authority, readiness, execution, verification, recovery and closure while each platform remains authoritative for its own state.
Network labs • platform foundations • hybrid networking • disaster recovery
platform/postgresql-hahyops apply \
--env production \
--module platform/postgresql-ha \
--inputs postgresql-ha.ymlRepresentative outcomes
Three exercised paths from the wider public catalogue.
Establish authoritative network and platform state, then provision downstream services from governed intent across a clean on-premises environment.
Reference implementation: NetBox IPAM and Proxmox SDN across an authoritative on-premises network and service foundation.
Protect application state, execute verified failover, and control service return through isolated recovery paths with current endpoint and checksum validation.
Reference implementation: PostgreSQL HA with Patroni and pgBackRest across on-premises and Google Cloud recovery targets.
One governed operation
The contract stays stable while the selected implementation and resource authority do their own work.
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 module spec selects a versioned execution profile and pack without changing the blueprint contract.
api_version: hybridops/v1
kind: ModuleSpec
module_ref: platform/postgresql-ha
requirements:
credentials: []
inputs:
defaults:
apply_mode: auto
inventory_requires_ipam: true
execution_plane: workstation-direct
execution:
profile: onprem-linux@v1.0
pack_ref:
id: onprem/common/platform/35-postgresql-ha@v1.0
outputs:
publish:
- endpoint_host
- endpoint_port
- cap.db.postgresql_haValidated inputs, execution evidence and published outputs are retained together, with secrets redacted.
Choose how you run HybridOps.
For: Evaluation, learning, and initial DR drills
- Open-source runtime and reference modules
- Public documentation and walkthroughs
- Linux, macOS, and Windows 11 setup
- Structured run records for every run
- No always-on cloud required
For: Lean teams adopting HybridOps in production
- Adoption and architecture assessment
- Greenfield or brownfield implementation planning
- Guided onboarding and rollout support
- Recovery and DR drill review
- Implementation guidance and team handover
For: Regulated or multi-team programmes
- Multi-team governance and operating profiles
- Hardened implementation and recovery standards
- Audit-ready run records
- Training and organisational enablement
- Continuing technical advisory
Run HybridOps once.
Complete a credential-free operation, inspect its record, then continue with a reference path for your environment.
- Install on Linux, macOS, or Windows 11
- Run hyops quickstart without cloud credentials or external tools
- Inspect the resulting state, verified artifact, and structured run record