Here at Pagely, we've had customers requesting a staging location for some time, and we finally have an answer. Our <a href="https:\/\/pagely.com\/plans-pricing\/wordpress-vps-hosting\/" target="_blank" rel="noopener noreferrer">VPS hosting plans<\/a> and above (<a href="https:\/\/pagely.com\/plans-pricing\/enterprise-wordpress-hosting\/" target="_blank" rel="noopener noreferrer">Enterprise<\/a>) now feature staging - which is great news.\r\n\r\nThe current staging we have in place syncs files and databases between sites with the ability to ignore tables and\/or files. There is also a capability for basic site renaming, but without database rewriting of URLs since there are cases where that can cause issues.\r\n\r\nOur normal recommendation for developers wanting to test plugins\/deploys etc is to use our tool to sync production to staging.\u2002Then deploy changes using Capistrano or just a manual script and <a href="https:\/\/pagely.com\/blog\/what-is-wp-cli\/" target="_blank" rel="noopener noreferrer">wp-cli<\/a>,\u2002test and then run the same script against production. For non-developers we recommend a similar approach, but following a written script.\r\n\r\nWe are aware that many are seeking 2-way push-button syncing between production and staging, but syncing from staging to production with WordPress is very dangerous, and we can't with good conscious build or recommend a system that will blow up and destroy customer sites an estimated 1% of the time.\r\n\r\nAs time goes on we will be improving our staging aspect, and later this year rolling it out for our standard plans. Keep an eye out for updates as we are constantly working to improve various aspects of our service.