A global payments platform needed a real, elastic cloud — but couldn't use a public one. So we built them their own, from hardware that had nowhere else to go.
Dynamic, self-service provisioning that scales up and tears down in response to load — where all they'd had was stand-it-up-once, manage-it-by-hand-forever.
See HowThey needed a cloud. They weren't allowed to use one.
At the time, a payments platform inside one of the world's largest technology companies was barred from using any public cloud — everything had to run on-premises. But what central IT offered wasn't a cloud at all: a one-shot VM provisioning tool that stood a machine up once and then left you to manage it by hand, forever, like a pet. There was no way to provision, scale, and retire compute automatically as demand rose and fell — which is exactly what their test workloads needed as load spiked and subsided.
Meanwhile, stacks of already-purchased servers sat unused in their shipping boxes — bought, paid for, and with no room left in the "real" datacenters to rack them.
We turned the stranded hardware into the cloud they were missing. Using OpenStack, we stood up a genuine private cloud on-premises — self-service and on-demand, with dynamic provisioning, scaling, and teardown in response to load — from the very servers that had been sitting boxed for lack of datacenter space. Where central IT offered one-shot pets, engineers now got elastic capacity they could allocate and release on their own.
It was designed security-first, and locked down so tightly that the company's own security team couldn't even reach it to begin their mandatory destructive penetration test — we had to stand controls down before they could so much as attempt it.
Then the cloud got a little too popular. Teams started using it for all their testing without asking — and under the rule that anything internally penetration-tested counts as "production," that instantly made it production and triggered a required destructive test. With only the single environment we'd built and nothing to spare, we ran OpenStack on OpenStack: nested virtualization with double-NAT and network-namespace isolation gave the security team a fully isolated, destructible target that never touched the real cloud.
Boxed servers to self-service capacity
Already-purchased hardware with nowhere to live became a real, on-demand private cloud — no public cloud required, no new spend.
Dynamic scale in response to load
Provisioning, scaling, and retirement happened automatically as test load rose and fell — the elasticity a one-shot VM tool could never provide.
Passed a test it couldn't be reached to start
Locked down hard enough that the pen-testers needed controls stood down just to begin — and destructively tested safely on a nested clone of itself.
On-premises, air-gapped, or hybrid — real elastic infrastructure on hardware you own, built to your constraints.
Get in Touch