Studio services / No. 08
Tech & IT services
Infrastructure is easy to overlook until a domain expires or a restore fails. We map the accounts, servers and dependencies that keep your business online, then agree who owns each one when something goes wrong.
Discuss your project ↗
01 / The brief
Who it’s for
Businesses inheriting a hosting setup, migrating servers or bringing scattered domain, email and backup accounts under control.
If your site runs entirely on a managed platform, begin with ownership, DNS and recovery access. Server administration is useful only for infrastructure your team actually controls.
02 / Scope
Inside the work
Hosting and DNS
Map domain ownership, DNS records, certificates and environments. Rehearse a cutover and document the route back.
Email and access
Review mailbox provisioning, sender authentication and the process for granting or revoking administrator access.
Recovery rehearsal
Restore a backup into an isolated environment and check that a nominated owner can use it. Record the recovery steps and elapsed time.
03 / Discovery
Where we start
Bring an account inventory, a simple architecture sketch, renewal dates and your maximum tolerable outage. Share access through delegated roles, never by putting passwords in the brief.
Explore cloud architecture decisions ↗ while preparing your brief.
Explore deployment and infrastructure automation ↗ while preparing your brief.
See how we work ↗04 / Field notes
Before you start
How do we decide how often to back up?
Choose how much recent work you can afford to lose and how quickly service must return. Those targets guide backup frequency, retention and restore testing.
Does server management include out-of-hours support?
Set the coverage window, escalation contact and response expectations in the service agreement. Monitoring alone does not establish an on-call commitment.