deploy
Ship from the terminal
One command uploads, installs, and activates your plugin ZIP on an existing sandbox.
$ sandywp deploy test-site my-plugin.zipOne URL gives anyone a fresh WordPress site with your plugin active. Behind it: disposable sandboxes for testing every build before it ships.
Search WordPress.org by name or slug. Your guest gets a fresh sandbox with the plugin active — no SandyWP account required. Themes work too.
Choose latest WordPress, pin a supported release, or test the current preview across PHP 8.1–8.3. That “works on my machine” bug has fewer places to hide.
Explore PHP switchingWordPress
PHP
Extras
deploy
One command uploads, installs, and activates your plugin ZIP on an existing sandbox.
$ sandywp deploy test-site my-plugin.zipdebug
Toggle WordPress debug flags per site, read debug.log in the dashboard, or use SSH and WP-CLI when you need a shell.
Dashboard → Debug mode → Enablereset
Reset a standard sandbox to a fresh WordPress install while keeping its public URL and admin login.
Dashboard → Reset to clean slatePrefer the terminal for the whole environment? See every SandyWP CLI command.
Default-stack sandboxes use a warm pool and are typically ready in seconds. Pinned or preview WordPress versions, multisite, and plugin installs take a little longer while SandyWP provisions the requested stack.
Yes. Send them /plugins/<slug> and they can launch a fresh guest sandbox with that WordPress.org plugin active. SandyWP may ask for an abuse-protection check before creating the site.
That is what the sandbox is for. Reset a standard site to a clean install, or delete it and create another. Your production site stays out of the test loop.
It complements it. Keep building locally, then deploy a plugin ZIP or push a local WordPress install to a real, shareable URL on the stack you choose.
Free to start your first reproduction site is seconds away.