Start free

The test copy: private, isolated and gone after the run

2 min readBy the Verploy team

Isolation, checked on every runNo emailmail isstopped beforeit leavesNo requestsno CRM, nowebhooks, nopaymentsNo cronscheduled tasksand ActionScheduler offNot indexednoindex andprivate, onlyfor Verploy

A test copy is only safe if it cannot do anything in the real world. A copy that sends order emails, fires webhooks or renews subscriptions is not a test; it is a second live site.

On the site’s own hosting

Verploy makes the test copy on the same server as the live site, with the same files and database tables. That way the test runs on the same PHP version and server settings as the real site. After the run, the copy is removed.

Isolated, and checked every time

  • No email: outgoing mail is stopped before it leaves.
  • No outgoing requests: nothing reaches a CRM, Zapier or a payment provider. Only downloads from WordPress.org and Verploy are allowed.
  • No scheduled tasks: WP-Cron and Action Scheduler are switched off, so no subscription renewals or webhooks fire.
  • Not visible and not indexable: only Verploy, or an admin with the run token, can open it.

Verploy checks this isolation at the start of every run and shows it in the run: “Test copy isolation verified”.

A safe update that was held back on the test copy (example data)
What fails on the copy stays on the copy. (Example data.)

Want to see it on your own sites? Start free on up to 3 sites, no credit card.

Start free
Changelog
System status

Keep reading

How it worksDay one: can Verploy work on this hosting? The connection checkHow it worksEvery update checked, risky ones tested on a copy first: how Verploy decidesHow it worksForms and checkout, tested on the test copy before every risky update
View all posts