Services / Servers & Hosting

Servers that stay up.And someone who notices when they don't.

VPS, cloud, performance, monitoring and migrations.

We build, patch and watch Linux servers, and we run more than 130 live websites on our own. Yours gets the same treatment: the right amount of machine for the job, kept current, watched, and backed up somewhere that isn't the machine itself.

What you get

Built for the actual workload

Ubuntu, nginx, PHP, MySQL and Redis, sized and tuned for what your site really does rather than a plan off a price list.

Patched and current

Operating system and service updates applied, and PHP versions moved on before they stop getting security fixes.

A CDN and a firewall in front

Pages and assets served from edge locations, with a web application firewall filtering the traffic before it reaches your server.

Certificates that renew themselves

HTTPS set up with automatic renewal, and a check that the renewal actually ran. Expired certificates are an avoidable outage.

Backups off the server

Kept somewhere separate, so a dead machine is an inconvenience rather than the end of the business.

Monitoring, and a human

We watch uptime, certificates, disk and load, and you hear from us when something needs doing.

How it works

  1. Look at what you haveWhat is running, where, on what, and who has the logins. Often that inventory is the first time anyone has written it down.
  2. Plan the buildWhat moves, what gets rebuilt, what gets retired, and the order it happens in.
  3. Build and test out of sightThe new setup runs on a private address while we test it, so nothing changes for your customers until it's right.
  4. Cut over with a way backThe old setup stays available until the new one is proven. If something is wrong, we go back and try again another day.
  5. Keep it runningPatching, monitoring, backups and the occasional "we moved this before it became a problem" email.

Left alone, this is how it goes

What we get called about

None of these are hypothetical. They are the calls that come in, and every one of them is cheaper to prevent than to fix.

  • A certificate expires and every visitor gets a browser warning.
  • PHP goes end-of-life, so security fixes stop arriving and the plugins start breaking.
  • The disk fills up at two in the morning and the site simply stops.
  • An update takes the site down, and the only backup is on the same machine.
  • You are on shared hosting, and someone else's bad week becomes yours.

Questions we get asked

Do we have to move hosting to work with you?

No. We can look after what you already have, as long as we can get proper access to it. If we think the current setup is the problem, we'll tell you why, and what moving would actually involve.

Who owns the server?

You do. The accounts are in your name wherever that is possible, and if you ever leave, the credentials and the data go with you. We won't hold your infrastructure hostage.

Do you work with WordPress?

Every day. Most of what we look after is WordPress, along with Laravel applications and static sites. We handle the hosting, updates, backups and security around it.

Can you take over from our current IT person?

Yes, and it is a normal thing to ask for. We start by writing down what exists, because inherited setups usually come with gaps nobody has documented.

Got a technical mess?

Excellent. We like those.

Tell us what's going on. You'll hear back from a real person at Purple Imp.