Hosting and website maintenance are connected, but they are not interchangeable. Hosting provides the environment that makes the website available. Maintenance looks after the application, content, integrations and ongoing changes running in that environment.

“Managed” hosting adds provider assistance, but the exact boundary varies. The word does not automatically mean somebody is responsible for every plugin, form, checkout, content change or custom integration.

What hosting normally covers

Depending on the provider and plan, hosting can include:

  • server or platform availability;
  • computing, storage and network resources;
  • certificates and basic platform configuration;
  • infrastructure backups;
  • operating-system or managed-runtime work;
  • platform monitoring and incident response.

The contract determines the real coverage. A self-managed server and a fully managed application platform are very different products.

What website maintenance normally covers

Website maintenance can include:

  • CMS, plugin, module, theme or framework updates;
  • compatibility review and post-update checks;
  • website-level backups and recovery readiness;
  • form, checkout, login and integration testing;
  • bug fixes and content changes;
  • performance and SEO hygiene;
  • lifecycle planning and improvement recommendations.

These responsibilities sit closer to the application and the customer experience.

Where the gap appears

Imagine that the server is online, but a plugin update breaks the enquiry form. The host may correctly say the infrastructure is healthy. The website is being served exactly as configured. Yet the business has stopped receiving leads.

Or the CMS may be healthy while the headless frontend fails to deploy. The CMS vendor, frontend host and development team each see a different layer. Without one person owning the complete journey, the issue can bounce between providers.

Compare responsibilities, not labels

Ask the host:

  1. Which software layers do you update?
  2. Are application backups included, and who tests restoration?
  3. Do you test forms, checkout and logins after changes?
  4. Do you investigate custom code and third-party integrations?
  5. What happens when the infrastructure is healthy but the website journey is broken?
  6. Who coordinates an incident across multiple providers?

Then ask the website maintenance team:

  1. Which hosting and infrastructure responsibilities are excluded?
  2. Who receives platform alerts?
  3. Can they work with the existing host?
  4. How are access and escalation handled?

Three workable arrangements

Separate host and maintenance partner

This works well when the responsibility boundary and escalation contacts are documented. The maintenance team handles the application; the host handles the infrastructure.

One provider coordinating both

This can reduce handoffs, provided the quotation states which services are actually provided and which remain with third parties.

Managed platform plus internal web team

An internal team can own the application and use a managed platform for infrastructure. The organisation still needs capacity for updates, testing, content and development.

The question that matters

Do not ask only, “Is our hosting managed?” Ask, “Who is accountable when a customer cannot complete the important journey?” The answer should name a person or team, the first checks they perform and how the issue moves across provider boundaries.

Sources