I’m Georgios Tsotsos, and most people call me George. I’ve spent a bit over twenty years building and leading software and product engineering organizations, mostly around cloud-native platforms, edge systems, and the management planes that connect the two.

The through-line is that I’ve usually been accountable for both halves of a decision, the architecture and the business consequence of it. That is an uncomfortable place to sit, and it is also where the interesting problems are. Almost everything on this site comes out of that position.

What I Work On

Cloud-native platforms and what they cost. Multi-region SaaS, control planes, and the operating economics underneath them. I’ve led platform organizations through the phase where the infrastructure bill stops being a line item somebody in finance owns and becomes an architectural constraint that engineering has to answer for.

Regulated and sovereign environments. I’ve been through a FedRAMP Moderate authorization on Azure Government, and the controls themselves were rarely the hard part. What consumed the time was producing evidence that changes had been reviewed and approved by someone with the standing to approve them. I’ve also designed a PCI-DSS SAQ-D environment and run the engineering organization that operated it, and worked under SOC 2 and more recently against the EU AI Act. The pattern holds across all of them: the regime is usually reasonable, and the difficulty is whether your systems can produce the evidence as a by-product of running normally.

Machine learning and AI in the delivery process. I’ve designed ML systems in production and run the organizations that built them, on log analysis at scale and on pricing. What occupies me now is a different question: what happens to an engineering organization when a large share of its code is generated rather than written, and who is accountable for the outcome when it fails.

Edge computing and device fleets. Broadband gateways, CPEs, Wi-Fi access points, set-top boxes. The management planes that keep millions of multi-vendor devices patched, configured and observable across intermittent connectivity, built on open standards like the Broadband Forum’s User Services Platform (TR-369) and open-source baselines like prplOS.

What I Write Here

This site is where I work through the engineering and leadership questions I’m dealing with anyway. Four recurring threads:

  • AI architecture. Agentic systems, edge AI, and the operational realities of running inference at scale rather than in a demo.
  • Engineering governance. Accountability, audit evidence, and how organizations adapt when AI changes who makes a decision and who can be asked about it later.
  • Platform engineering. Cloud-native and edge infrastructure, control planes, and the trade-offs that decide whether a system holds up under load.
  • Leadership at scale. How technical decisions reach customer value, regulatory exposure, and organizational outcomes, usually later and less directly than anyone plans for.

I try to keep the arguments defensible and the sources checkable, and I’d rather be corrected than be vague. Views here are my own. No current or previous employer reviews or approves them.

Talks and Standards

I speak at industry and open-source conferences, mostly on edge platforms, broadband architecture and container management at the device level.

All of these were given in a vendor role, for companies I worked for at the time. Each page links the original recording. The write-up is my own.

I follow the work at the Broadband Forum, the prpl Foundation, the Linux Foundation and the CNCF closely enough to have opinions about it, and I’m a member of the IEEE.

Elsewhere

LinkedIn · GitHub · X · ORCID 0009-0004-2813-952X