Is 'It's on a Server Somewhere' Good Enough for Your Critical System?

The moment a system starts taking bookings and holding customer data, where it runs and who looks after it stop being technical details. They become part of your risk register, whether you keep one or not.

"Where does your booking system live?" is a question that gets some surprisingly vague answers. On a server. In the cloud. With a company our old developer chose. Somewhere.

For a brochure site, vague is survivable. But the moment a system takes bookings, holds customer data or runs your daily operation, "somewhere" becomes a risk with your name on it. When that system goes down at 9am, "the hosting company is looking into it" is not a plan. So let's talk about what hosting a critical system actually involves, because it's a lot more than server space.

What makes a system critical (it's not the technology)

Simple test: if it stopped for a day, what would it cost you? Bookings missed, staff idle, customers ringing, reputation dented. If the answer makes you wince, the system is critical, whatever it's built on. That's the standard we hold ourselves to with bespoke business systems like the ones behind Jones International's operation.

Hosting is a chain, and chains have weakest links

Server, application, database, domain, certificates, email delivery, third-party services: your system depends on all of them, and a failure anywhere in the chain looks identical to your customer. Proper hosting means someone owns the whole chain, including the unglamorous links like the domain renewal and the certificate that expires on a Sunday.

Monitoring that watches what customers do

"The server is up" and "customers can complete a booking" are different facts. Real monitoring exercises the actual journeys, and tells someone before the phone rings. If your current arrangement waits for a human to notice a problem, your customers are the monitoring.

Backups are a recovery plan, or they're a folder

The question is never "do backups exist?" It's: how quickly can the system be restored, to what point in time, and when did anyone last prove it? An untested backup is a hope. A tested one is a plan. The same continuous discipline applies to security: patches, updates and dependency fixes arrive weekly, and skipping them quietly is how systems age into liabilities.

Support that understands your application

Generic hosting support can reboot a server. They can't tell you why bookings stopped confirming, because they've never seen your system before. Application-aware support, the kind that knows your workflows, your integrations and your data, is the difference between a ten-minute fix and a three-day email chain. It also makes deployments calmer: changes rehearsed, timed around your operation, with a way back if something misbehaves.

Choose by business impact, not by price per month

Cheap hosting isn't cheap when you price in the bad day. Match the arrangement to what the system means to your business: capacity for your busiest morning, documentation so no single person is a point of failure, and clear ownership of every link in the chain. That's what our hosting and support service exists to provide for the systems and software we build: not server space, but accountability.

If you're not sure what your critical system is sitting on, that's worth finding out this week, not during the outage.

Get in Touch

Is 'It's on a Server Somewhere' Good Enough for Your Critical System?
Pedwar Web Design Most Trusted Award 2025

Most Trusted Web Design Company 2025

We're proud to have been recognised as Wales' Most Trusted Web Design & Development Company for 2025. This award reflects our commitment to delivering exceptional digital solutions and outstanding client service that sets the standard for excellence.