Deterministic Automation for Hybrid Infrastructure

Execute DR drills and controlled burst across on-prem and cloud. Every run produces redacted, deterministic evidence.

Declare what should happen. Attach policy separately. Swap tooling without rewriting.

Quickstart Book a demo

Cloud resources are provisioned on demand. Cost and environment guardrails are built into every run.

Module contracts stay stable. Profiles carry policy. Packs stay replaceable.

< 5 min

From install to first evidence run

60–80%

Cost savings vs always-on cloud

100%

Deterministic evidence on every run

Modules across 5 providers

Capabilities

A compact operator surface that stays consistent as your tooling evolves.

DR drills

Reproducible failover with structured outputs, redacted logs, and a clear verification chain.

Controlled burst

Provision burst capacity only when signals and policy allow. Keep cloud spend event-driven.

Policy profiles

Centralize backends, workspaces, retries, and toolchain policy without leaking it into module intent.

Replaceable packs

Swap Terraform (via Terragrunt), Ansible, or Packer plans without breaking the module contract.

Validation

Deterministic input merge with module-owned validators before execution runs.

Evidence-first

Every run persists deterministic results and envelopes that can back an audit trail or incident review.

Reference output

Drivers run in isolated workdirs and write evidence under the runtime root. Redaction is default.

run_evidence:
  path: <root>/logs/module/<module_id>/<run_id>/
  files:
    - driver_meta.json
    - driver_result.json
    - inputs_runtime.json
    - workspace_policy.json
    - backend_binding.json
    - terragrunt.log
    - stdout.redacted
    - stderr.redacted
  guarantees:
    redaction: true
    deterministic_payload: true
    file_mode: 0o600
    correlation_id: <run_id>

Docs and runbooks describe the wiring. The operator surface stays stable even when the toolchain behind it changes.

Execution model

A strict boundary between intent, policy, and implementation.

ModuleSpec stays clean

Intent only. No backend logic, tool flags, or secret material.

api_version: hybridops/v1
kind: ModuleSpec
module_ref: platform/onprem/postgresql-ha

inputs:
  defaults:
    apply_mode: auto
    patroni_cluster_name: postgres-ha
    postgresql_version: 16
    dcs_type: etcd
    inventory_requires_ipam: true
requirements:
  credentials: []
execution:
  driver: config/ansible
  profile: onprem-linux@v1.0
  pack_ref:
    id: onprem/common/platform/35-postgresql-ha@v1.0
outputs:
  publish:
    - pg_host
    - cluster_vip
    - endpoint_dns_name
    - apps
    - cap.db.postgresql_ha

Profiles carry policy. Packs carry implementation. ModuleSpec remains tool-agnostic.

Drivers produce evidence

ModuleSpec

Intent contract: inputs, constraints, probes

Driver

Execution engine and isolation boundary

Profile

Policy and defaults (governance)

Pack

Replaceable tool plan bundle

Evidence

Deterministic outputs and provenance

Inputs

Merged with deterministic precedence, then validated.

Workdir

Packs are copied into an isolated workdir under the runtime root.

Evidence

Stable paths with redaction by default and deterministic result payloads.

hyops apply is the stable entry point. Docs describe the wiring.

Pick the edition that fits your risk profile

Start with self-serve evaluation. Add governance, onboarding, and support as your risk profile grows.

Self-serve

Community

For: Teams validating the workflow in a lab or low-risk environment

Reference modules, docs, and demos
Evidence-first execution with redacted output
Lab profiles and practical runbooks
On-demand cloud — no always-on workload spend

Guided rollout Most common fit

SME

For: Lean IT teams and schools moving from evaluation to adoption

Everything in Community
Paid Copilot and full documentation access
Academy training for guided implementation tracks
Onboarding, DR drill review, and rollout guidance
Cost-guarded burst patterns with practical support

Program engagement

Enterprise

For: Regulated, multi-team, or multi-environment organizations

Everything in SME
Governance profiles and hardened rollout standards
Audit-ready evidence and operating model alignment
Structured training, enablement, and stakeholder support
Commercial planning for broader adoption

Start here

Run your first DR drill in minutes.

Start with the self-serve quickstart to evaluate the workflow directly. For a guided walkthrough or delivery model mapping, use the demo option at the top of the page.

Install the Community edition — no always-on cloud required
Pick a reference module and run hyops apply
Inspect the evidence output: redacted logs, result envelope, provenance
Read the runbook to go further

Open Quickstart

Explore next

Why HybridOps Use cases Academy Documentation