The most scalable workflow for WordPress
Efficiently manage and continuously improve your websites using the leading SaaS-based cloud architecture.
No credit card required
What makes our workflow unique?
Multi-tenancy, the widely adopted SaaS cloud architecture, unifies all sites under a centralized codebase, enabling you to:
No credit card required
Continous improvement
With a centralized codebase, your sites receive more than just routine plugin updates. You also get the advantage of continually rolling out new features that all your customers will enjoy.
You can safely improve and add plugins and themes in an isolated clone of your application called a “version”, test, then move all sites there.
Issue with an update? Roll back affected sites with zero downtime for debugging, while keeping working sites on the latest version.
Build like the biggest names in SaaS
A few notable companies utilizing multi-tenant cloud architecture today:
How does it work?
Simple steps to update sites, whether you’re just starting out or managing thousands of sites.
The process remains simple and consistent.
1. Create version
Provision a separate environment for implementing changes to themes or plugin files.
2. Deploy snapshots
Save and deploy version updates with snapshots.
3. Test safely
Move staging sites between versions to test all changes safely.
4. Update customers
Once tested safely, move customers over to a new version with one click.
5. Rollback errors
Quickly roll back any unforeseen errors by switching back to an old version.
6. Debug sites
Debug affected sites while keeping others on the latest version.
Aron Martinez – Founder
AMWeb
Check out what users have built
Get inspired and see how you can transform your business too.
Jorge Santos – CEO
FreshRules Agency
Start your free trial today
Or continue to explore what makes wildcloud the ultimate solution to build recurring revenue with WordPress:
Sell pre-built WordPress sites on autopilot
Fully managed containerized infrastructure that can scale the most demanding applications with ease.
Frequently asked questions
The main benefit is to be able to continuously develop and update all your sites centrally and reliably, leveraging the same SaaS cloud architecture used by major website builders such as Shopify and Wix. Other benefits include the ability to automate processes, like sales and subscription management, and automatic scalability of your sites’ resources.
Once you have launched your product with Version 1 and created a snapshot for sale, you can initiate a new version (Version 2) to continue development. Sales will still be based on the snapshot of Version 1, while Version 2 serves as a test environment for further enhancements.
When Version 2 is ready, create a snapshot to make it available for sale. Existing customers on Version 1 can be migrated to Version 2, effectively receiving an upgrade. You can continue this process, creating new versions and upgrading your product over time. This approach allows you to develop and test versions independently while ensuring compatibility between them. Remember to set the production version as the default for new tenants when using the API.
In a multi-tenant environment, each product version you create includes the plugins and themes installed for all tenants. To update plugins or themes, create a new version of your product, perform the necessary updates, and then migrate tenants to the updated version. This process ensures that all tenants have access to the latest features and improvements, streamlining updates in a user-friendly manner.
While deploying a new Snapshot of your current Version is the quickest, it’s not always safe. To ensure safety, wildcloud has introduced the Versioning System. By creating a clone of your Version, you have a separate development environment for all your Tenants. You can create a duplicate of your Production Version, which is completely isolated. When ready, you can move your Tenants from your Production Version to your new development Version. Here are the steps:
- Create a new version
- Add new plugins and/or update existing plugins or themes through the version editor.
- Deploy a fresh snapshot to incorporate all updates.
- Move your tenants from the old version to the new version
- Create a new version
- Select the new version of WordPress or PHP and provision the version
- Test the new version by creating some test tenants
- Move production tenants when you’re confident they won’t break
- Move your tenants to the old version
- If you don’t have an old version, create a new version based on an old snapshot and move the tenants to this version