Blueprints

Validated operating patterns with explicit environment posture, guardrails, and versioned implementation surfaces.

A blueprint is not a one-off environment file. It composes stable module contracts with policy profiles, environment state, and replaceable implementation packs so the same operating pattern can be reused cleanly across shared foundations, drills, staging, and production lanes.

Reference Blueprints

29 reference blueprints organized by deployment scope.

On-Prem
8
  • onprem/bootstrap-netbox@v1SDN + NetBox Bootstrap
  • onprem/authoritative-foundation@v1Authoritative Foundation
  • onprem/postgresql-ha@v1PostgreSQL HA (Patroni + etcd)
  • onprem/rke2@v1RKE2 Cluster
  • onprem/rke2-workloads@v1RKE2 + ArgoCD Workloads
  • onprem/netbox-ha-cutover@v1NetBox DB HA Cutover
  • onprem/eve-ng@v1EVE-NG Training Platform
  • onprem/gns3@v1GNS3 Training Platform
Networking & Cloud
15
  • networking/wan-hub-edge@v1WAN Hub to Edge (GCP + Hetzner)
  • networking/edge-control-plane@v1Edge Control Plane
  • networking/hetzner-vyos-edge@v1Hetzner VyOS Edge
  • networking/onprem-vyos-edge@v1On-Prem VyOS Edge
  • networking/onprem-site-extension@v1On-Prem Site Extension
  • networking/gcp-ops-runner@v1GCP Ops Runner
  • networking/onprem-ops-runner@v1On-Prem Ops Runner
  • networking/powerdns-shared-primary@v1PowerDNS Shared Primary
  • networking/powerdns-onprem-secondary@v1PowerDNS On-Prem Secondary
  • gcp/gke-burst@v1GKE Burst Cluster
  • gcp/linux-desktop@v1GCP Linux Desktop
  • gcp/windows-desktop@v1GCP Windows Desktop
  • gcp/containerlab@v1Containerlab Lifecycle
  • gcp/eve-ng@v1EVE-NG on GCP
  • gcp/gns3@v1GNS3 on GCP
DR
6
  • dr/postgresql-ha-backup-gcp@v1PostgreSQL Backup to GCS
  • dr/postgresql-ha-failover-gcp@v1PostgreSQL Failover to GCP
  • dr/postgresql-ha-failback-onprem@v1PostgreSQL Failback to On-Prem
  • dr/postgresql-cloudsql-standby-gcp@v1Cloud SQL Standby in GCP
  • dr/postgresql-cloudsql-promote-gcp@v1Cloud SQL Promote in GCP
  • dr/postgresql-cloudsql-failback-onprem@v1Cloud SQL Failback to On-Prem

Full blueprint step sequences, module compositions, and runbook links are in the blueprint index.

Module Catalog

Core module families behind the current validated platform paths.

Infrastructure

SDN, virtual networks, WAN hubs, edge foundations, and image lifecycle across on-prem, GCP, Azure, AWS, and Hetzner.

  • core/onprem/network-sdn
  • core/azure/vnet
  • org/gcp/wan-hub-network
  • org/hetzner/vyos-edge-foundation
  • org/gcp/wan-vpn-to-edge
  • core/onprem/template-image
Platform

PostgreSQL HA, RKE2 Kubernetes, ArgoCD, NetBox IPAM, network-lab runtimes, edge observability, and DNS routing.

  • platform/onprem/postgresql-ha
  • platform/onprem/rke2-cluster
  • platform/k8s/argocd-bootstrap
  • platform/onprem/netbox
  • platform/linux/containerlab
  • platform/network/edge-observability
  • platform/network/decision-service
DR & Storage

pgBackRest to GCS/S3, Cloud SQL replication, object storage repos, and DNS-based failover.

  • platform/onprem/postgresql-ha-backup
  • org/gcp/cloudsql-postgresql
  • org/gcp/cloudsql-external-replica
  • org/gcp/object-repo
  • platform/network/dns-routing

Full module contracts, lifecycle runbooks, and input/output references are in the module index. Implementation packages are published through the appropriate source repositories and registries.

Governed execution model

The same blueprint can operate across environments because policy, state, and execution are separated cleanly.

Full topology: on-prem primary runtime, always-on edge decisioning, event-driven cloud burst and DR. Hover any box for detail.

Prometheus scrapes on-prem cluster metrics and remote-writes them to the Thanos edge receiver for a global view.

The Decision service evaluates policy rules against aggregated Thanos metrics. If thresholds breach, it emits action signals.

DNS cutover module executes the traffic shift. Structured run records are written to external object storage.

Cloud target cluster activates (warm or cold), DR data promotes, and failover ingress begins receiving traffic.

HybridOps Executive ArchitectureThree-zone topology showing on-prem primary, Hetzner edge decisioning, and cloud burst/DR targets with data and control flows.HybridOps v1 baseline: on prem primary, always-on edge decisioning, event-driven cloud burst and DROn Prem PrimaryHetzner Edge · Always OnCloud Burst / DRRKE2 workload clusterPrimary runtime for platform and appsPrometheus per siteScrape cluster, services, and infra metricsGitOps agentDesired state sync for on prem workloadsStateful services externalized, replicated by policy.WAN edge HA pairIPsec, BGP, floating IP, secure ingressThanos Receive + QueryGlobal metrics view for policy and opsDecisionPolicy loopDNS cutoverAction moduleRun records correlate with run IDs.Cold / warm cluster targetProvisioned only on burst or DR eventDR data targetReplica promotion or backup restore endpointFailover ingressReceives traffic after DNS cutoverExternal object storage (GCS): Long-term metrics blocks and DR drill run records. Independent from on-prem.remote_writeburst / DR triggerDNS actionmetrics blocksData flowControl / policy actionKey surfaceOn-prem · Edge · CloudAnimated pulse

For detailed signal and control mapping, see the ADR overview. The execution model page explains the contract chain in detail.

WAN topology

Hetzner edge pair, BGP peering to GCP hub, and HA VPN tunnels — as deployed by the networking blueprints.

Three-zone WAN topology connecting on-prem workloads through a Hetzner edge pair to the GCP cloud hub. BGP route exchange and HA VPN tunnels provide redundant, automatically-converging connectivity.

Workload hosts, management network, and VLAN segments on the on-prem site. Routes are advertised via eBGP to the Hetzner edge pair for onward transit.

Primary/secondary edge pair with floating IP for automatic failover. Terminates IPsec and WireGuard VPN tunnels to GCP. BGP sessions maintained across both tunnels.

Cloud Router peers with the edge pair via eBGP over HA VPN. Dynamic routes propagate on-prem prefixes into the VPC. Cloud DNS handles failover routing policy.

HybridOps WAN topology: on-prem to Hetzner edge pair to GCP hub with BGP and HA VPNON-PREMprivate rangeWorkload Hostsapp · db · k8s nodesMgmt Networkdedicated subnetVLAN SegmentsSDN-controlledPrivate ASNHETZNER EDGEWAN edge pairFloating IPautomatic failoverEdge Primaryactive · BGP upEdge Secondarypassive · standbyVPN TerminationIPsec · WireGuardPrivate ASNGCP HUBcloud hub / VPCCloud RouterBGP peer · dynamic routesHA VPN Gateway2 tunnels · 99.99% SLAVPC WorkloadsDR · burst capacityCloud DNSfailover + routing policyCloud ASNsite extensioneBGP peeringHA VPN2 tunnels · eBGPBGP route exchange propagates on-prem prefixes to GCP hub automatically on failover

Book a call

Share a little context so we can make the session useful from the start.

Prefer email? hello@hybridops.tech