Work with me
Practical help with private AI, server infrastructure, secure remote operations, and deployments where the site is the hard part.
Engagement paths
Technical assessment and architecture
We establish the workload, the operating constraints, the security boundaries, the budget, and who supports it afterwards. You get a requirements brief, an options comparison with the trade-offs stated plainly, a preliminary architecture, and a deployment and operations plan.
Pricing is set privately once the scope is clear. Anyone quoting a number before understanding the site is guessing.
Build, source, and deploy
Equipment selection, legitimate procurement, integration, networking, documentation, and coordinating the deployment. I identify which parts 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
An honest look at 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 will change when it is true, not before.
Marine and constrained sites
Local computing and supporting infrastructure 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 is intended to sit alongside what you already maintain, not replace it.
How an engagement runs
- 01InquiryYou describe the problem. No form gymnastics.
- 02Fit discussionA short call to work out whether this is something I should be doing at all.
- 03Scoped assessmentPaid, defined deliverables, defined end. Only when it is warranted.
- 04ProposalScope, approach, responsibilities, and what is explicitly excluded.
- 05ImplementationAgreed plan, with local specialists named where relevant.
- 06HandoverDocumentation, recovery procedures, and whoever holds the keys afterwards.
An introductory call is a conversation, not a free system design. The assessment is where the design work happens, and it is paid.
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.