Preston Zen

Work with me

Practical help with private AI, server infrastructure, secure remote operations, and deployments where the site is the hard part.

01

What I sell

An hour of my judgement

This is the one thing I sell personally. You describe the problem — what has to run, where, and what happens when it stops — and I tell you what I would actually do, what I think it costs, and whether I am the right person for it. No deck, no discovery process, no deliverable afterwards.

  • A straight answer on the approach, including the option you have not considered
  • The risks that matter, separated from the ones that do not
  • What this realistically costs and how long it takes
  • Whether to hire me, hire someone else, or do nothing yet

Paid, because the value is in the hour itself rather than in what it sells. If it becomes clear early that I am not the right person, I say so and refund you.

02

Where the delivery happens

The call is mine. The work that follows it is delivered through Private Compute Systems, which does fixed-fee assessments, fixed-price builds, and managed operations. One company, one contract, scoped and priced there rather than here.

Build, source, and deploy

Equipment selection, legitimate procurement, integration, networking, documentation, and coordinating the deployment. I name the parts that are regulated work for a licensed local specialist and bring them in, rather than pretending the boundary does not exist.

No claim of unlimited geography or automatic on-site availability. Where I can be present I will say so; where I cannot, we plan around it.

Secure remote operations

Management access, monitoring, backup and recovery, identity, patching, and local escalation. The question is always the same: when this breaks and you are somewhere else, what actually happens next?

There is no 24/7 coverage and no numeric SLA on offer, because there is no staffed operation behind one. That changes when it is true, not before.

Marine and constrained sites

Local computing aboard vessels and at off-grid or remote sites, starting with non-safety-critical applications: offline document and manual search, approved knowledge tools, local services that survive a dropped link.

No autonomous vessel operation, no navigation advice, no integration into propulsion or safety systems. If you are an integrator, electrician, or ETO, this sits alongside what you already maintain.

03

How an engagement runs

  1. 01The callOne hour with me. You leave knowing what you would do next, whether or not you hire anyone.
  2. 02Scoped assessmentFixed fee, defined deliverables, defined end. Run through Private Compute Systems.
  3. 03ProposalScope, approach, responsibilities, and what is explicitly excluded.
  4. 04ImplementationAgreed plan, with local specialists named where relevant.
  5. 05HandoverDocumentation, recovery procedures, and whoever holds the keys afterwards.
04

What to tell me

  • What needs to run?
  • Where will it run?
  • What are the power and connectivity constraints?
  • Who owns and administers the data?
  • What is the timeline?
  • Who will support the physical site?

Partial answers are fine. “Not yet defined” is a real answer and is on the budget dropdown for that reason.

Tell me what cannot fail.