Techne Summit We'll be in Alexandria, 3–5 October. We've set aside a few free two-hour calls for people we meet there — bring an infrastructure problem and we'll tell you what we'd do about it. The details →

A 30-day deadline, and no room to slip.

Migration · 30-day deadline
10days of effort, inside a 30-day deadline
33% under the risk-adjusted estimate
0hrs of downtime at cutover
100% of it defined in code

An early-stage SaaS company came to us with 30 days left on their hosting contract and no way to extend it. If the cutover slipped, their product had nowhere to run — with paying customers on it.

What they had was hand-built: no infrastructure-as-code, no staging, manual backups, changes made straight on the server. It couldn't be copied across — it had to be rebuilt properly, in the time we had.

We moved it onto managed services, with separate development, staging and production environments, automated deploys, central logging, and no long-lived credentials. It went live with no downtime and no customer noticing, and came in under the estimate.

The architecture we settled on under that deadline is still what they run today.

What we inherited

one environment · changes by hand application database backups manual, if any access by hand no isolation · no tested recovery

What runs now

isolated environments · automated delivery change delivery pipeline development staging production managed data central logs scoped access · tested rollback
Anonymised from a delivered engagement: a manually operated single environment, rebuilt into an automated delivery pipeline with isolated environments and managed data services. Delivered in ten working days — five inside the risk-adjusted estimate, against a 30-day contract deadline.