Managed WordPress Hosting Demystified…

Patrick Gallagher, co-founder and CEO of GridPane, will be breaking down the myths, the gotchas, and the hidden strings behind the multi-billion dollar “managed” WordPress hosting space and showing YOU how you can take complete control of this aspect of your business, all while saving time, driving better performance, and realizing much higher margins. Patrick will also cover building your very own self-managed LMS hosting setup for fun and profit.


Managed WordPress Hosting For LMS Sites Explained

Patrick Gallagher, co-founder and CEO of GridPane, joins Chris Badgett to demystify managed WordPress hosting for course and membership sites. They cover what separates true managed hosting from marketing, why direct access to your own server infrastructure matters for LMS performance, how to size a server for real concurrent users, and practical guidance on caching, backups, video hosting, and migrating an existing site without downtime.

What You’ll Learn

  • What “managed WordPress hosting” actually includes, and how to tell a truly managed host from one that just uses the word as marketing
  • Why LMS and WooCommerce sites need more server resources per site than a typical brochure website
  • The real difference between concurrent users and total traffic, and why a quiz can crash a server that traffic alone never touches
  • How to avoid the most common caching mistakes that break dynamic course content
  • What to check before migrating an existing site to a new host

Key Takeaways

  • Ask any host directly what CPU, RAM, and PHP worker limits your plan includes. A vague answer is itself a signal.
  • Budget at least one dedicated server per serious LMS or WooCommerce site rather than sharing a box with unrelated projects.
  • Keep an independent, third-party backup of your site in addition to whatever your host automates.
  • Run one caching layer at a time, and turn all caching off while you are actively building or editing content.
  • Use a third-party status page and uptime monitor hosted off your own server, so an outage does not take your monitoring down with it too.

Frequently Asked Questions

Can I run WordPress hosting like GridPane on a Windows server?

No. GridPane and the major managed WordPress hosts all provision Linux servers, usually Ubuntu, running Nginx as the web server. WordPress technically runs on Windows, but none of the mainstream managed hosting stacks support it, so running an LMS site on Windows is not recommended.

If I move to a self-managed host, do I lose control over my own server?

No, the opposite. With a self-managed platform like GridPane you own the underlying server at the infrastructure provider, so you can install other software on it if you choose. The tradeoff is that anything outside the supported WordPress stack, such as a Drupal install on the same box, will not work with the platform’s staging and backup automation.

How do I monitor uptime and server resources for my LMS site?

Use a third-party status page and uptime service, such as Uptime Robot, hosted independently of your LMS server. If your status page lived on the same box as your site, an outage would take the status page down with it. Independent status pages also tie into your infrastructure provider’s own status feed, so you can tell a real outage apart from a provider-side incident.

Should I host my own course videos instead of using Vimeo or Wistia?

Generally, no. Self-hosted video adds bandwidth and latency problems, especially for students outside your server’s region, and none of the open-source video platforms are mainstream-ready yet. Services like Vimeo Pro, Wistia, or Cloudflare Stream handle global delivery and device encoding for a relatively small monthly cost.

Can an existing site be migrated to a new host without a lot of downtime?

Yes, if the current host gives you SSH and WP-CLI access, a host like GridPane can automate most of the migration. If the source is a locked-down managed host, sites usually have to move one at a time using a migration plugin. A site that is actively crashing needs a maintenance window first so there is a stable copy to move.

What is the alternative to WordPress multisite for franchises or multiple languages?

Subdomain-based multisite is the more workable version for franchise or multi-language setups, but it comes with one shared database across every sub-site. The cleaner long-term alternative is multi-tenancy, where each site keeps its own separate database but shares a single, centrally updated set of core files, themes, and plugins. Turnkey multi-tenancy tooling for WordPress does not widely exist yet.

How do I fix caching conflicts on a dynamic LMS site?

Run one caching layer, not several. A common support issue is a site running server-side caching, a caching plugin, a page builder’s own caching, and Cloudflare caching all at once, which makes problems nearly impossible to diagnose. For a dynamic LMS, Redis-based page caching is the right layer; add a CDN layer like Cloudflare on top only if needed, and turn all caching off while actively editing content.

What should I do if my site keeps crashing under concurrent user load?

First get the site stable enough to migrate, usually by putting it in maintenance mode. Move it to a server sized for real concurrency, not just traffic, since a quiz taken by 60 to 100 people in the same few minutes is a much heavier load than 500 people browsing over a day. If a properly sized server still struggles, the underlying code likely needs a professional performance review.

