5 services
Services
PayloadCMS and Next.js product work, embedded engineering inside an existing team, the Linux and NixOS layer underneath, and architecture review when the question is a decision rather than a build.
Engagements tend to take one of the shapes below. A mix of them is normal — the split is about how work gets scoped, not about who shows up.
PayloadCMS development
Over two years of professional PayloadCMS work across a wide range of products: content modelling, access control, custom admin UI, plugins, and migrations off a CMS that has been outgrown.
Details 02Next.js & TypeScript product work
Application work in TypeScript and Next.js — greenfield App Router builds, rescue work on a codebase that has stopped being fun, typed API boundaries with tRPC or gRPC, installable PWAs, and Core Web Vitals that hold up.
Details 03Embedded engineering
A senior engineer dropped into an existing team for a defined stretch — quick to fit into the process already in place, communicating in writing, and useful in the first week rather than the second month.
Details 04Linux, self-hosting & NixOS
The layer under the application: reproducible NixOS hosts, self-hosted services owned outright, and build environments that behave the same on every machine.
Details 05Architecture & technical review
Short, sharp engagements where the deliverable is a decision: a written second opinion on an architecture, an API design read, or technical due diligence on a codebase before money moves.
Details