I build infrastructure. Servers, networks, storage, websites, software.

Client infrastructure

The everyday work of the business: Linux servers running containerised services, multi-drive ZFS arrays past 100 TB with redundancy and capacity planning, and UniFi networks covering multi-room properties end to end, including the access points, controller, routing, firewall rules and the cabling underneath.

Most of it is unglamorous and load-bearing: a storage pool that can't lose data, a server that has to come back by itself after a power cut, a network that has to reach the far corner of a property. I scope, quote and build it, and I'm the person answering when something breaks at an inconvenient hour.

Edecy AI Live

A private AI assistant running entirely on hardware I own: chat, image understanding, image generation and video, with no third-party model API behind it. Invite-only accounts, an admin console, and per-person permissions for the capabilities that are expensive to run.

The interesting problem was sharing one GPU. A single card can't serve everyone at once, so the service watches its own memory pressure and drops to a smaller model when it has to, then says so on screen. It reaches the internet without opening a port, and the public half holds no code capable of touching the host it runs on.

RXANGEL storefront

A producer with 281 beats needed somewhere to sell them that wasn't handing a cut of every sale to a platform. I designed the shop around his own artwork, wrote the site, and built him a separate admin panel so the thing isn't dependent on me: he uploads a track, sets a price, edits a licence, presses publish, and the live site has it about twenty seconds later.

Two parts were harder than they look. His catalogue came in with a 13 dB loudness spread, which on a shop page means every third beat makes you reach for the volume, so each track now carries a measured gain and the player levels them as they play. The panel is also open to the internet, because he needs it from anywhere and installing something was never going to happen, so uploads are treated as hostile by default: files are identified by their contents rather than their extension, every filename is regenerated before it touches disk, and the login check runs before the request body is read at all. What the shop serves is a transcode, so his master recordings never leave his own drive.

The part I'd point at, though, is the handover. He runs it. I haven't had to touch the catalogue since. The catalogue has now started running itself as well: a scheduled sync imports his new releases, levels them and publishes them with nobody at the keyboard.

This website

You're reading it. Hand-written HTML, CSS and JavaScript. No framework, no build step, no dependencies, no npm install. It's served from Cloudflare Workers and the whole thing deploys in about twenty seconds.

The parts I'd point at: the readouts are real, so the memory meter on this page is the actual graphics card a few seconds ago and goes dark when the machine is off. The RXANGEL card reads his own catalogue, so it updates when he publishes rather than when I remember to. Fonts are self-hosted, which is why these pages make no third-party request beyond the host's own analytics. It carries a content security policy and the rest of the headers, passes WCAG AA contrast, and works from 320 px up.

Open the source if you want. Building it this way is the point.