Hosting keeps the website available

Hosting is the environment that stores and serves the website or application. It may include computing resources, storage, networking, certificates, deployment tools and backups of the hosting platform. The provider keeps its platform operating, but that does not automatically make every website placed on it correct, secure, current or useful.

Website Care keeps the website healthy

Website Care is an ongoing service around the website itself. Depending on the agreement, it can include code and dependency updates, content changes, accessibility checks, fault investigation, performance work, monitoring and small improvements. A website can be hosted without active care, or cared for while hosted by another provider.

Map the responsibilities clearly

  • Identify who owns and renews the domain name.
  • Record who manages DNS, hosting, certificates and deployment access.
  • Define who updates the website code, dependencies and content.
  • Confirm what is backed up, how long copies are kept and who can restore them.
  • Agree who receives availability, security and form-delivery alerts.
  • State which content changes and development tasks are included or separately quoted.
  • Document third-party services such as email delivery, analytics, booking or payments.
  • Keep an exit plan covering the domain, code, content, data, accounts and a final backup.

A provider name or monthly price alone does not answer these questions. The service description should explain boundaries and response expectations in plain English.

Compare offers on outcomes

Cheap hosting may be suitable for a simple low-risk site, while an application handling customer data may need stronger operational controls. A care plan might include monitoring but not round-the-clock response; it might include updates but not redesign work. Compare what happens when something fails, who acts, how quickly they acknowledge it and what recovery has been tested.

What not to do

Do not assume hosting includes unlimited content changes or that a care plan includes the hosting bill. Do not cancel the old service before the domain, DNS, files, databases, email dependencies and rollback route are understood. Avoid shared logins and make sure the business retains appropriate ownership or access.

When to stop and ask for help

Ask for a responsibility map if renewal, backup, security updates, monitoring or recovery ownership is unclear. Get advice before moving a live site with email, customer accounts, payments or integrations. A rushed move can interrupt services that are not visibly part of the website.

Prepare for support

List the domain registrar, DNS provider, hosting provider, website platform, repository or source-code owner, important forms and integrations, current care arrangement and renewal dates. Do not send passwords. Provide authorised access through each service's proper invitation or role mechanism when work begins.