1. Home
  2. Staging & Deployment
  3. Is Staging Available on All…

Is Staging Available on All Plans?


All of our hosting plans support staging functionality.

While each plan holds a predefined site limit, we don’t distinguish between how you decide to use those available “slots” for your apps. You’re free to create as many staging/development/testing instances as you would like — provided you do not exceed your plan’s limit.

You can find these allotments and other resources/features outlined in our comparison matrix page.

Creating a Staging Site

Assigning a new installation as your staging environment is accomplished in just a few clicks. Customers can navigate over to the Apps tab, click New App to set up a new instance, enter the domain name you want to use for the new site and select Save & Create.

Now that you have a staging app created, you’ll want to clone your content over to the new app. We have a couple of in-house tools that let you do this:

Pagely Sync & Pagely Clone

Using our Pagely Sync tool adds easy transporting for creating quick one-time copies of your site and cloning sites between staging and production environments for any one-off testing. After logging into your VPS via SSH, you can run simple commands to complete this update. Follow along in our technical support KB article Cloning WordPress Site with Pagely Sync for a full overview of steps to take.

Additionally, we offer a more robust tool called the Pagely Clone Tool if you need more repetitive cloning or have a Multisite application you’ll be cloning. This tools is better equipped to handle more granular settings than the Pagely Sync tool.

Git Integration Tool

Incorporating a proper version control schedule is strongly recommended for our Pagely customers. Our Git Integration tool can help simplify how to configure your GitHub repository to automatically deploy changes to your WordPress website and help save some time and stress on a setting up your workflow manually. Requirements, details, and considerations to be taken into account when using this tool to define your Git-based deployment approach are specified in the technical article linked above.

Was this article helpful?