We launched the multi-tenant WordPress Marketplace! 🎉

Seperate WP installations
Individual scaling of websites (no shared resources)
One Console to manage all sites
Unlimited scaling potential (SaaS infrastructure)
Continuous, 100% confident WP development

Beyond WordPress multisite

Single WordPress installations that each have a separate database, but shared in functionality.

These companies
have already switched multisite for
multi-tenant WordPress

WPCS Version Control Teaser

A 10x improvement on existing technology

Compared to WordPress multisite, sharing one database over the network, multi-tenant WordPress creates separate WordPress installations for every customer.

Key Differences

multi-tenant WordPress (WPCS)

WordPress Multisite


Seperate WP installations

Shared over the network


Decentralised infrastructure

Central point of failure


A separate development environment

Live to production, introducing development anxiety

User Data (Compliance)

Separated for each customer

User data is shared, making eCommerce impossible


The entire WordPress ecosystem

Limited compatibility

Scalability (Traffic)

Individual scaling

Centrally scaling resources

Scalability (infrastructure)


Natural cap approx. 500

Technical Expertise

No-code solution, just WordPress

Inhouse coding expertise

Everything you need to leverage WordPress for SaaS

Multi-tenant WordPress

Leverage the dominant cloud architecture for SaaS:

Stand alone WP installations with shared functionality, but separate database – making managing thousands of sites possible.

Versioning System

Deploy with 100% confidence.

Version Control lets you easily make changes and keep all of your websites updated from one place. 

See what the community says
about WPCS

Multi-tenant WordPress is getting embraced by the community as the next iteration of WordPress Multisite. Read their words: 

“It’s such a pleasure to see changes made to my version site pass down to my tenants. It’s great that they are standalone WP sites, without the compatibility issues.
We have a window of technical advantage to exploit until the World catches on that multi-tenancy is available.”

Ken Lyle

Owner @ The Tattoo Platform

“After using WPCS for just a few minutes I immediately realized how powerful but yet beautifully simple they’ve made the entire Multi Tenancy process, a process that’s never quite been known as such.

Multi Tenancy has long been known to be the ultimate solution to the limitations of WordPress Multisite, as well as the true enablement of WaaS and SaaS on WordPress.”

dustin Snider

CEO @ DS Development Solutions

“WPCS’ Multi-Tenancy product puts my mind at ease because plugins work the way they should, like on single self-hosted sites, and you can manage your clients from the main site.”

Boun Vilailath

Owner @ Monnete

“WPCS is just a great service. From now on, managing hunderds of WordPress sites is a breeze. With just a few clicks all of them are updated or provided with a new feature/plugin.

No more stress to break things. Simply start a new environment (tenant) to see results before deploying to all production websites.”

Jerome de Groot

E-commerce Manager @ Nedac Sorbo

Managed Cloud Hosting for
SaaS-like WordPress Solutions

The WordPress multi-tenant cloud platform runs on Amazon Web Services (AWS), orchestrated by Kubernetes.

Amazon Web Services

AWS’ cloud services is the biggest and most mature public cloud platform on earth, which is why we built our WordPress multi-tenant cloud platform with AWS as the foundation.

View More Details

Containerized WordPress

Our container-based infrastructure provides quick scalability, availability, and resilience. All your WP installations come with uncapped performance & bandwidth.


View More Details

Take a look into your Low-Code SaaS Builder


WordPress Multisite combines all site resources (themes, plugins, etc) together under a single WordPress install (code and database). Whereas, multitenancy allows for completely individual WordPress sites (own resources and database) sharing a single WordPress codebase.


  1. All users who are added to your network will be users on all sites on your network.
  2. To allocate a different default role for users on individual sites, you must use a plugin.
  3. There is no way to restrict or impede updates on individual sites.
  4. All themes are installed for the entire network. If you edit the code of one theme, you edit it for all sites using that theme.
  5. There are many plugins that aren’t WordPress Multisite compatible.
  6. Changing hosts, or removing a single site from Multisite is very difficult. Moving back to the multisite is a pipe dream.
  7. A multisite network requires higher technical knowledge, especially in the areas of server administration and network management.
  8. Despite being on one WordPress install, hosting costs will reflect the need to host many websites.
  9. Issues that affect one site can (potentially) bring the entire WordPress Multisite network down.
  10. Noisy neighbor problem: if one website has a lot of traffic, it will affect the performance of the other websites because all websites run on the same server
  11. Backups and customizations are a problem in general
  12. You can’t improve your “prototype”: improve on your core website and safely ship this upgrade to all your existing customers.

Our multi-tenant cloud platform enables you to create multiple versions of any WordPress product that spin up highly-available tenants (websites) with shared functionality but separate content. This enables you to develop and distribute changes like a SaaS.

You can create multi-tenant WordPress products right in the platform and manage all websites as one product. Your entire Website as a Service and all tenants are hosted in the cloud, which means you can build any WordPress website and multiply as many as you wish.

WPCS guarantees uncapped performance for all websites. Our container-based infrastructure provides quick scalability, availability, and resilience.

All your WP installations come with uncapped performance & bandwidth. Moreover, the system enables you to automate the entire process from sale to launch. 

SSL Certificates are included. Our SSL certificates are provisioned using Let’s Encrypt’s services. They are based on single domains. So subdomain1.mywebsite.com and subdomain2.mywebsite.com receive separate certificates on different tenants.

It depends heavily on your current stack and functionality. In general, you can make an export of one of your subsites (including the plugins, themes, etc) and import that in a Version.

Deploy a Snapshot and create a new tenant based on that Snapshot. This allows you to test your product in WPCS without having to incur downtime. You can read more about this in our documentation.

After you have verified that everything is functional and in working order, contact us to discuss a migration plan. We are happy to help you migrate to WPCS.

Yes, you can place a CNAME record in your domain registrar. This way, when customers sign up on your website you can provide them with a subdomain (example.com, subsite1.example.com, subsite2.example.com) 

When customers are ready to launch their site, they can easily do so by changing their domain name. You simply have to add the main domain to the Tenant, Press verify and set it as the main domain. This can also be done using automations. We explain this in detail in our course.

Absolutely, we don’t have vendor lock-in. If one of your customers wants to leave, you can easily create an export of the website using the WP All in One Migration tool. If you want to leave, we will provide you with exports of your full stack at WPCS asap.

We are also working on the ability to download snapshots and tenant backups. This will allow you to host all the sites you have on WPCS on any traditional hosting solution.

We haven’t seen any plugins that are technically not supported so far. That being said, we do require plugins to ‘play nice’ with WordPress’ best practices. Especially when it comes to file management. Concretely: any plugin writing files must use the appropriate wp-content folder. (The path is found under the WP_CONTENT_DIR constant) 

We enforce this rule as both a security measure and as a best practice to keep your development cycle orderly and sane. From there, however, plugins are free to write to disk as they wish. As for adding constants to the wp-config.php file, this is currently not possible. 

We are working on allowing for tenant-specific constants to be defined before WordPress initialises. Until then, constants can only be defined in plugins or themes. If you have a specific case you’d like to discuss in this context, please let us know

It depends on what the SaaS/WaaS does. The most we can say is it won’t take much longer than if you’d build in WordPress elsewhere. We presume you also want to automate your business, which in total can amount to about a week. We include a full course after signing up for a trial.

Build a WP-based SaaS today

Start a 30-day free trial – Cancel anytime