Managed WordPress Hosting for People Who Don't Want to Manage WordPress

Every host sells "managed WordPress." Here is the list of things we actually do for a site on these plans, so you can hold us to it.

• Core, plugin and theme updateson a fixed schedule (monthly on WP Launch, weekly on WP Grow and WP Scale) applied to staging first, checked, then pushed live.
• LiteSpeed Cache configuredfor your site at setup: page cache, object cache where available, image optimisation and browser cache rules. You don't touch cache settings.
• WordPress hardeningdisabled file editing, login protection, XML-RPC restrictions, correct file permissions, security headers, and Imunify360 scanning at the server level.
• Daily backups stored off-serveron an off-server storage box, with 14, 30 or 60 days of retention. One-click restore on WP Grow and Scale.
• Uptime monitoringon every tier, with alerts to you on WP Scale.
• A staging site on every planincluding WP Launch, so nothing is tested live.
• Plugin and theme conflict fixes included.When an update breaks the layout or the checkout, that's our ticket, not a billable one.
• Malware cleanup included.If something gets through, we clean it, find how it got in, and close it.

What's not included: bugs in code your developer wrote (USD 10/hour) and site redesigns (a separate project).

We've cleaned up a lot of WordPress sites for agency clients. The failures are boringly consistent:

An update broke something. A plugin update conflicts with the theme, the site shows a white screen or the checkout stops working. On these plans updates go to staging first; if staging breaks, live never does. If something still slips through, fixing the conflict is included.

Nobody updated anything. The opposite problem, a site running a two-year-old plugin with a known exploit. Scheduled updates close that window.

Malware got in through a plugin or weak login. Imunify360 blocks most attempts at the server; WordPress hardening and login protection close the common doors. If a site is compromised anyway, we clean it and tell you how it happened.

The host's "backup" was on the same server. When the server died, so did the backup. Ours are on a different provider in a different country.

It was slow, and nobody knew why. Usually unoptimised images, a bloated theme and no real caching. LiteSpeed Cache configured by someone who has done it a few hundred times fixes most of it; our Dapto Dentist client saw 40–60% faster page loads from this kind of work.