Offer 01 · Mid-market
A landing zone.
Not a demo.
For energy, industrial, regional health, and mid-market operators who already run vSphere or VCF and have been told to “do AI” without a place for the data to live.
What you get
Four artifacts. Then a price to build.
Architecture for compute, storage, and model placement on the estate you already operate.
Hardware and GPU bill of materials — what to buy, what to reuse, what not to.
Data-flow and residency diagram counsel and security can read.
Phased build plan with a fixed price for the first zone.
On the metal
Built on what you already run.
VCF
Cloud Foundation 9.x
SDDC Manager, vSAN ESA, NSX, Supervisor / Tanzu. The control plane under existing VMs and new GPU-ready hosts. Certified VCF Architect and Administrator 9.x.
Data
Storage that can be named
Pure, Portworx / CSI, NFS, S3, NVMe-oF, PowerStore, Cohesity. Site-to-site replication for the path that has to survive a site loss.
AI
Inference in the perimeter
Local and air-gapped models. GPU where the workload earns it. No claim of training factories. Production inference and assistants on metal you own.
Engagement
Design first. Build second.
Design engagement
Two to four weeks. The four artifacts above. A number to implement the first zone — design in the mid five figures when the estate is real, build priced separately.
First zone
Implement what the design named. One cluster or isolated domain. Identity, storage path, model runtime, monitoring. Live, with an operate runbook.
Operate
Month-to-month retainer to keep the zone current. Leave when it stops earning its place.
Questions
Is this a VCF migration project?
It can include VCF readiness. It is not “buy VCF because Broadcom said so.” If VCF 9 is the right control plane, that is what we design. If it is not, the design will say so.
Do you train large models?
No. This is infrastructure and inference — assistants, retrieval against your own corpus — on hardware in your perimeter. Training factories are a different seat.
Can this be air-gapped?
Yes, when the estate already is. That constraint is designed in, not bolted on after a SaaS pilot.