Full Webinar Transcript

What Web Hosting Actually Means

Chris Badgett: Welcome to this training on demystifying WordPress hosting, specifically for LMS and learning management websites, online courses, training-based membership sites, and internal training portals. These types of sites built with WordPress have specific needs, so I wanted to bring in a real web hosting expert who can also explain this in a way a non-developer can actually understand. That is one of my frustrations with the hosting industry. People start talking about PHP workers and CPU usage, and it feels like talking to a lawyer or an accountant: you know you need the thing, but you do not really understand what you are getting. Patrick is over at GridPane, which describes itself as the world’s first hosting control panel built exclusively for serious WordPress professionals.

Patrick Gallagher: Thanks for having me. I will try to keep this from getting too technical. Before we get into what is essential for learning management system hosting specifically, it is worth looking at managed WordPress more broadly, since most of you are probably operating in that space. All web hosting, whether it is ninety-nine cents a month shared hosting or twenty thousand dollars a month at the top end, really comes down to three things: hardware, software, and support for when things break, because they always do. The hardware is dedicated servers, physical racks of computers running specialized software that keeps the box running efficiently. Then there is support for how all of that works together.

The Five Pillars Of Managed WordPress Hosting

Patrick Gallagher: There are five things I call the pillars of managed WordPress that pretty much every major host has. Backups: once a day, three times a day, every hour, whatever the cadence, they back your site up and make it available to you. Updates: not just the server hardware, but your WordPress core, themes, and plugins, kept current. Security: the site and server are hardened, and if you get hacked, most hosts include some remediation. Speed or performance, which is really caching, the software trickery that delivers your site faster. And staging: a practice environment where you can change themes and plugins without risking your live site. These are table stakes. If a host is bragging about having these, understand that everybody in the managed space has them.

How To Tell If Your Host Is Truly Managed

Patrick Gallagher: Unfortunately, sometimes “managed WordPress” is just marketing. There is a whole category of what I would call fake managed, or pseudo-managed, hosting, where you are not actually getting the high degree of support and professional engineering behind the real thing. In my view, true managed WordPress means the host is independently monitoring that your site is up at all times, and if your site goes down, you should not have to be the one to tell them. One honest way to find out which category you are in: intentionally break your site and see what happens. If nothing happens, you are at a host that is not actively managing anything.

There is nothing wrong with self-managed hosting, or with things being fully automated by software. That is exactly what GridPane is. We automated the pillars, staging, backups, performance, upgrades, primarily through software. The leap from that to truly managed hosting comes down to the quality of the support and the engineers behind it.

Why GridPane Lets You Connect Your Own Cloud Infrastructure

Patrick Gallagher: A lot of the biggest managed hosts benefit from you not knowing exactly what hardware allocation you are actually getting, because if you knew, you might ask whether you are getting good value for money. WP Engine, the biggest player in managed WordPress, recently announced a shift to Google’s newer, faster server instances. That is the hardware layer, and it is something anyone can connect to directly. You can sign up with Google Cloud yourself and get a meaningful amount of free credit every year, and using software like ours, or like RunCloud or ServerPilot, you can connect straight to that infrastructure without paying an markup to access it.

Chris Badgett: What’s the actual difference between regular hosting and managed WordPress as a category?

Patrick Gallagher: Sometimes nothing. There is only a small handful of true managed hosts, and a whole bunch of people who are pseudo-managed. We do not do that abstraction. Our software connects natively to DigitalOcean, Vultr, Linode, AWS Lightsail, and other major infrastructure providers. You create an account with one of those companies and drop your API key into GridPane, and we communicate with your account on your behalf.

How To Build A Server On Your Own DigitalOcean Account

Patrick Gallagher: Here is what that looks like. With your API key attached, you name the server, choose whatever price point you want since this is the real hard price the provider charges with no markup on top, and select the region. If you are building a course site aimed at learners in London, for example, you would pick that region. Click create, and now our software is talking to DigitalOcean, provisioning that server on your behalf. You never have to touch the underlying infrastructure again. A build like that takes about fifteen minutes.

Chris Badgett: So someone who isn’t a developer, who might normally be intimidated by a provider like DigitalOcean, could actually use it through GridPane?

Patrick Gallagher: Exactly. You sign up with your credit card, get your API key from your profile, drop it into GridPane, and you never have to log back into DigitalOcean’s own dashboard again.

