Skip to content
Senior web & app development · 20 capabilities
oakstone.digital
Platform & support / capability

Hosting & domain management
that stops being your problem.

Infrastructure, DNS and deploy pipelines managed so uptime stops being your problem.

This is for you if
  • Nobody is certain where the site is hosted
  • A domain or certificate has expired without warning
  • Deploys happen over SFTP
A sharper way forward

The work should
change the numbers.

Tools we reach for
VercelCloudflareAWSTerraformGitHub ActionsPostmark

Hosting only becomes interesting when it fails, which is why it is usually inherited rather than chosen: a server someone set up in 2019, a domain registered to a former employee, DNS records nobody can fully explain, and an SSL certificate that renews by hope.

We take ownership of that layer and make it dull. Infrastructure defined in code, environments that match, deploys that roll back, and a DNS and email configuration that is documented rather than folklore.

Everything is set up in your accounts and your name. If you leave, you take working infrastructure with you rather than a hostage situation.

What's included

What the engagement
actually contains.

01

Platform selection and setup

Hosting sized to your actual traffic and team, favouring managed platforms over servers you must babysit.

02

Infrastructure as code

Environments defined in version control so staging genuinely matches production.

03

DNS and email deliverability

Records documented, SPF, DKIM and DMARC configured properly so your mail arrives.

04

CDN, TLS and caching

Edge caching, automated certificate renewal and cache rules that do not serve stale pages.

05

Deploy pipelines

Preview environments per branch, one-command production deploys and instant rollback.

06

Domain and asset custody

Registrations, renewals and access consolidated into accounts your company actually controls.

What you get
  • Provisioned infrastructure defined in code
  • Documented DNS and email configuration
  • CDN, TLS and caching rules
  • CI/CD pipeline with preview and rollback
  • Access and ownership inventory
  • Disaster recovery and escalation plan
Signals it is time
  • Nobody is certain where the site is hosted
  • A domain or certificate has expired without warning
  • Deploys happen over SFTP
  • Staging does not resemble production
Common mistakes we fix

What usually went wrong
before we were called.

  • 01Domains registered to a personal account of someone who has left
  • 02Staging that differs from production in ways nobody has documented
  • 03Deploys over SFTP with no rollback path
  • 04Email deliverability quietly broken by a missing DMARC record
How we measure it
  • Uptime and mean time to recovery
  • Deploy frequency and rollback time
  • Email delivery and spam rate
  • Certificate and renewal automation coverage
Typical timeline

1–3 weeks for audit and migration

Practicalities

What week one
actually looks like.

First week

An access and ownership audit — which is frequently the most valuable week, because it surfaces the single points of failure nobody had written down.

What we need from you
  • Registrar and hosting credentials
  • DNS control
  • A billing owner for provider accounts
  • Email provider access
Not included
  • Hosting, CDN or domain fees, which you pay at cost
  • Corporate IT or device management
  • Email support for staff mailboxes
  • Compliance certification

Scope boundaries stated up front rather than discovered in a change request.

How the work runs

Four stages, visible throughout.

01

Assess

A baseline across performance, security, accessibility and dependency risk, with findings ranked by consequence.

02

Stabilise

The urgent items closed first: exposed surfaces, failing checks, missing backups, unpatched dependencies.

03

Automate

Budgets, scans and alerts moved into CI and monitoring, so regressions are caught by machines rather than customers.

04

Review

A quarterly session on what changed, what is drifting and what deserves next quarter’s attention.

Questions buyers actually ask

Hosting & domain management, answered.

No. You hold the accounts and pay the providers directly at cost, and we manage the configuration. Marking up infrastructure creates an incentive we would rather not have, and it makes leaving harder than it should be.

Yes. We start with an access and configuration audit — which is frequently the most valuable week, because it surfaces the single points of failure nobody had documented. Migration only follows if it is genuinely worth doing.

On a modern managed platform with a CDN in front, 99.9% or better is a reasonable expectation for a marketing site or storefront. The more useful question is how quickly a failure is detected and how fast a rollback happens — both of which we make explicit.

A better brief starts here

Make hosting & domain management useful.

Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.

Start a conversation