Hello, I’m Kyriakos

Senior Infrastructure Engineer with over twenty-two years of experience in infrastructure, security, and network integration. Based in Leiden, Netherlands. Building things on the internet since 1999, networks since 2004.

I am now building open-source communications and infrastructure tools. The connection to my previous work is practical: people still need information when networks fail, and automation needs limits when it touches systems people depend on.

The Journey

My career path started where many of us from the early 2000s Greek tech scene began: internet cafés, helpdesk, and fixing things that weren’t supposed to break. From there, I progressed through technical support, systems administration (both Microsoft and Unix/Linux), network engineering, and eventually specialized roles in critical financial infrastructure.

During the last two decades, I’ve held positions ranging from maintaining navigation systems for 800 taxis, to implementing COMSEC for classified military communications, to engineering SWIFT banking infrastructure at Adyen. Security was a primary duty in most of those roles — it tends to follow you once you’ve had a clearance.

My career has mostly been within structured, conservative organizations. When things got too comfortable, I moved on — always looking for the place where I’d learn the most.

Notable Roles

  • Adyen — SWIFT Engineer on Adyen’s banking infrastructure. Compliance, HA, security — working closely with treasury and infrastructure teams
  • Doctors Without Borders (MSF) — Senior IT Infrastructure Lead supporting humanitarian operations in conflict zones and disaster areas worldwide
  • SWIFT — Network Engineer for global financial messaging infrastructure
  • European Space Agency (ESTEC) — Systems Administrator for mission-critical applications, adhering to ESACERT (ESA’s Computer Emergency Response Team) security guidelines
  • 476th Electronic Warfare Battalion — COMSEC/INFOSEC implementation for classified communications (Hellenic Army, compulsory service that turned into actual security work)

What I build, and what I own

After twenty years of managing other people’s infrastructure, I wanted to own the whole loop: the problem, the architecture, the test and the thing that wakes me up at night.

I use AI coding tools extensively. I decide what gets built, set the architecture and operating boundaries, review and test the output, and take responsibility for the result. For MeshSat, that includes a team: Elli assembles hardware and leads QA; George advises on PR and marketing. Our public account of the work explains the division of responsibilities.

MeshSat joins radio, satellite and mobile networks. It is a prototype preparing for a funded field-validation programme. Territory Grounder applies lessons from my earlier Agentic ChatOps platform to governed incident investigation and remediation. CubeOS and MuleCube address local self-hosting and portable offline computing, with beta software and pre-production hardware respectively.

The Products page keeps the capabilities, limitations, external support and commercial status together. Now records the current activity without turning every repository into a business plan.

The place I learn by breaking my own things

The lab is my hands-on environment for Kubernetes, BGP and infrastructure-as-code. My professional background is networks, systems and security; the lab is where I extend that experience and test the parts nobody else has to depend on yet. It is overkill for a homelab. That is part of the point.

The June 2026 inventory counted 13 Kubernetes nodes across two sites: 7 in the Netherlands and 6 in Greece. Earlier references to 7 described the Netherlands cluster alone. A Netherlands snapshot from 28 October 2026 still records 7; a comparable current whole-estate count has not been verified. Historical counts are not live capacity.

Get in Touch