Bring the cloud, back to you.

For a decade the pendulum swung all the way to the hyperscalers. It is swinging back. Cost, jurisdiction, latency and plain operational control are each pulling workloads off the public cloud, and organisations are repatriating the systems they cannot afford to lose: to the edge, to on-premise racks, or into a hot standby they own outright.

The cloud is not going away. The same mission-critical workload will increasingly run in more than one place at once: a hyperscaler region, an edge site, and a rack you own. What that needs is not another closed cloud with a new landlord, but an open AWS-compatible surface that runs wherever you put it and belongs to whoever runs it. The infrastructure you depend on should never depend on a vendor for its right to exist.

Anyone can wrap an API. Few can rebuild the storage, the block layer and the compute fabric underneath cleanly enough that workloads written for AWS just work. Predastore spreads S3 objects across nodes as Reed–Solomon shards. Underneath EBS, Viperblock runs a write-ahead log behind an NVMe cache. Ask for an EC2 instance and you get a real KVM guest, with PCIe passed straight through to the accelerators. All of that took far longer than wrapping an API would have, and it is the only reason your AMIs boot unmodified.

Defence came first, because that is where the constraint is absolute: the link home goes down and the mission still has to run. Enterprise repatriation teams turned up next with the same requirement under a different name. Then the AI companies, staring at a GPU bill they could no longer justify. One platform kept answering all three, which is how a defence product became an infrastructure company.

The names come from home. Mulga is the king brown, one of the most formidable snakes in Australia. It borrows its name from the Aboriginal word for the acacia scrub of the arid centre, the country it hunts and shelters in. Spinifex grows out there too, a grass tough enough to hold the dunes together through drought and fire. Neither survives by being delicate, which is roughly the brief we gave the software.