Air-gapped enterprise deployment

Problem

Mining customers in the Gulf region needed the full analytics platform, but security policy ruled out any public cloud dependency. The product assumed AWS everywhere: object storage, batch compute, managed databases. Without an answer, these deals could not close.

Constraints

• Fully air-gapped: no outbound internet at runtime, no cloud control plane.
• Customer-operated hardware with no cloud-native managed services available.
• The same codebase had to keep serving existing cloud customers, so a fork was not acceptable.

What I built

I architected and delivered a self-contained, Kubernetes-based on-premise deployment package with cloud-agnostic runtime abstractions. The centerpiece is a cloud abstraction layer that unifies AWS, Azure, and Kubernetes integrations behind a single backend interface, so application code targets one contract and the deployment target becomes configuration rather than a code path.

• A cloud abstraction layer unifying three cloud backends behind one interface.
• Kubernetes-based on-premise infrastructure replacing managed cloud services.
• Cloud-agnostic runtime abstractions that removed direct platform coupling from application code.

Result

Secure air-gapped enterprise deployments became possible without forking the product. The same release ships to public-cloud and fully isolated on-premise customers, and platform coupling across the backend dropped substantially as a side effect.