When hosting depends on luck

If nobody owns the updates, backups or deployments, small problems turn into big ones.

  • Nobody can tell you who's responsible when the site goes down.

  • Patching, certificates and updates depend on one person remembering.

  • You have backups, but nobody has ever tried restoring one.

  • When something breaks, it's never clear whether it's the hosting or the code, or whose job it is to fix.

  • Procurement or a customer wants evidence of your controls, and you can't easily give it.

Attacks are common, and old software lets them in

Most medium-sized and large UK businesses have been hit, and unpatched software is a growing way in.

  1. Hosting

    Set up and run on infrastructure chosen for the product, with staging and production kept separate.

  2. Monitoring and incident response

    We watch uptime, performance and errors, and respond to incidents within agreed times.

  3. Patching and updates

    Security updates for the platform, CMS and dependencies, tested before they go live.

  4. Backups and recovery

    Regular backups, kept separately, and restores tested so we know they work.

  5. Evidence for your auditors

    Access, change and incident records, run under our ISO 27001 information security management system.

The small print on hosting

Three things worth checking with any host.

ISO 27001 isn't a force field

It certifies that an organisation manages information security properly within a defined scope. It doesn't make any website unbreachable, so ask what's in scope.

A backup isn't a recovery plan

Recovery needs tested restores, a runbook, the right access and an agreed time to be back online. Until a backup has been restored, it's a hope.

"99.9% uptime" needs small print

How it's measured, what's excluded, and what happens when it's missed matter more than the number.

Ten questions for your current host

Ask whoever runs your site today. The answers should be quick and specific.

  • Who do we call when it's down, and how fast do they respond?
  • When was a backup last restored, and how long did it take?
  • How quickly would we be back online, and how much data could we lose?
  • When were the platform and its dependencies last patched?
  • Who has access to production, and when was that list last reviewed?
  • How are changes tested and rolled back?
  • Where is our data hosted, and which other suppliers touch it?
  • How do you measure uptime, and what's excluded?
  • What happened in the last incident, and what changed afterwards?
  • If we left, what would we get and how long would it take?

The things people usually ask

Plain answers about hosting and security, what's involved and what we need from you. Anything else, just ask.

Do you host sites you didn't build?

Yes, after a review of the code and setup, so we both know what we're taking on.

What are your support hours?

We agree the support hours and response times with you, based on how quickly you need us.

Is our data hosted in the UK?

We choose the region with you, based on where your customers are and what your contracts require.

Ways to get started

  • Projects

    Bigger products and platforms, built end to end or with our specialists in your team.

    Typical range
    £50k to £250k+
  • Ongoing support

    Hosting, maintenance and support, on a service level set to your needs.

    Service level
    Set to your needs

If we sound like a good fit, let's talk.