Infrastructure and network engineering
Infrastructure is judged on its worst day. Everything else is marketing.
A network that works when nothing is wrong is table stakes. The engineering question is what happens when a link drops, a certificate expires, a disk fills, or a provider has a bad afternoon — and whether anyone finds out before the users do.
We design, build and operate Linux-based infrastructure: routing and switching, segmentation, VPN and remote access, virtualisation, containers, reverse proxies, storage and backup. Everything is documented as built, monitored with intent, and reproducible from configuration rather than memory.
Where this usually starts
01
Growth without structure
The network grew one device at a time and now nobody can explain the topology. We document what exists, remove what should not, and design the structure that the next three years need.
02
Backups that were never tested
A backup job that reports success is not a recovery plan. We design restores, test them, and make the evidence part of the routine.
Adjacent layers