Infrastructure & Delivery Runbooks
Shared servers survive every deploy, on purpose.
- Scale
- 25 documented runbooks
Problem
A handful of servers each host a dozen unrelated services: a website, a VPN, a monitoring stack, a database. A routine deploy or config change to one can silently take down another if nobody remembers what else lives on that box.
What we built
A registry of every shared server and what runs on it, deploy rules that write only to the paths a service owns, a post-deploy checklist that curls every co-tenant's surfaces, and runbooks for DNS and mail provisioning, backup pipelines, web image optimisation and Excel financial models.
Result
Deploys to shared infrastructure ship without taking a co-tenant down, and DNS, mail and backup work follows a written procedure.
Links
No public link. This one runs inside a customer perimeter.
Tags
Related work
Ask us about this
Brief