Your Web Host Is Not Your Web Team

Hosting and website management solve different problems

A managed WordPress host supplies the infrastructure that makes a website available. It runs the servers, maintains the hosting platform, provides backups, watches its network, and helps recover from infrastructure failures.

A web team operates the website that runs on that infrastructure. It updates WordPress and its extensions, publishes content, investigates application errors, checks forms and integrations, manages releases, and coordinates with the host when the source of a problem is not yet clear.

Both jobs matter. Confusing them usually becomes expensive during an incident, when the host reports that the server is healthy while the organization is still looking at a broken form or an unusable page.

What an approved WordPress host should provide

We do not approve a host based only on its company name. Plans, account permissions, and support levels differ. We review the specific setup the website will use.

• SSH and WP-CLI access for controlled maintenance and diagnosis.
• A staging environment where consequential changes can be checked before release.
• Individual delegated accounts, protected by multifactor authentication, instead of shared credentials.
• Automated backups with a restore process that can be used under pressure.
• Continuous infrastructure monitoring and documented crash recovery.
• Technical support available at all hours for infrastructure incidents.
• A current PHP runtime, full-page caching, CDN support, and enough resources for expected traffic.
• An established operating history and a generally strong professional reputation.

Fast is a property of the whole setup

There is no useful speed label that applies to every site on a hosting plan. A small brochure site and a membership platform can use the same host and behave very differently.

For approval, fast means the plan removes obvious infrastructure bottlenecks. It uses a current runtime, supports effective caching and content delivery, has capacity for the site's real traffic, and performs without host-level constraints in staging and production measurements.

That does not guarantee a fast website. Oversized images, unnecessary scripts, inefficient themes, database queries, and third-party integrations can still make a well-hosted site slow. Those are application problems for the web team to find and correct.

Keep the account in your organization's name

The organization should own the hosting account and pay the host directly. Staff and vendors should receive individual delegated access appropriate to their work.

This makes responsibility visible, supports prompt access removal, and prevents a future vendor transition from turning into a dispute over credentials or infrastructure. It also keeps the commercial relationship with the host where it belongs: with the organization whose website depends on it.

The question to ask before signing

Do not ask only who hosts the website. Ask who operates it after launch.

A complete answer names the host, the account owner, the people with access, the web team, the monitoring process, the backup and restore process, the publishing workflow, and the person responsible for coordinating an incident. If any of those answers is missing, the organization has purchased infrastructure without assigning operations.