Robust, secure, instantly scalable WordPress sites, managed with an easy-to-use dashboard. Drive efficiency through business automation and advanced developer tools
Allowing small businesses and SMBs to compete better against monolithic corporations
Multitenancy allows for completely individual WordPress sites that share a single WordPress codebase.
Handle updates and upgrades, maintenance, and other related tasks centrally, minimising operational overhead.
Confidence that each site is scaled independently, having a separate individual WordPress installation.
Enjoy fast, reliable high performance WordPress websites managed by WPCS’s multi-tenant cloud platform on AWS.
Maintain all the control that comes with managing your own infrastructure, but concentrate on websites rather than servers, allowing your team to focus on high-value work.
Our container-based cloud infrastructure can manage any traffic spike, without sacrificing performance, consistently delivering optimal performance as expected.
Fully managed and free HTTPS certificates, automated backups and manual backups, and built-in security. WPCS comes included with everything you need to safely scale any WordPress site.
Safely share data while your website runs in the cloud. No more servers to configure. Manage thousands of sites from the Console while allowing individual sites the freedom to customise.
Manage your brand or customer websites from the Console to drive efficiency and minimize operational overhead.
Work directly from the Console using Version Control, enabling a safe and continuous development flow that remains simple no matter the scale.
Access the back-end from your sites; add sites with a few clicks based on starting points (Snapshots) that remain under the central control of Versions.
Easily change PHP and WordPress versions. Update themes or plugins, or migrate Tenants over to a new updated Version with a single click.
Collaborate in teams, connect domains, build scalable automations, and more.
Versions contain your brand or customer website’s features and functionalities. Move Tenants between Versions to safely and continuously develop your solution.
“It took us days to weeks to build new websites for partners, even though they were based on our successful product. Managing our websites took a large chunk out of our month. Turns out replicating success isn’t as easy as duplicating a website, managing it like a SaaS takes even more time! We were seriously concerned about the scalability of our portfolio, while our customers were anxious to work with us.”
“WPCS is just a great service. From now on, managing hundreds of WordPress sites is a breeze. With just a few clicks all of them are updated or provided with a new feature/plugin.
WPCS introduces DevOps best practices to WordPress, enabling anyone to build enterprise-level hosted SaaS solutions.
Run PHP in your Tenants when certain important events happen. For example, an email to notify you or your customer whenever a site is created.
Automate Tenants provisioning, plan management, up and down-selling, and domain configurations using WordPress and the WPCS API.
Implement DevOps best practices at scale to WordPress using continuous integration and deployment pipeline with 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 20gb of storage. 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 your use case requires more storage, contact us for 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