planning window
10-20 weeks
depending on configuration and acceptance
built in the Netherlands for workloads that cannot sit in someone else's cloud
Delta Kern is building air-gapped and relocatable container datacenters for defense, government and critical infrastructure, with Dutch operations, hardening and workload enablement layered on top.
planning window
depending on configuration and acceptance
operating modes
built for fixed sites, remote sites and field deployment
control model
hardening, monitoring, patching and lifecycle under national control
why this exists
Delta Kern sits between generic hardware supply and fixed sovereign cloud. The proposition is simple: Dutch-controlled compute where continuity, control and deployability matter more than cheapest shared infrastructure.
The moat is not the container itself. It is the control model, the deployment playbooks and the repeatable operations around it.
For new contracts since January 1, 2026, public buyers are asking harder questions about security, control and dependency.
Programs such as GPT-NL are pushing transparency, governance and public values into the infrastructure layer.
The Dutch defense budget for 2026 stands at €26.8B, with more focus on digital resilience and dual-use innovation.
Containerized modular datacenters are proven. The gap is the operating model, delivery playbooks and workload enablement.
product stack
The first commercial wedge is storage, private cloud and secure inference. Every deployment is supported by a managed operating model instead of a one-off infrastructure project.
rapid deployment
1-3 racks for field compute, offline-first workloads and local continuity where links cannot be assumed.
sovereign baseline
Air-gapped or connected private cloud, storage and backup capacity for workloads that need tighter control.
mission AI
Secure on-prem inference with liquid-cooled GPU options for protected AI workloads close to the data.
service layer
Architecture, networking, workload design, MLOps and hardening that turn the pods into operating capability.
where the first demand sits
The initial market does not need to be broad. A small set of early partners with real continuity requirements is enough to prove the delivery, security and operational model.
25
safety regions
21
water boards
342
municipalities
Forward compute, local storage, sensor fusion and continuity when links degrade or disappear.
Temporary crisis-site capacity, resilient data hubs, mobile backup and offline collaboration.
Air-gapped processing, sovereign backup and shielded workloads outside shared hyperscaler environments.
Ports, water, energy and utilities that need local analytics, resilient systems and controlled data paths.
delivery model
The container format wins because it compresses deployment into a repeatable cycle. Customers buy sovereign capacity, service and outcome instead of a one-off construction project.
01
Racks, power, cooling and security controls are assembled off-site into a known operating envelope.
02
Thermals, failover, networking and workload stacks are validated before transport.
03
Capacity moves to a fixed site, remote site or temporary mission location as a productized unit.
04
Deployment starts with known assumptions for power, cooling, access and security controls.
05
Monitoring, upgrades, hardening and support stay under a Dutch-led operational model.
Faster to capacity
Planning assumption of 10-20 weeks, depending on configuration and customer acceptance.
Repeatable engineering
Known thermal, power and security envelopes reduce one-off design risk.
Mobility and resilience
Pods can move, duplicate and serve as continuity assets when the operating context changes.
Cleaner commercial story
The offer bundles sovereign capacity, managed operations and mission outcomes into one model.
coming soon
The near-term focus is design partners, pilot customers and aligned ecosystem relationships across defense, public sector and critical infrastructure.
air-gapped modes
private cloud and storage
secure inference
managed ops