Why Patrick Gallagher Built GridPane

Patrick Gallagher: This platform exists because I ended up canceling an account, for the second time, with a large managed hosting provider after getting frustrated that their support could not solve problems I was running into. I decided I had to solve it myself, so I set out to build an internal toolset for my own agency. The more we invested in it, the more it became clear this was the more interesting business.

There were really four things I hated that led to building GridPane. The first was minutia, all the boring maintenance tasks that make building sites less fun. The second was reliability, and we have built high-availability features so that even if an entire data center goes down, your site does not go down with it, an area of hosting that has not seen a lot of investment. The third was time, my most valuable asset, and we have tried to streamline the platform so that if you find a task taking more than three clicks, you have found a bug. The fourth was autonomy: knowing exactly what hosting would cost, and being able to spin up a server in a region I might never personally visit. We had an agency with a cluster of clients in Australia, and latency was a real problem. If your server is on the East Coast and your customers are on the West Coast, or on the other side of the world, the speed of light is fast, but three thousand miles is still three thousand miles, and there are a lot of network hops in between. Build a server close to your customers.

Building An LMS Site With A Bundle Of Plugins And Themes

Patrick Gallagher: GridPane has a bundles feature, which other platforms call a blueprint or a canvas. It lets you define a set collection of themes and plugins ahead of time, so a new site is built exactly the way you want it right out of the gate. You type the domain, choose the server, optionally choose a system user to isolate the account, and pick your bundle. Click build, and the dashboard talks to that server, installing WordPress along with every plugin and theme in the bundle, so the site is live and ready the moment you log in.

You could have a bundle for a real estate business, a different bundle for a yoga-focused LMS, and another for continuing medical education, each with its own theme and plugin set. Inside a bundle, you add a theme or plugin either by linking to it, such as a Dropbox link for a premium item, or by its WordPress.org slug if it is in the public catalog.

Cloning A Site Instead Of Rebuilding It From Scratch

Patrick Gallagher: One question we get a lot is what to do if you want actual content and data already in place, not just plugins and themes, sample content, authenticated API keys, everything ready to go. In that case you can clone an existing site completely, to another site on the same server or to a different server entirely. A good pattern is to keep a boilerplate site you always have access to, so a new project starts from a real, working baseline instead of an empty install.

Why Direct Hardware Access And High Frequency CPUs Matter For LMS

Patrick Gallagher: Almost every LMS, when it is built right, carries a lot of content, tests, and quizzes, and that is heavier than a standard brochure site. Having your own dedicated hardware, your own VPS, matters because on a provider with a fixed limit on PHP workers, your only real ceiling on a VPS is the physical resources of the box, which you can scale at any time.

High frequency instances, the kind now common across the industry such as Google’s newer server generation, matter a lot for LMS specifically because the underlying processor runs faster. I once worked on a competitor’s LMS, not LifterLMS, that ran recursive checks during quizzes to look for cheating, and it was so transactionally heavy that it kept overwhelming the database. High frequency, dedicated-CPU instances help absorb that kind of load. And backups remain essential in any context, but the more customers and coursework you have riding on a site, the less room there is for a mistake, so beyond whatever your host automates, keep your own third-party backup somewhere independent, so that even in a worst case where your host’s service goes down, you still have your data.

How GridPane Compares To cPanel

Chris Badgett: Someone’s asking if this is an alternative to cPanel.

Patrick Gallagher: Yes. cPanel’s popularity comes from being a jack-of-all-trades control panel: you can build WordPress sites, add email accounts, do SFTP, install all kinds of scripts. GridPane is an alternative in the sense that everything not related to WordPress is stripped away. Email is a good example. Like the major managed WordPress hosts, we recommend a best-of-breed provider for email, such as Google Workspace or Zoho, on a totally separate platform, because you do not want email running on the same server as your WordPress site. It is both a bigger attack surface for hackers and a real performance burden on a machine that should be fully dedicated to serving your site.

cPanel’s appeal to hosts is that it lets them pack a lot of customers densely onto a single server. With our control panel, you are connected to your own dedicated hardware. There is nobody else on that system, so you get to fully use all of the compute resources yourself.

Virtual Private Servers, Shared Hosting, And Dedicated Servers Explained

Chris Badgett: Can you unpack what dedicated, VPS, and shared hosting actually mean?

