Overview
I design and operate the platform layer: hypervisor clusters, shared storage, directory and identity services, DNS/DHCP/IPAM, certificate services, and the hybrid links that tie it to your cloud footprint.
Designs are sized against measured workload, not vendor sizing calculators, with explicit failure-domain and maintenance-window behaviour.
Lifecycle matters more than the build. I take on patching cadence, firmware baselines, capacity review and end-of-support tracking so the estate does not quietly rot.
What you receive
01Hypervisor cluster design and build
02Storage sizing, tiering and replication
03Identity, DNS, DHCP and IPAM services
04Hybrid cloud connectivity
05Patch and firmware lifecycle programme
06Capacity and end-of-support register
Outcomes I hold myself to
- Predictable maintenance with no user-visible impact
- Documented recovery paths for every platform service
- No surprise end-of-support exposure
Common questions
Do you support Proxmox in production?+
Yes, including clustered deployments with Ceph or ZFS replication and documented DR procedures.
Can you take over an existing estate?+
Yes, via a discovery and stabilisation phase before I accept operational responsibility.