Enjoy uncapped performance and unlimited bandwith using the WordPress multi-tenant cloud platform
Continuously update your product for all customers, collaborate in teams, connect domains, build automations and more.
In WPCS, all your websites are separate WordPress installs, but theme files, plugins, and language files are shared under the same Version.
Within a Version, all websites have the same functionality, but separate database.
This enables a SaaS-like development cycle that’s continuous and 100% secure.
Automate tenant provisioning and build other automations by leveraging the WPCS API.
Deploy Snapshots to send changes in your Version directly to all Tenants. Snapshots also function as templates when launching new Tenants.
Powered by Amazon Web Services, all sites come with unlimited bandwidth and uncapped performance.
Automated and manual backups, SSL, and build in security. WPCS comes included with everything you need to safely scale your WP-based SaaS,
WPCS introduces DevOps best practices to WordPress to build enterprise-level hosted SaaS solutions
Versions contain your solutions features and functionalities. Move tenants between versions to safely to continuously develop your solution.
Implement DevOps best practices at scale to WordPress with your continuous integration and deployment pipeline using the WPCS CLI.
Due to the scalable nature of WPCS, tenants do not run on the same type of machine, or even container, for every request. This means we need to talk in terms of PHP processes.
A single PHP process is by default allowed to use up to 0.5 CPUs and 256MB memory. You can contact us to increase the available resources for a single PHP process.
To summarize, how much CPU and RAM your tenant has depends on how busy the site is. The more your site is accessed and the more resources it needs, the more resources our systems will assign to your tenant. This makes sure your tenant is always available and performant.
We provide unlimited storage and bandwidth, based on our Fair Use Policy. This should work for almost all use-cases. A notable exception to this rule is video hosting. If you want to play videos on your Tenants (websites), please make sure these are hosted elsewhere.
If we do find you in breach of the Fair Use Policy, we will first contact you to see if we can come to a solution. If a solution is not viable, we will add fees.
Our pricing is flat, keeping our Fair Use Policy in mind. Getting a lot of traffic on a single tenant will simply scale up your product.
We will contact you if your product exceeds our Fair Use Policy in terms of resource usage. This hasn’t happened yet with any of our clients. We will always contact you first whenever it may happen to find a solution.
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.
Let’s say you want to enable your customers to sell products via their website. So you decide to make WooCommerce available to your customers.
First, create a new Version in the Console and give it a name, like ‘v2’. In the version’s Snapshot Editor (click the Editor button), add the WooCommerce plugin. After it has been installed successfully, head back to the Console and Deploy the Snapshot.
Now, head to a Tenant you want to upgrade with WooCommerce. Create a manual backup, and give it a name “woo commerce added”. Then, you’ll find the Move to Version button under the Actions dropdown in the upper right corner.
Click it and select the ‘v2’ Version, the one you just now created. After the move is complete, you’ll find that you can activate WooCommerce in the Tenant.
Run a few safety checks to see if the changes didn’t break anything after activation. When no errors occur, make these changes over a subset of your customers. Create backups and test accordingly.
When the changes won’t affect any of the sample size, you can be confident to execute the changes over all your customers.
After you have created Version 1 of a Product and created a Snapshot of your version for sale, you can create a new Version (Version 2) to continue developing your product.
Sale of websites is then based on the Snapshot you made of Version 1. Version 2 is used as a production website in this way. When your Version 2 is ready, you can take a Snapshot of it so that it will be used for sale from now on. All existing customers who used Version 1 can be moved to Version 2, so that they will in fact receive an upgrade.
You can keep creating new Versions and upgrade your Product in the same way after that. Using this method, you can develop Versions independently and test whether the Versions are mutually compatible.
Be sure to set the Version you want new Tenants to be created on (when using the API) to be the production version!
The multi-tenant environment is set up when you create a Version of your product. This means that the plugins and themes installed there are available to all Tenants.
Updating plugins or themes is done by creating a new Version of your product, doing all updates therein and then moving tenants to the new Version. In this way, all Tenants will eventually have access to the new or updated functionality. It’s super easy.
Start a 30-day free trial – Cancel anytime