Patrick Gallagher: Ninety-eight percent of the time, when someone says “I have a server,” they mean a virtual private server. A true dedicated server, which very few people actually have, is a physical box, one full unit in that tall rack of computers, entirely yours. Most infrastructure providers, DigitalOcean, AWS, and similar, use virtualization software to split one physical server into pieces, and you get your own slice. Nobody else can touch your slice, but other customers have their own slices on the same physical box.

Shared hosting goes a step further: you have no dedicated piece at all, just small allotments of a shared pool, which creates the “noisy neighbor” problem, where someone else’s heavy site can slow yours down even though you are not doing anything unusual. Shared hosting is fine for a simple brochure site, but for an LMS you want your own dedicated RAM and processors, which means a VPS at minimum. “Bare metal” is the phrase interchangeable with a true dedicated server: direct access to the physical resource, all yours.

A Quick Detour Into Linux, Ubuntu, And Red Hat

Patrick Gallagher: All of the major infrastructure providers we connect to automatically provision an Ubuntu Linux server, though we also support connecting to any custom infrastructure provider in the world, including region-specific ones like Hetzner in Europe. There are operating system limits, though: we are not compatible with Windows, and I would not recommend hosting on Windows generally. If you look at the biggest hosts, and even at Automattic, the parent company of WordPress.com, they all run Linux with Nginx as the web server, not something you will find as the default on a Windows box.

Linux itself traces back to Unix, and a developer named Linus Torvalds created an open-source version that has since branched into distributions like Red Hat, Slackware, and Ubuntu, each maintained by different groups who took the same underlying code in their own direction. The closest analogy is iOS versus Android: different companies building on similar underlying guts with their own opinionated approach layered on top.

What You Still Own When You Move To A Self-Managed Host

Chris Badgett: What aspects of the server does GridPane control, and can someone still run other software on it without interfering?

Patrick Gallagher: Unlike a platform like Cloudways, which owns the server itself and gives you restricted access to a box they pay for on your behalf, with GridPane your servers at DigitalOcean or wherever else are one hundred percent yours. You can do whatever you want with them, including installing something like Mautic, Joomla, or Drupal alongside your WordPress sites. The catch is that our staging and backup automation is built around the WordPress stack, so anything outside that will not benefit from those tools and could cause problems if it interferes with the box. A static HTML site works fine, since you can just delete the default WordPress files and upload your own, but staging pushes will not know what to do with it. We have never had to remove anyone from the platform for this, but we have asked people to move something onto its own separate, dedicated box.

How Many Sites You Can Safely Run On One Server

Patrick Gallagher: A few rules of thumb. Do not build a box smaller than two gigabytes of RAM, roughly ten dollars a month at any of the major providers. And do not run more than about ten sites per gigabyte of RAM as a starting point, so a ten-dollar, two-gigabyte box could handle upward of twenty simple sites. For LMS and WooCommerce specifically, divide that by four, five, or even ten, since those workloads are much heavier. You do get some economies of scale as you go up in box size, but the resources scale roughly linearly across providers, so it is often smarter to run several smaller, twenty-dollar boxes spread across different purposes than one large eighty-dollar box carrying everything.

For a serious LMS or e-commerce site specifically, I generally recommend one site per box. Think of it as a real business: a twenty-dollar server is a small cost against a site that might be generating thousands of dollars a month in recurring revenue. It is not worth sharing that box with an unrelated project just to avoid paying for a second server.

What Concurrent Users Really Means For A Course Site

Chris Badgett: People constantly ask us, in presales and after they buy, how many concurrent users LifterLMS can handle. Help me answer that.

Patrick Gallagher: The honest answer is it depends, and mostly on concurrency, not traffic. A standard, mostly static site can absorb thousands of concurrent users on a modest box because it is being served from cache. But I worked with one LMS, not LifterLMS, running a bloated code base, that hosted webinars every Friday followed by a quiz. Sixty people taking that quiz at the same moment on a forty-dollar box would bring the whole server to its knees. That is not even a lot of traffic, sixty people over a few minutes, but it is a lot of concurrency. Five hundred people visiting your site over a day usually means, at any given instant, well under one person actually active. True concurrency is a different measurement entirely.

