If you operate critical infrastructure, you currently procure two things separately and hope they fit: the network, and the systems that run on it. That seam is where the problems start — in availability during a crisis, in demonstrating compliance to the regulator, and in the question of who carries responsibility when it matters.
DFNZ and Netz 33 have entered into a partnership to close that seam.
The network
Netz 33 is building a nationwide, highly meshed fibre backbone from a single source, multiply redundant and, according to the company, designed to meet the requirements of NIS2 and the German KRITIS umbrella act. What matters here is less the bandwidth than the design principle: an infrastructure that holds even when parts of it fail.
The systems
DFNZ contributes the layer above: AI-supported software, cyber security, sensor fusion and highly integrated system architectures. What sets us apart is the serial-production logic we bring from the automotive industry. Systems that are certifiable, testable and scalable — not one-offs, but reproducible series with demonstrable quality across the full lifecycle.
Why the two belong together
Digital sovereignty is explained often and built rarely. It does not emerge on a single layer, but across the entire stack: from the fibre in the ground to the application running on it. That continuity is the reason for our partnership — and the point where operators of critical infrastructure have the greatest leverage today.
“Sovereignty is not created where it is declared, but where network and system actually fit together,” says Eric Voss, Managing Director of DFNZ. “Netz 33 is building an infrastructure that holds under load. We bring the systems that run on it — with the serial-production logic of the automotive sector: certifiable, testable, scalable. For operators of critical infrastructure, that means the responsibility at the interface no longer rests with them alone.”
What drives us
DFNZ was founded on a simple observation: in defence and in critical infrastructure, capability only counts once it exists in relevant numbers, on a timeline that matches the threat. A prototype that convinces in a demonstration and then takes years to reach the field is not an answer. Bringing the engineering discipline of serial production into these domains is the reason this company exists.
This partnership applies that principle to a layer that has long been treated as somebody else’s problem. Networks are built by network people, systems by system people, and the interface between them is where availability, security and accountability quietly go missing. Closing it is not a technical detail. It is the difference between infrastructure that is resilient on paper and infrastructure that holds when it is tested.
Design. Deliver. Defend.
