Managed hosting

Hosting is mostly about what happens on a bad day.

On a good day any host looks the same. The difference shows up when a certificate lapses, an update breaks something, or a server stops answering — and in whether anyone notices before your customers do.

UK servers Daily off-site backups Restores tested Monitored, not assumed
At a glance

What sits around the site.

hosting-platform / architecture diagram
What sits around a site on managed hostingYour siteon a UK serverManaged platformpatched & monitoredby a named teamCDN & firewallin front of the siteOff-site backupsdaily, 30-day retentionMonitoringalerts us, not youStaging copytest before production
The site is one part of it. What surrounds the site — the firewall in front, the backups held elsewhere, the monitoring watching it and the staging copy to test on — is the part that decides what happens on a bad day. Scroll the diagram sideways to see all of it.
How it is put together

Infrastructure managed alongside the application.

Most hosting problems are not really hosting problems. They are an application problem and an infrastructure problem being passed between two suppliers while the site stays broken.

We manage both, which means there is nobody to hand the question to. The same people who know how the site is built also know what the server is doing.

What that covers

  • UK-based managed servers — provisioned and sized to the platform, not sold as a tier
  • CDN and firewall in front — so routine noise never reaches the application
  • OS and platform patching — applied in scheduled windows, tested on staging first
  • Auto-renewing SSL — the certificate lapse that takes sites down is a solved problem
  • A staging environment — a copy to try the change on before production
  • A monthly report — uptime, what was updated, and anything we fixed
Backups & recovery

A backup is only as good as the restore.

Two things catch people out more often than they should: a schedule that quietly stopped running months ago, and an archive that turns out not to restore cleanly at the one moment it is needed. Both look identical to a working backup until you need one.

Held off the server

Daily, off-site, on 30-day retention — so losing the machine does not lose the backups along with it.

Restores are tested

A backup nobody has restored is an assumption, not a safeguard. We exercise the restore path rather than taking it on trust.

A way back from an update

Platform and plugin updates run in scheduled windows after testing on staging, so a bad update is reversed rather than debugged live.

Monitoring

It should alert us, not you.

The point of monitoring is that somebody who can fix the problem finds out first. If the way you discover your site is down is a customer emailing you, the monitoring has not done its job regardless of what it is measuring.

Time-sensitive issues — a site offline, or unusable to visitors — carry a published response target of 2 business hours. Retained clients can raise those by phone rather than waiting in a queue.

monitoring / coverageretained
Uptime & performanceChecked continuously
Monitored
Time-sensitive responseSite offline or unusable
2 business hours
CoverageMon–Fri, 8am to 6pm
Published
Monthly reportUptime, updates, work done
Included
Straight answers

A few things worth being straight about.

Hosting tends to be sold in absolutes. On a few points the useful answer is more helpful than the confident one.

We publish a target, not a guarantee

Our uptime figure is a 99.9% target excluding planned maintenance. It is not a contractual guarantee with credits attached, and we would rather say so than imply otherwise.

Moving will not fix a slow build

If a site is slow because of how it was built, better hosting raises the floor but does not solve it. We will tell you where the time is actually going before you move.

Support hours are working hours

Coverage is Mon–Fri, 8am to 6pm. We are not a 24/7 operation and pretending otherwise would only matter on the night it turned out not to be true.

You do not have to host with us

We support sites hosted elsewhere all the time. Hosting with us removes a handover, not a requirement.

Nothing here is locked to us

It is your site, your domain and your data. If you want to move it somewhere else later we will help you do it rather than make it awkward.

We take on a limited number

Managed properly means a named team who know your platform. That only works at a size where we can actually keep that promise.

Who this suits

Built for sites the business depends on.

Businesses running on their site

Where the website takes orders, bookings or enquiries, and time offline has a cost attached to it rather than being an inconvenience.

Agencies with client portfolios

Somewhere you can put client sites and explain the arrangement to the client, with staging and reporting you can pass on under your own brand.

Ecommerce

Where checkout has to keep working under load, and a bad update on a Friday is a revenue problem rather than a support ticket.

Questions

What people ask before moving.

What is actually included?
UK-based managed servers, daily off-site backups on 30-day retention, auto-renewing SSL, a CDN and firewall in front of the site, OS and platform security patching, uptime and performance monitoring, a staging environment, and a monthly report covering uptime, what was updated and anything we fixed.
What happens when something breaks at 2am?
Monitoring alerts us rather than waiting for you to notice. Our published SLA target is a response within 2 business hours for anything that takes a site offline or makes it unusable, and retained clients can raise those by phone rather than waiting in a queue. Coverage is Mon–Fri, 8am to 6pm.
Are the backups actually tested?
Yes. A backup nobody has restored is an assumption, not a safeguard. Restores are tested rather than taken on trust, and the backups are held off-site so a server-level failure does not take them with it.
Can you take over hosting somebody else set up?
Yes. We start with a review of the current environment, document what we find, then plan the move. Migrations are done to a staging environment and tested before any DNS changes, so the switch itself is short and reversible.
Do we have to host with you to work with you?
No. We work on sites hosted elsewhere all the time. Hosting with us mainly removes the gap where an application problem and an infrastructure problem get passed between two suppliers while the site stays broken.
Will moving actually make my site faster?
Sometimes, and sometimes not. If a site is slow because of how it is built rather than where it is hosted, moving it will not fix that — and we would rather tell you before you move than after. We will look at where the time is going first.
Next step

We will look at your site before telling you to move it.

Send us the address and the current setup. We will tell you where the time is going and whether moving would make a difference — including when the honest answer is that it would not.