For that customer, we moved them from a roughly sixty-dollar server to a two-hundred-dollar one, and a week later I checked in assuming they had canceled a class, since the box had barely spiked above single-digit CPU usage. They had run the quiz as normal; we had simply overshot the sizing. As a rough range, fifty to one hundred concurrent users doing something transactionally heavy, like a quiz, generally needs a server costing at least one hundred dollars a month, though it depends heavily on how efficiently the site is built.

How To Vertically Scale A Server When Traffic Grows

Patrick Gallagher: All the major infrastructure providers make it easy to scale a server up and hard to scale back down, so start small, test, and watch your utilization. If you are trending above fifty to seventy percent utilization consistently, you can vertically scale, essentially telling your provider to double the size of the box. That takes about five minutes of downtime while the server powers down and back up, and you come out the other side with roughly twice the capacity.

Building A Status Page And Monitoring Server Resources

Chris Badgett: How do people add a status page for their own clients, and how do they monitor server resources generally?

Patrick Gallagher: You can build your own status page using a service like Uptime Robot. A good status page service ties into your infrastructure provider’s own status feed directly, so if your site looks down but your box is actually fine, you can immediately see that the outage is on the provider’s end, in a specific data center, rather than something wrong on your side. Always host your status page independently of your own server. If your main site goes down and your status page is hosted on that same box, the status page goes down with it, the same way you would not want your only way of checking whether Slack is down to be a page that Slack itself hosts.

Inside our own dashboard, every site also has a stats package showing everything running on the box: service status, disk space, backup sizes, RAM and CPU utilization. It is fairly detailed, more than most people need day to day, but the same numbers are also visible directly inside your infrastructure provider’s own dashboard.

Should You Host Your Own Course Videos

Chris Badgett: At LifterLMS we generally recommend Vimeo Pro or Wistia rather than self-hosting video, though some people do want full ownership and put it on something like Amazon S3. What’s your take, especially for course creators for whom video is central?

Patrick Gallagher: I have a bit of a love-hate relationship with this. Before GridPane, part of me wanted to build an alternative to Wistia because it felt too expensive. I have looked at every open-source self-hosted video package out there, and I do not think any of them are ready for mainstream use; the ones that are ready have already become enterprise products. I recommend Vimeo, YouTube for marketing content, and lately Cloudflare Stream, which starts at five dollars a month and delivers video quickly worldwide.

At the end of the day, these are your own boxes, so some people do upload video directly and serve it from their own server. The infrastructure providers we connect to give generous bandwidth allowances, commonly a couple of terabytes of transfer even on a ten-dollar plan, so most people will not come close to hitting that. If someone genuinely needs to self-host a large volume of video, a true dedicated server provider with unmetered bandwidth is worth a look, though support quality varies. The core reason services like Wistia, Vimeo, and Cloudflare Stream exist is that video needs to reach a global audience quickly, encoded correctly for whatever device someone is on, and a single box in one location cannot do that as well as a purpose-built delivery network.

Migrating An Existing Site To A New Host

Chris Badgett: Do you have scripts for migrating sites in, and what’s your general stance on migration?

Patrick Gallagher: Most of our customers come from another host, so this comes up constantly. If you have SSH access and can run WP-CLI on your current host, we can largely automate migrating sites over, even at scale; I once moved eighty-seven sites, over one hundred gigabytes total, for one customer in under an hour. If you are coming from a locked-down managed host, or a different control-panel-based host, we usually have to move sites one at a time using a migration plugin like All-in-One WP Migration or UpdraftPlus. Unfortunately, many managed providers make it deliberately harder to migrate away, so we cannot always automate the outbound side of that. The first migration is typically included and we record ourselves doing it, so you can see exactly how it was done for future moves.

Getting A Free Trial And Talking To Someone Before You Buy

Chris Badgett: For anyone considering a switch, do you offer consultations before purchase?

Patrick Gallagher: Paid accounts start with a free trial period so you can test the platform before committing anything. If you want to talk to a person first, you can message our team and get connected with myself or a senior member of our customer success team before you ever enter a credit card. Once you are in the platform, you can also schedule a thirty-minute onboarding call to walk through questions and figure out whether it is genuinely a good fit. We would rather you test it and decide it is not right than sign up and feel stuck.

Hosting Plans For Agencies And Client Sites

Chris Badgett: What about agencies hosting on behalf of a lot of clients?

