WaaS networks are a popular revenue channel for more WordPress professionals and agencies. They allow for a relatively hands-off, predictable monthly revenue stream where clients handle most of their own website building using premade templates.
For now, WP-Ultimo is really the only plugin available for a multisite WaaS. We have an integration with Ultimo that will add mapped domains to the domains tab inside your website’s customizer, and you can use our AutoSSL feature to automatically attempt to provision an SSL for these domains as they’re added.
Ultimo is a great plugin for market validation and proving that you have a business that you can grow. To build a truly scalable WordPress SaaS though, multitenancy is the only safe, secure, limitation-free solution.
Multisite vs Multitenancy
WordPress multisite is a single installation of WordPress where network sites exist as subsites within this single installation. It has one shared database, one system user, and all the sites live together sharing the same resources.
Multitenancy is a solution to the problems that come built-in with multisite/WaaS networks. Unlike multisite, multitenancy shares the same WordPress codebase, but each site within the network has its own PHP user and its own database, keeping them independent from one another.
The WordPress codebase that each site runs off is immutable , making multitenancy sites more secure than even regular WordPress sites, and far more secure that regular multisites. Updates to the WordPress codebase are made via GIT and go out instantly across the network.
This approach allows sites to be split across as many servers as needed, spreading “risk” across many baskets instead of everything being on the same server, same database. You can even add sites to their own individual servers, which means multitenancy also works for WooCommerce and other complex websites which can be a disaster when running inside one multisite installation,.
It’s the only way to scale a WaaS network in a safe and secure way.
- Multitenancy runs on an immutable code base that is managed via Git.
- All multitenancy network sites have their own database, system user, and PHP resources, which means they are isolated from one another and can be scaled individually.
- Multitenancy sites can run on their own individual servers.
- Multitenancy sites are far more secure than a traditional multisite installation due to the immutable codebase, separate databases, and server level isolation.
- Multitenancy is ideal for offering e-commerce and other advanced, resource intensive functionality that is a nightmare in a traditional multisite installation.
At vCanopy, multitenancy is available on our Agency plan.
Multisite Network Management Strategy and Scaling Problems
In the early days of your WaaS when running a multisite installation, one of the best things you can do minimise your risks is to cap your network size and use multiple installations.
This way you can have multiple networks running on multiple servers, which in turn keeps your database size more manageable, keeps your networks more mobile (meaning it’s much easier to move a small 2-3GB multisite than it is a 30GB multisite), potentially keeps them more secure, and it means that you’re not putting all your eggs in the same basket. If you have a giant network, if you ever have a situation where ALL of your sites go down at the same time, you’re going to have a hell of a day in support.
There are a couple of ways to do this, and it will affect your sign-up workflow.
OPTION 1. ROTATE YOUR NETWORK OUT ONCE IT REACHES X NUMBER OF SITES
Here you would have a primary marketing site, and then when your customers go to sign up they would click through to your multisite which would be its own separate site. Once you reach X number of sites, simply swap the network out for a new one on a new server.
So for example you may have:
- yourdomain.com (primary marketing site)
- n1.yourdomain.com (multisite network #1, max 30 sites)
- n2. yourdomain.com (multisite network #2, max 30 sites)
And so on. Your primary marketing site links through to the separate network sites which is where they sign up, and you just switch the link out on the marketing site when you switch your network out.
OPTION 2. USE DIFFERENT LOCATIONS
This option is largely the same as option 1 above, except on your marketing site you offer a choice of locations. For example, you may have a network option in LA, New York, and London:
When your customers select their location they click through to the applicable network.
You can then switch these networks out as they reach X number of sites, and have la2, ny2, uk2, etc.
DNS Management, CNAMEs, and Floating IPs
At some point, you’ll need to move your WaaS network from one server to another. This may be because the OS has reached its end of life or your changing infrastructure providers, but whatever reason, it will be necessary.
For some network owners, this may mean having to reach out to every single site owner in their network and asking them to update their DNS records. Ideally, you want to avoid ever having to do this, especially as you grow. Here are two strategies to consider.
1. TAKE ADVANTAGE OF FLOATING IP ADDRESSES
If you’re following the guidance above and using multiple networks, and keeping them relatively small in size, then as long as you stick with the same provider you can take advantage of floating IPs.
When you provision your server, you’ll be assigned a static IP (e.g. 184.108.40.206). You can then assign a floating IP address to this server (e.g. 220.127.116.11). This will make the sites on your server available on both of these IPs, and so you can specifically have your clients set their A and CNAME records to point to the floating IP (in this example, 18.104.22.168).
When the time comes to move servers, simply clone your network across, check and ensure it’s been cloned successfully, and then when ready, switch your floating IP over to the new server. Neither you or your clients will need to update your DNS records.
You can learn more about floating IPs in this article:
Floating IP Addresses and vCanopy
2. HAVE YOUR CLIENTS USE CNAMES
Instead of having your clients set the traditional A record for the root domain and CNAME record for “www”, have your clients instead set both of these up as a CNAMEs and point them to a domain that you control.
You can then use this domain that you control to point to the IP of the appropriate vCanopy server. Then, in the future, if/when you need to move this website to another server, you can update the IP address of the domain that you control, and your client’s websites will then also automatically point to this new server due to the CNAME.
You won’t ever need to touch their DNS directly, but this way you can control what IP all of the websites are pointing to.
TAKE CONTROL OF CLIENT’S DNS WHEREVER POSSIBLE
The most ideal path for you as the network owner would be to have your clients let you take control over DNS with either Cloudflare or DNS Made Easy.
This way you can ensure that either one or both of the above strategies are in place, and once they’re set up, you don’t need to worry about changing these records ever again.
The easiest approach to SMTP is to simply send all transactional emails from the main network domain. This is what will happen out of the box once mail has been setup. It’s not only easier in setup, but it will prevent support issues related to email deliverability where clients haven’t set up their SPF records and validated their domain.
If you need for mail to be sent from each individual subsites domain then this is a little trickier. The official SendGrid plugin used to offer this functionality, however, unfortunately it has not been maintained and we don’t recommend using it for this reason.
A good alternative that can help you accomplish this is the 100% free FluentSMTP plugin. It requires that this be set up for each individual subsite, so you may want to provide training for your network sign-ups on how to do this.
Performance advice here is different for multitenancy and multisite, and this is largely due to all the limitations/drawbacks that come with multisites.
Multitenancy performance is straightforward. There’s very little difference to managing regular domains, so you can give each individual site the resources they need, you can host them on their own servers if you want to, and scale those servers up as these sites grow.
All the standard advice applies – use higher frequency CPUs, fast RAM, fast storage, etc. You can also tune your PHP workers on a per-site basis, as well as all your other PHP settings. Getting high performance out of your sites isn’t as complicated as most people think. Check out this guide for more information:
For your multisite, you should approach it like you would a large dynamic site (like a Woo store or an LMS).
If you keep your networks small (30 sites is a good number in my opinion), they likely won’t require more than a 2 CPU 4GB RAM server. We recommend Vultr High Frequency, but DigitalOceans Premium AMD Droplets and Vultr’s newer High-Performance options are all also good choices.
Higher performance CPUs will help keep your backend admin area snappy and fast and provide a better editing experience for both you and your customers.
- Set your PHP workers to “Static” if you’re using Nginx, and set them to 3-4 workers per vCPU.
- If using OpenLiteSpeed, keep the default “ProcessGroup” settings.
- Make sure Redis Object caching is enabled, and ideally use our server caching instead of a plugin (though in some cases, it can make managing your network easier if using a plugin like WP Rocket and that may be worth a sacrifice in frontend performance).
- Make sure your server has plenty of RAM to accommodate your database.
If your current network is slow, here is a good place to start:
Below are links to all of the articles mentioned in this guide: