Preston Zen

About

I build and secure real technology. The work spans cybersecurity, server infrastructure, hardware engineering, and international sourcing, and it is increasingly pointed at one question: what does it take to run serious computing somewhere that was not designed for it?

Those four things are usually four different people. Keeping them in one head is the actual advantage. A security architecture that ignores the power budget is a document. A hardware design that ignores who will service it is a prototype. An infrastructure plan that assumes a reliable link is a plan for somewhere else.

I work across different places because the people, equipment, and practical problems are there. My usual cycle is Europe in summer and autumn, Asia in winter and spring, and a US trip in August. Specific project and conference plans change. The travel archive covers that side separately.

What I am building toward

Private AI and resilient infrastructure for constrained sites. The commercial shape of that is still being worked out, and it will get its own name and its own site when there is something real behind it rather than a landing page. In the meantime, the work happens under my own name and through the ventures below.

Speaking

I have co-presented a hands-on technical workshop at DEF CON 34. Topics I can speak to with actual material behind them:

  • Designing infrastructure that can genuinely be supported remotely.
  • Private AI outside a conventional data centre.
  • What cybersecurity changes when software controls physical equipment.
  • Lessons from field engineering and international hardware sourcing.
  • Making a credible technical demonstration rather than an impressive-looking prototype.

For an invitation, send the date, location, audience, format, organiser, length, and whether travel is covered through the contact form.

The through-line

  • Security practice

    Offensive security work and certification through OSCP and OSCE³. The habit that stuck is not the exploitation; it is assuming that anything reachable will eventually be reached, and designing the recovery before the breach.

  • Owned infrastructure

    Building and running server hardware in San Diego and Japan. Two sites in two jurisdictions, both administered from wherever I happen to be, which is the constraint that shapes everything I now recommend to clients.

  • Hardware and RF

    Designing, prototyping, and shipping detection hardware through Kaizen Labs, and teaching direction finding as a four-hour hands-on workshop at DEF CON 34.

  • Field work

    Component sourcing and field engineering under conditions where the supply chain does not cooperate. Published only at a high level.

  • Marine

    Sailing, an IYT Bareboat Skipper ticket, and a boat on the Ligurian coast. It reads as a hobby and functions as a test rig: a vessel is the most constrained infrastructure site I have regular access to.

Ventures

On the record