Toggle navigation

The world’s first complete technology for building and running clouds.


Over the last few decades the IT industry has evolved into complex, discrete silos of compute, network and storage, with layers upon layers of software, all provided by a multitude of vendors, focused on ever smaller parts of the puzzle. Teams of discrete IT specialists are needed to thread it all together to make something that’s useful, secure and reliable.

It’s a complexity brick wall, and global IT is charging toward it. It serves the vendors, but it doesn’t serve the customers.

No more.


Starting From Scratch

What if you ignored those silos? What if you started with a single end goal in mind and thought through every facet of the design and manufacture of meeting that end goal, stripping out the fat, ignoring convention, removing fragmentation, and fully integrating the product realisation process from the start? You could then completely transform the experience of deploying and running cloud infrastructure.

The Cloud, Transformed

You could address at source the IT skills crisis by radically simplifying the skills required. You could build a high performance, infinitely scalable, resilient and adaptable technology architecture that can operate on a fraction of the energy, and that can be inspected and audited for security and sovereignty at a level of granularity never before seen.

A Single Technology for Cloud

Aside from HyperCloud, the only way to build cloud infrastructure is by composition. It takes a deep bench of skilled engineers to stitch together the disparate components and collections of non-cloud specific enterprise software with layers of automation and orchestration. And the composition process is not only complex and time consuming, it’s also only the beginning of ongoing headaches; managing and living with composed clouds is even tougher.

A cloud technology – defined

The only way to transform the painful deployment and management of cloud infrastructure is through a technology-based approach. The concept of removing, abstracting, and automating every part of the system to distil a highly resilient and radically simple way to build and own a cloud is long overdue. HyperCloud is the first and only technology to do this.

But what does that actually mean? 

We’ve created a 10-point cloud “acid test” to differentiate between a single technology, or a “cloud by composition”.


  • Is it holistic? Cloud technology should encompass a holistic suite of ever-expanding hardware options designed as one regardless of network, storage, or compute function, running the same OS, the same firmware, and using the same NICs to maximise compatibility and efficiency, and minimise complexity.
  • Does it operate as a single fabric? Generic design or re-purposing of enterprise servers results in complexity with significant management overhead. Cloud technology should be totally dedicated and optimised to operate together as one fabric.
  • Can you audit it as one technology? To remove security risks introduced in opaque supply chains, organizations should be able to comprehensively and efficiently security audit clouds as one technology–from component and source code level all the way up through to service delivery.
  • Can it provide public-cloud-like consumption? Public clouds are the gold standard in consumption experience; true private and hybrid options should provide the same types of capabilities and overall experience.
  • Does it provide guaranteed compatibility and unified support across every layer of provision? Concerns over regression testing with every new software update or hardware release and the need for extra licences or multiple support contracts weigh down support teams. Cloud technology should free teams to focus on adding value.
  • Does it require conduits or gateways? Cloud technology should eliminate the need for conduits or gateways.
  • Can you seamlessly apply updates and patches? Manual software updates, firmware patching, and vulnerability patching is incredibly time consuming in complex cloud infrastructure and often requires downtime. Cloud technology should enable automatic and systematic application of updates and patches across the entire infrastructure.
  • Is the hardware is designed to be “cloud consumable”? There should be no single point of failure across the fabric or deep technical skill sets required for adds moves and changes. If you can operate a screwdriver, you should be able to add more nodes.
  • Does the infrastructure operate as one system? With cloud technology the infrastructure should operate as one system, managed from one IP address, with the software layer able to fully manage the hardware layer, regardless of how large that infrastructure becomes.
  • Is the cloud more performant and easier to manage as it grows? As cloud technology grows to hyperscale, it should become more performant and resilient and proportionally easier to manage and secure.

“Clouds by composition” will never pass this test.