Patrick Gallagher: Either of our account tiers can run an LMS, but we usually recommend the higher developer tier for agency-style businesses, since it comes with higher-priority support and access to high-availability features that fit an agency’s needs better. Beyond that, we have ongoing enterprise or white-label conversations for agencies that want their own branding attached to the platform, or that need something like two dozen support seats for a two-dozen-person team. Right now site limits are effectively unlimited, since the underlying infrastructure cost is yours to carry directly.

Who GridPane Is Actually Built For

Patrick Gallagher: Our best-fit customer is either an agency running a lot of sites, or someone running one or two very serious production sites. One of our customers runs a large e-commerce business selling plants directly to consumers on a single WooCommerce site; he came to us because his previous host’s PHP worker pricing kept climbing even though he only ran one site, because he needed the worker capacity that came bundled with a much bigger plan. People coming from hosts like WP Engine, Kinsta, Flywheel, or Liquid Web tend to recognize the value fastest, since they already understand what they are paying for elsewhere. For someone brand new with a single small site, our pricing can look expensive by comparison, until that one site scales enough that the value becomes obvious.

Combining LifterLMS With Zoom For Blended Learning

Chris Badgett: One more from the chat: someone working with gyms is looking at blended learning using Zoom alongside LifterLMS. LifterLMS is not really a replacement for Zoom, and most of our most successful users run both together. We recently published an in-depth article on using LifterLMS with a gym or personal training business, which we will share separately.

Site Templates And Boilerplate Sites On The Roadmap

Chris Badgett: Someone’s asking if, instead of just bundles, you could deploy a full-fledged, pre-configured site as a one-click template on new domains.

Patrick Gallagher: Not yet, but it is coming, and it would not surprise me if it shipped within a couple of months. Right now the workaround is to build a blank site and clone an existing, fully bundled site over to it, which is a few clicks rather than one, but still quick. The eventual goal is a “build from template” option right in the new-site flow, choosing a pre-built, boilerplate site the same way you choose a bundle today.

Inside The Hosting MBA Course

Chris Badgett: What’s the vision behind the “Hosting MBA” you mentioned?

Patrick Gallagher: There are two things in the works. One is a shorter boot camp or challenge focused on getting the fastest wins out of the platform. The other, Hosting MBA itself, is a longer, roughly twelve-week course with a webinar component, straight lessons, and checklists. The goal is not just to help someone use GridPane well, but to build a real, sustainable hosting business on top of it, including how to quote and justify a hosting fee when a client is comparing you to ten-dollar-a-month competitors. Before GridPane, I ran my own agency for thirteen years, and in the last several years I got much better at charging higher fees, not by working harder, but by connecting with the right clients and communicating the value clearly. That is what the course is built to teach.

What GridPane’s API Can Do Today

Chris Badgett: Someone’s asking about API access.

Patrick Gallagher: We have an API today that is not yet publicly documented, though that is coming. We use it internally right now, for example to build a site, and our own front-end talks to it behind the scenes. If you wanted to build something like a WooCommerce interface that provisions hosting resources automatically when someone buys, that kind of integration will be possible. Some more advanced endpoints will likely stay limited to enterprise customers, partly because we have already had to deal with people, once given early access, accidentally flooding the system, building large numbers of sites in minutes. Basic operations, building a site, changing ownership, changing PHP versions, already have endpoints; we just need to finish documenting them and build the right guardrails first.

How GridPane Compares To Webmin

Chris Badgett: Does GridPane offer the same features as Webmin?

Patrick Gallagher: Not directly, because Webmin is not specific to WordPress; you can build almost any kind of site with it. For anything you could do to run a WordPress site on Webmin, we do the same thing and more. As one example, you can change a site’s owner, add auto SSL, change the PHP version, turn on a web application firewall, or switch caching settings, all in a single click. We deliberately keep the interface simple on purpose, even though there are hundreds of underlying commands available if you want to go deep into customizing PHP, Nginx, or MySQL. In the long run we expect to offer both a basic view and a more advanced one, since some of that power could cause real problems if someone does not know what they are doing.

Sending Backups To Your Own Third Party Storage

Chris Badgett: Can backups automatically go to something like Google Drive in addition to a host’s own servers?

Patrick Gallagher: We were re-releasing our remote backup service around the time of this recording. Every site has access to migration plugins you can use entirely independently of the platform for your own third-party backups, which I strongly recommend keeping regardless of what your host automates. Native remote backup support was rolling out to cover Amazon S3, Backblaze B2, Wasabi, and other S3-compatible storage first, with broader support for services like Dropbox and Google Drive following. The eventual goal includes letting a single site push backups to more than one remote destination at once.

