Info
Who runs the estate, in pictures and in words.Lenn Okuro
Network engineer and infrastructure consultant between Zurich and Nairobi. I build systems the way networks are built: every concern gets one home, every boundary is a contract, and nothing trusts the layer beside it by default.
What I build towards: infrastructure a community can own. My master's thesis (design science research, Nairobi as the case) asks who owns the digital economy of a creative scene and what it takes to keep the value where it is made. The estate on the home page is the research artifact: identity, routing, storage, build and compute on owned hardware, deployed by pull, observed by a console that treats silence as a bug.
What that means for a business: one person who can design the network, gate the access, run the delivery pipeline, stand up a content plane and write all of it down so it can be handed over. Small means, large-platform practices, no lock-in.
I write logs the way I would explain a decision to a peer. If you run a team and want to own your delivery chain, that is the conversation I like most.
Practice
What the estate is built with, and what third parties have verified.- TCP/IP · BGP · OSPF
- WireGuard mesh
- VLAN segmentation
- Split-horizon DNS
- Zero-trust access
- Identity-aware proxy · OIDC
- WAF · IDS
- Scans in CI
- Docker Compose
- Proxmox VE
- Ansible
- Pull-based deploys
- Linux · Bash
- Python · TypeScript
- PostgreSQL · Redis · S3
- Windows Server · Azure AD
- CCNA: Enterprise Networking, Security & Automation Cisco
- CCNA: Switching, Routing & Wireless Cisco
- CCNA: Introduction to Networks Cisco
- Network Defense Cisco
- Intro to Cybersecurity Cisco
- IT Essentials Cisco
- Open Source & 5G Transition Linux Foundation
- PCEP Entry-Level Python Programmer Python Institute