LEEDS / HOSTINGNORTHERN ROOTS. CONNECTED AMBITIONS.

THE INFRASTRUCTURE / FIND THE RIGHT LAYER

A home for
every workload.

Choose the responsibility you want to keep.

Web space, domains and email

For a website, start with the application, content system, storage, traffic pattern and email needs. Confirm domain registration details, DNS authority, certificate renewal, backup coverage and how you can export the site. A domain, an email account and a website are separate services even when purchased together.

Ask who maintains the application and plugins. Hosting management does not automatically include your website code or mailbox migration.

Virtual machines and private environments

Define compute, memory, storage performance and network requirements around a representative workload. Confirm the guest operating system, licences, privileged access, patching and monitoring owner. Establish whether backups cover entire images, application data or both—and test the recovery sequence.

A virtual machine offers control with operational responsibility. A private-cloud proposal should state its isolation model, management boundary and capacity rather than relying on the label alone.

Dedicated hardware and colocation

For your own equipment, specify rack units, dimensions, weight, power draw, power feeds, ports and remote-access needs. Confirm the actual facility, operator, access process, delivery arrangements, remote-hands scope and support contacts. Resilience depends on the complete service design, not a rack in isolation.

Compare the service models

ModelUseful starting pointConfirm responsibility
Web hostingPublishing a website and related servicesApplication updates, email, backups and renewals
Virtual machineA controlled operating-system environmentGuest security, licences, resource limits and restore
Dedicated serverA workload with hardware-specific requirementsHardware ownership, replacement, management and access
ColocationHousing your own physical equipmentRack space, power, connectivity and on-site work

Connectivity and recovery belong in the proposal

Agree bandwidth, addressing, routing, cross-connects and the recovery path. Describe recovery objectives in terms of the application and business process. Confirm backup retention, restore access and testing. Exact availability, facility location, prices and support arrangements require a project-specific proposal.

Discuss your infrastructure ↗