Skip to content

HybridOps — Contracting & Capability Statement

Hybrid platform engineering and automation across on‑prem and cloud—delivered through repeatable workflows, guardrails, and verifiable outcomes.

Services

  • Hybrid infrastructure & DR — Proxmox ↔ Azure/GCP designs, connectivity patterns (including NCC hub‑and‑spoke), and DR drills aligned to RTO/RPO targets.
  • Kubernetes platform engineering — cluster bootstrap and hardening, GitOps enablement, and workload delivery patterns for on‑prem and cloud targets.
  • Network automation — multi‑vendor automation (Cisco, Arista, Fortinet, pfSense) with BGP/OSPF and gateway redundancy patterns (VRRP/HSRP/CARP).
  • IaC and delivery automation — Terraform/Terragrunt, Ansible, Packer image pipelines, and CI workflows (Jenkins / GitHub Actions).
  • Observability and SRE operations — Prometheus/Grafana stacks, alerting/webhooks, and reliability guardrails tied to operational objectives.

Differentiators

  • Outcome‑driven delivery — objectives and acceptance criteria defined up front (availability, recovery, performance, cost).
  • Vendor‑neutral patterns — designs prioritise portability and operability over lock‑in.
  • Product‑led approach — work is implemented through HybridOps.Core, a licensed platform‑in‑a‑box (modules, drivers, probes, and operator CLI), not one‑off scripts.
  • Governed execution — changes are documented, workflows are repeatable, and results are captured as verification records.

Example engagements

  • Hybrid DR readiness (4–8 weeks) — baseline connectivity, observability, DR plan + drill, and stakeholder‑ready review bundle.
  • Burst‑to‑cloud enablement (2–4 weeks) — GitOps‑ready workload delivery with policy/guardrail hooks for burst and rollback.
  • Pipeline modernisation (2–3 weeks) — image factory + IaC + CI hardening with reproducible runs and traceable outputs.
  • Network automation sprint (2–3 weeks) — lab‑validated automation patterns promoted into production‑ready runbooks and workflows.

Deliverables

  • Architecture diagrams and implementation notes.
  • Runbooks and HOWTOs for repeatable operations.
  • Terraform/Ansible/Packer code and CI pipelines.
  • Dashboards and alert policies (where relevant).
  • Verification bundles mapped to agreed objectives (for stakeholders and audit trails).

Tooling and platforms

Proxmox, EVE‑NG, Hetzner, Azure, GCP, Google NCC, Kubernetes, Cisco/Arista/Fortinet/pfSense, Terraform, Terragrunt, Ansible, Packer, Jenkins, GitHub Actions, Prometheus, Grafana.

Ways of working

  • Fixed‑scope packages with explicit acceptance criteria.
  • Time & materials for ongoing engineering work.
  • Training and handover for internal teams.

Contact

  • Jeleel Muibi (London, UK; remote-friendly)
  • Website
  • Email: hello@hybridops.tech

Licensing note: Public code is published under MIT‑0 where stated per repository. Documentation is published under CC BY 4.0 where stated. Third‑party product names and logos are trademarks of their respective owners.