Work

Built to run unattended. Still running.

A few pieces of work that show the range. Some are anonymised at the client's request; the detail is real.

software · operations · [year]

[Case study 1 title: e.g. Replacing the spreadsheet a whole department ran on]

Situation

[What the client was dealing with. Who they are in general terms, the process that lived in a file or in one person's head, what it was costing them.]

What we built

[The approach and the system. What it replaced, how it was specified with the people using it, how it handles the awkward cases, how it's maintained.]

Outcome

[Real numbers: volume handled, hours saved, errors removed, time in production. One good figure beats five adjectives.]

[stack]
infrastructure · platform · 2026

Rebuilding a multi-site hosting platform after a compromise

Situation

[Our own platform. Several live client sites on one server. A managed database upgrade exposed a fault, investigation found rogue plugins and admin users on multiple sites. Sites had to stay up throughout.]

What we built

[Immediate containment: quarantine, credential and salt rotation across all sites. Then a new platform: Ubuntu, Caddy, a PHP-FPM pool and user per site, managed MySQL, no root SSH, push-based monitoring from each site to a central Go service. Migration site by site with no downtime.]

Outcome

[Sites isolated from one another. Any compromise is now contained to one site. Monitoring reports in; silence is an alert. Figures: sites migrated, downtime during migration, time from detection to containment.]

ubuntu · caddy · php-fpm · mysql · go
integration · [sector] · [year]

[Case study 3 title: an integration or hardware project, e.g. connecting a 3PL's customers to its warehouse system]

Situation

[Placeholder.]

What we built

[Placeholder.]

Outcome

[Placeholder.]

[stack]

Want the detail on any of these?

We're happy to talk through how something was built, what went wrong along the way, and what we'd do differently. Ask.

Start a conversation