Hosting & deployment

Somebody responsible on Monday.

Hosting is not a line item we resell - it is the half of the work that starts when the build finishes. Environments, releases, backups, monitoring and access control, with the accounts in your name so you are never locked out of your own product.

01 / THE WORK

Somebody responsible on Monday.

These are the parts that decide whether the result holds up. Open whichever matters to you.

SetupEnvironments and a repeatable release

Staging and production configured the same way, with deployment as a routine step rather than an event somebody has to be brave for.

DomainsDomains, DNS and certificates

Registration or transfer, DNS records, TLS and renewal - set up once, in your accounts, and documented.

DataBackups that have been restored

A scheduled backup nobody has ever restored is a hypothesis. We test the restore path and tell you the recovery window.

WatchingMonitoring and access control

Uptime and error monitoring that reaches a person, and access that can be revoked when somebody leaves.

InheritanceTaking over somebody else’s build

We will adopt an existing system - but only after reading it properly and telling you the truth about what we found.

ExitYou can leave

Infrastructure in your accounts, documented, so moving to another team is a handover rather than a rebuild.

02 / WHAT YOU GET

What is actually delivered.

This fits when: The build is done, or nearly done, and nobody owns what happens after launch.

  • Environment setup, domain and DNS configuration, TLS, and a repeatable deployment path
  • Managed databases with backups that have been restored at least once, not merely scheduled
  • Monitoring and access control, with the accounts in your name from day one
  • A maintenance arrangement after launch - including taking over what somebody else built

Have a question or an idea worth moving?