We launched the multi-tenant WordPress Marketplace! 🎉

Earn more, spend less,
grow faster

Solve all scaling issues of Multisite by migrating to WordPress multitenancy

Supported by

The Multisite Dilemma

The infamous dilemma faced by multisite users.

Multi-tenant WordPress

Transitioning from a Multisite to WPCS turns subsites into single WP installations that have a separate database, but shared functionality.

vs

WordPress Multisite

It’s seemingly easy to build a WaaS using WordPress Multisite. We tried it too. Though, you inevitably run into scaling problems.

As your company grows

Increase in customers
Continuous, 100% confident development
Retain focus on customers; increased customer satisfaction; increased efficiency
Decrease in operating cost due to reduced hosting price, retain competitiveness
Improve product value at scale; charge more; increase profit margins & company valuation

As your company grows

vs

WordPress Multisite

It’s seemingly easy to build a WaaS using WordPress Multisite. We tried it too. Though, you inevitably run into scaling problems.

As your company grows

Increase in customers
Development cycle becomes more complex
Inhouse technical expertise requirements expand, driving up operational costs
Stagnation of product development
Lower profit margins & inability to innovate

Introduce WordPress multitenancy today

Solving the BIG Scaling issue

The three scaling issues of WordPress: technical, development, and business. These issues can never be solved by WordPress Multisite. You have to dig deeper. Fortunately, the dominant cloud infrastructure of SaaS is finally available: multi-tenant WordPress

Multisite vs WPCS

Key Differences

multi-tenant WordPress (WPCS)

Multisite

Database

Seperate WP installations

Shared over the network

Security

Decentralised infrastructure

Central point of failure

Development

A separate development environment

Live to production

User Data (Compliance)

Separated for each customer

User data is shared, making eCommerce impossible

Compatibility

The entire WordPress ecosystem

Limited compatibility

Scalability (Traffic)

Individual scaling

Centrally scaling resources

Scalability (infrastructure)

Unlimited

Natural cap approx. 500

Technical Expertise

No-code solution, just WordPress

Inhouse coding expertise

Case Studies

These companies are already getting results.

FAQ

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