Why Multisite Is Not The Right Fit For Every Franchise Or Multilingual Site

Chris Badgett: What would you recommend as an alternative to WordPress multisite for something like thirty-five regional franchises, or a set of subdomains for different languages under one main site?

Patrick Gallagher: Personally I am not a fan of multisite, though it genuinely fits some use cases well, franchise setups and multi-language sites among them. If you go that route, I would strongly recommend subdomain-based multisite over subdirectory-based multisite. The alternative I would actually like to see does not fully exist yet: multi-tenancy, where each site keeps its own separate, sharded database, but shares one centrally managed set of core files, plugins, and themes that update everywhere at once with read-only access from each site. That gets you the efficiency of updating once without collapsing every site’s data into one shared, messy database, which is my main complaint with multisite as it exists today. Turnkey tooling for that does not really exist yet, so for now, multisite remains the fastest path if you need to launch something like this quickly.

Moving A Site To A New Host Without Changing Servers

Chris Badgett: Can you migrate a site that’s managed by a service like SpinupWP, already running on someone’s own DigitalOcean server, into GridPane without changing the underlying server?

Patrick Gallagher: No. Because you own the box either way, we can copy the site over easily, but you cannot run two different management platforms on the same server at once. The real concern is usually the DNS change involved in pointing to a new IP address. One workaround some providers offer is a floating IP, an address tied to a data center rather than a specific server, which you can reassign to a new box without touching DNS, though most providers only let you set that up from the start, not retroactively. In practice, moving from a platform like SpinupWP means building a new server with us, cloning the site over, and decommissioning the old box once everything checks out.

How Staging Environments Work For Sandbox Testing

Chris Badgett: Can you speak to how GridPane handles staging environments and sandbox testing?

Patrick Gallagher: Every site gets a staging site built by default, and you can push changes between staging and live in a few different ways: all files and the full database, or a partial push of just files or just the database. You could also build a site under a subdomain of your own domain and later change what the primary domain is, or build under a temporary domain and clone it to the final one once it is ready. There is no limit on how many staging sites you can run. Right now, staging push functionality is tied to sites we built specifically as a designated staging environment for another site, though a future goal is letting you nest any existing site as the staging environment for another.

Rescuing A Crashing Site With A Hundred Concurrent Users

Chris Badgett: Someone’s on a shared, budget host running LifterLMS and WooCommerce together, seeing around a hundred concurrent users, and the site keeps crashing. Where would you tell them to start?

Patrick Gallagher: Unfortunately, you first need a maintenance window, putting the site into a members-only or maintenance mode so it is stable enough to actually back up and move. If someone genuinely has a hundred concurrent users regularly, that is a real achievement, and I would start with at least a twenty- to forty-dollar box. Clone the site over, test it using a local host-file redirect so you can preview it in a browser before switching anything publicly, then update DNS to point to the new server, take the site out of maintenance mode, and watch how it performs under real traffic.

If it is still struggling on a properly sized box, try vertically scaling once to the next tier. If problems persist beyond that, the underlying code likely needs a professional review; a server that size should generally handle a hundred concurrent users fine unless they are doing something transactionally heavy like a quiz, which points toward an inefficiency in the code itself rather than the hosting.

Getting Caching Right On A Dynamic LMS Site

Chris Badgett: LMS sites are very dynamic, which makes caching complicated. How should people think about caching, caching plugins, and what the host itself is doing?

Patrick Gallagher: We deal with this constantly. I recently spent ten minutes untangling a support ticket where a site had our own Redis caching running, the WP Rocket plugin active, a page builder doing its own caching, Cloudflare caching turned on, and browser caching on top of all of it, five different caching layers stacked together. We build our platform so that you should not need any additional caching plugin, and you do not necessarily need Cloudflare’s own caching layer either.

The short version: pick one caching layer and stick with it. If you like what a plugin like WP Rocket does, use that and turn our built-in caching off, or use ours and skip the plugin, rather than running both. While you are actively editing content or trying new things, turn all caching off, ideally on a staging site, so you are seeing the real, uncached version of the page. For a highly dynamic site like an LMS, Redis-based page caching is the right layer, rather than a purely static caching approach designed for simple brochure sites. You can layer a CDN like Cloudflare on top if you want its network features, but the moment you add more than two caching layers, you lose the ability to tell what you are actually looking at when something breaks.