Maintenance
Managed WordPress Hosting Isn’t a Price Tier
Managed hosting is a promise about accountability
The brochure language is nearly identical across every tier: automated backups, SSL included, 24/7 support. What the brochure doesn't say is what "24/7 support" means when it's a ticketing queue staffed offshore, or what "managed" means when the answer to a plugin conflict is a link to a knowledge base article. For institutions — PBS affiliates running pledge drives, university enrollment portals that spike the last week of January, health systems fielding patient inquiries — the difference between a host that answers and a host that eventually responds is not a preference. It's a liability question.
Managed WordPress hosting, properly understood, is not a price tier. It is a named party who is on the hook when something breaks. That distinction collapses under marketing pressure until the outage happens — and then it is suddenly the only thing that matters.
Managed WordPress hosting is not a price tier. It is a named party who is on the hook when something breaks.
Most plans sell infrastructure, not the promise
A managed plan from a large hosting company typically means the server is configured for WordPress: caching layer in place, PHP version current, staging environment available. That is infrastructure management, and it is genuinely useful. What it is not is operational accountability — someone who knows your site, watches your traffic patterns, and calls you before the enrollment deadline instead of after. The staff who answered your sales call do not answer the phone at 11 p.m. on a Tuesday when the donation form stops submitting.
The tell is in the support structure. A host with real accountability has named humans attached to named accounts. A host selling a managed tier has a ticket system with SLA targets measured in hours. For a site that drives tens of thousands of dollars in a four-hour pledge window, hours is the wrong unit. Lantern, our ongoing-care plan, is built around the opposite assumption: someone is already watching before you know there is anything to watch for.
Before you sign, ask who calls you
The buyer's test is simple enough to run in a sales call. Ask: if my site goes down at 9 p.m. on a Sunday during our annual fundraiser, who contacts me, and how fast? A host with real accountability answers that question with a name and a number. A host selling infrastructure answers it with a link to the SLA terms. Neither answer is dishonest — but only one of them describes what institutions actually need from a hosting relationship.
Ask also who is responsible for the WordPress layer specifically: plugin conflicts, theme compatibility after a core update, a caching plugin that began serving stale pages after a content change. "We manage the server" and "we manage the site" are different sentences. The gap between them is where most institutional outages live. If the answer involves opening a ticket, the relationship is self-service with a premium label on it. Talk to us if you want to understand what accountability looks like before you need it.
The right managed host for an institution is the one whose name you already know when the phone rings — not the one you look up in a crisis. Infrastructure is a commodity. Accountability is what you are actually buying. Most plans sell the first and describe it as the second. The question worth asking before you sign is not which tier covers your traffic volume. It is which human is on the hook if the site fails during the one hour a year it cannot afford to.