How the work runs
Approach
Six working principles that shape every engagement.
Questions before promises
Most projects that go wrong were mis-scoped in the first conversation, not mis-built later. Expect to be asked a lot before being quoted anything — including the awkward questions about who actually controls your domains and whether anyone still has the login for the old hosting.
If the honest answer to “can you do this?” is “not well”, you’ll hear that instead of an invoice.
Everything in code
Infrastructure defined in Terraform, content in a version-controlled repository, pipelines in the repository next to what they build. Nothing configured by clicking around in a console where it can’t be reviewed, reproduced or explained six months later.
Built to be handed over
Documentation and runbooks as part of the work, not an afterthought. No proprietary tooling, no components only I can operate, no arrangement that depends on my continued involvement.
Lock-in is a business model. It isn’t this one.
Risk named early
Every migration has one thing most likely to go wrong, and it is rarely the thing being migrated. Moving an API, it’s the clients you don’t control still holding the old address. Moving anything with state, it’s the cutover window and what happens to writes during it. Moving a public endpoint, it’s DNS — usually because company email runs on the same domains, and careless nameserver changes take down the mail.
Whatever it is for your system, it gets named in the first conversation rather than discovered on cutover day.
One at a time, with a way back
Nothing moves in a big bang. Workloads move one at a time, each with a rollback path that stays available until the new version has proven itself under real load. Where traffic can be split, it gets split — a few percent first, held long enough to be boring, then more. Undoing a step should take minutes and require no heroics.
Small, boring, durable
Static hosting over servers that need patching. Managed certificates over calendar reminders. Fewer moving parts, chosen deliberately.
The goal is infrastructure you stop having to think about.