I build the infrastructure
your business runs on.

services

What I build.

who you get

The mission. SD Tech Solutions exists to build the infrastructure a business runs on, and to keep it running. Sometimes that is an open-source stack I provision, configure and maintain myself. Sometimes it is Sophos, Microsoft 365 and the other enterprise systems you already pay for, onboarded properly and looked after. Either way the aim is the same: a resilient setup, a straight answer, and a solution that pays for itself.

I manage Windows Server, SharePoint and Microsoft 365 estates professionally — that is the day job, and it is where the standards come from. The consulting is that same work, at a scale a small business can actually afford.

What is hard to fake is a system that has been running in production for a year and someone who can tell you exactly where it breaks. Every tool on this site — the security console, the private AI, the file storage, the password vault — runs on my own hardware first. If it is not good enough for my infrastructure, it does not go on yours.

I take on a small number of clients at a time, because the person who scopes your build is the person who racks it. Everything I build is documented and reproducible — addressing plans, identity design, runbooks, versioned configuration — so your own staff or another engineer can pick it up from the paperwork if I am ever unavailable. If what you need is a help desk staffed around the clock, I will say so at the check-up and point you somewhere better suited. If you want one engineer who knows your estate by heart, that is exactly what this is.

open source

Security and management tooling I built for my own fleet, now open source. Read the source, run it on your own hardware, or have me set it up for you.

under the hood

# architecture only. Sanitised for publication.

$ systemctl list-units --type=service --state=running

  private-cloud      › files, VPN, backups on my own hardware
  web-frontends      › client sites + portals, hand-coded
  edr-platform       › self-built EDR + email gateway  [hosted in Canada]
  llm-runtime        › self-hosted models, 7B–14B, air-gapped option

$ uptime --since
  first rack years ago. rebuilt as the standards moved.
  still running.

what happens next

What happens after you get in touch.

Most people write to me when something has already started to hurt: the server is out of warranty and nobody wants to touch it, the backup has never been restored, email is unreliable, or the person who set everything up has left. From there the sequence is the same every time.

1. The free check-up. An hour of my time, on-site or remote, looking at what you actually have. You get a straight assessment of what is exposed, what is costing you, and what to fix first — in a short write-up that is yours either way.
2. Scope, in writing. What is in, what is out, what it costs, and what “done” looks like — agreed before anything is touched.
3. Build alongside the old. New systems go up beside what you have, get tested, then swap in during a planned window. Reversible at every step.
4. Handover. Documentation, credentials, and a walkthrough for whoever runs it day to day. It is yours to keep.
5. Keep it running — if you want. Patching, monitoring, backups checked and faults fixed under a light retainer, or your own team takes it from here.