Our Managed Static WordPress offering is still in pilot mode.
Managed Static
Every fleet has sites that changed for the last time years ago. The restaurant menu, the brochure site, the campaign page that never ended. They generate no revenue pressure, no content velocity, and no upgrade budget, but every one of them still runs a full PHP stack that must be patched, updated, and defended forever.
Managed Static ends that. Low-change sites are frozen into fast static builds served from a CDN, while WordPress quietly remains the CMS behind them. Nothing to patch, nothing to exploit, nothing to slow down.
Freeze the Site, Keep the CMS
WordPress as the CMS
The WordPress install doesn’t go away; it becomes the editing environment. Content changes happen in WordPress the way they always did, then republish to a fresh static build. Owners keep the tool they know. Your platform keeps the workflow it already supports.
Chat-Based Editing
For the smallest changes, skip the dashboard entirely. Update hours, swap a phone number, fix a typo through conversation, and the static build republishes with the change. The lightest sites get the lightest workflow.
Publish Fast, With SSL
Every build publishes as pre-built files served at wire speed, through your existing web serving and SSL, with CDN delivery wherever you run one, or on our edge for partners without infrastructure. Pages load near-instantly because nothing executes on request.
Zero PHP, Zero Attack Surface
Nothing to Patch
A static site executes no PHP on request. No runtime to hit end of life, no plugin vulnerabilities to exploit, no update cycle to manage. The site simply cannot be compromised through the paths that account for nearly all WordPress incidents.
Off the Legacy Ledger
Every site converted to static is one fewer site on an aging PHP version, one fewer entry in the risk report, and one fewer blocker when your infrastructure team retires an old runtime. Freezing is fleet hygiene that pays for itself.
Faster Than Any Fix
No stack optimization matches the speed of not running a stack. Static builds routinely turn the slowest legacy sites into the fastest pages on your platform, with perfect scores their owners never saw before.
Built for Fleet Operations
Subdirectory Mounting
Static builds can mount into existing site structures, so a frozen section lives alongside dynamic pages where needed. Freeze what’s finished, keep what still moves.
Converted in Batches
Like everything in WP Maintain, conversion runs at fleet scale: identify candidates, convert in controlled groups, verify, and publish. Suitable sites surface automatically from the same monitoring that powers the PHP Lifecycle.
Reversible by Design
The WordPress source remains intact. If a frozen site ever needs to be dynamic again, unfreeze it and it’s WordPress serving live pages the same day.
How WP Maintain Powers It
1. Candidates Surface Automatically
The same fleet monitoring behind the PHP Lifecycle identifies freeze candidates: sites on aging runtimes with low content velocity, no dynamic functionality in active use, and no upgrade path worth funding. Your team reviews a ready-made list instead of hunting for one.
2. The Platform Builds the Static Version
The WP Maintain connector renders the entire site to a static build: every page captured as plain HTML, CSS, and JavaScript, internal links rewritten, forms and search replaced with static-compatible equivalents. Each build is versioned and verified against the original before anything ships.
3. The WordPress Origin Comes Off the Front Line
After conversion, the WordPress install stops serving public traffic. It’s removed from public routing and parked behind authentication as the editing origin, on the same infrastructure or fully isolated from the production stack, whichever fits the host’s architecture. The PHP stack that attackers probe all day is simply no longer reachable from the internet, which is where the zero-attack-surface promise comes from. The parked origin itself runs on a current, supported PHP version wherever the site’s code allows; where legacy code still requires the old runtime, that runtime exists only inside the authenticated editing environment, dormant between editing sessions and never in the path of public traffic. The domain, email, DNS, and everything else the account always covered stays exactly where it is.
4. The Build Publishes Through Your Existing Stack
The static build deploys to the host’s own web serving with the SSL automation already in place; no new infrastructure required, because serving files is what hosts already do. Partners running a CDN layer get edge delivery through their existing setup automatically. Publishing destinations connect through the same open-integration model as the rest of the platform: your own serving stack, Cloudflare, Bunny, or any S3-compatible storage. For partners without server infrastructure, builds can publish to the WP Maintain edge instead, always under your brand and billing.”
WP Maintain is a partner platform: we serve web hosts and technical agencies, never site owners directly, so every frozen site remains your customer, your revenue, and your relationship. Same pipeline, your choice of destination.
5. Edits Flow Through, Automatically
When content changes, in the parked WordPress or through chat-based editing, the platform applies the change to the origin, rebuilds, verifies, and republishes. The owner experiences normal editing. The public only ever sees fast static pages.
6. Still a First-Class Fleet Citizen
Frozen sites stay inside the platform: uptime monitoring on the static endpoints, domain and SSL monitoring, activity logs on every rebuild, and continued presence in Proof-of-Care reports. The customer keeps seeing maintained value; your team keeps seeing one dashboard.
What the Customer Pays For
Freezing a site doesn’t end the customer relationship. It upgrades it.
Hosting Continues
The hosting plan stays exactly where it is. The domain, email, DNS, and everything else the account always covered stays exactly where it is, while the parked WordPress origin moves to an isolated editing environment, off the production stack entirely. Nothing cancels, nothing migrates away.
WP Care Becomes Managed Static Care
The care line item converts. Instead of paying for update management on a site that no longer changes, the customer pays for Managed Static: the editing origin kept safe and ready, chat-based edits and republishing, CDN delivery with SSL, uptime and domain monitoring, and a Proof-of-Care report showing it all. Same peace-of-mind promise, delivered in the form this site actually needs.
Better Economics on Both Sides
For the customer, it’s a faster, safer site than they’ve had in years, usually for a modest step up from base care. For the host, it’s higher recurring revenue per site than foundational WP Care, with a fraction of the delivery cost: no update pipeline consuming platform resources, no PHP runtime to defend, and support tickets from that site effectively ending. The care charge goes up while the cost to serve goes down, on a site that was previously pure liability.
The Renewal Conversation Writes Itself
“Your site hasn’t changed in three years and it’s running software that no longer receives security fixes. For a few dollars more than your current care plan, we’ll make it faster than it’s ever been, impossible to hack through its old stack, and still editable whenever you need. Nothing about how you use it changes.” That’s not an upsell script; it’s the honest state of the site, and it’s why freeze conversions convert.
The Freeze Lane of the Legacy PHP Fleet Program
Every legacy PHP site in a fleet fits one of four lanes: protect it while it waits, upgrade it to a modern runtime, freeze it into static permanence, or rebuild it on a modern stack. Managed Static is the freeze lane, built for the sites where the honest answer to “when will this be upgraded” is never.
For hosts, that lane is also a business: a per-site monthly service your customers pay for, delivering a faster and safer site than the one they had, at a fraction of the cost of keeping legacy PHP defended forever. The site’s story is finished. Now its maintenance is too.