A real, disposable WordPress — your user’s version, their host’s PHP — with your plugin already on it. One command.
Search WordPress.org by name or slug. Your guest gets a fresh sandbox with the plugin active — no SandyWP account required. Themes work too.
Free plan: 2 sandboxes, no credit card · Paid plans from $7/month
Trusted by
Count the steps between finding a bug and knowing the fix worked.
None of it is the part you are good at.
Or say it once to the agent in your editor.
“I build throwaway WordPress sites all day, to reproduce a bug or test a plugin. SandyWP makes that a single click. I liked it immediately.”
Austin Ginder anchor.hostFive ways. Pick the one nearest your hands.
cli deploy
Installs and activates a local ZIP. No upload form.
$ sandywp deploy acme-forms build/acme-forms.zip Every CLI command git deployment
Auto-deploy on push. Public or private repos.
$ git push origin fix/checkout-total How git deploys work push local
Mirrors a local install, database and all.
$ cd ~/Sites/acme-forms && sandywp push Push a local site mount
Save the file, refresh the tab.
$ sandywp mount acme-forms Mount a sandbox slack
Attach a ZIP to a mention. Nobody installs Node.
@SandyWP deploy development SandyWP for Slack github previews
A trusted collaborator tags SandyWP; the bot deploys and verifies the exact PR commit.
@sandywp-bot deploy SandyWP for GitHub Three of the five are the CLI — every command it has.
Somebody is stuck on WordPress 6.6 and PHP 8.1; somebody else is already on 7.1 RC 1.
WordPress
PHP
Extras
stable WordPress × PHP pairs.
pinnable releases, plus the 7.1 RC 1 track.
to switch PHP on a running sandbox.
before it ships
Click the paths deprecations break, before your users do.
Test on WordPress 7.1 RC 1The half of a bug report you never get is what the server saw.
| php.ini setting | Default | Range |
|---|---|---|
| Memory limit | 256 MB | 64 – 512 MB |
| Max execution time | 300s | 10 – 300s |
| Upload max filesize | 256 MB | 2 MB – 5 GB |
| Post max size | 256 MB | 8 MB – 5 GB |
| Max input vars | 1000 | 100 – 10,000 |
| allow_url_fopen | On | On / Off |
Six of the nine tunable values.
A real shell with WP-CLI, so tail -f wp-content/debug.log behaves as you expect.
Your own container. Keys only (ed25519, or RSA of at least 3072 bits), off by default.
Snapshot any sandbox — versions, plugins, theme, content, database — and relaunch it on demand. The combination that broke you becomes a fixture.
Every launch is a new, isolated site.
You describe the change; it comes back with the stack trace.
mcp server
One OAuth approval, then 51 tools: sandboxes, logins, PHP config, debug.log, files, git deploys.
claude mcp add --transport http sandywp https://app.sandywp.com/mcpcli
Every command you would type, your agent can run.
npx @sandywp/cli deploy acme-forms acme-forms.zipllms.txt
A machine-readable quickstart at the site root.
https://sandywp.com/llms.txtMore on AI development and AI features.
try-it link
Send /plugins/<your-slug>. A fresh WordPress, your plugin active, no account.
sandywp.com/plugins/your-plugincloner
The free Cloner plugin copies their live site into a sandbox. Production is only read.
wordpress.org/plugins/sandywp-clonermultisite
Tick multisite at create time. A real subdirectory network.
Create → Multisite (subdirectory)How Cloner packages a live site, and what it touches.
Priced on active sandboxes — not seats, not sites-under-management.
Free
$0forever
No card required
For finding out whether this fits.
Plus
$7/month
$70/year — 2 months free
Where the ZIP-and-upload loop disappears.
Pro
$17/month
$170/year — 2 months free
Keep a version matrix standing.
Max
$27/month
$270/year — 2 months free
For a shop with more than one product.
the arithmetic
50 sandboxes on Max is $0.54 each; 10 on Plus is $0.70. Yearly drops it further.
SandyWP vs InstaWP, in fullThe honest caveat: CLI, SSH, git deployment, Slack, PHP control and permanent sandboxes all start at Plus.
Same account, same sandboxes, no add-on pricing.
AI & MCP
Hand the loop to your agent.
CLI
Ship from the terminal that built it.
Git deployment
The branch you pushed, already running.
Templates
Save the awkward setup once.
SSH & SFTP
A real shell, with WP-CLI.
Debug mode
Toggle logging, read the fatal.
Cloner
Reproduce the bug on their site.
Slack
Drop a ZIP, get a site.
WordPress Beta
Meet 7.1 RC 1 first.
About 30 seconds from the warm pool. Pinned versions, multisite and preinstalled plugins provision cold and take longer.
CLI, git deployment, Slack, PHP control and permanent sandboxes. Free gives you 2 sandboxes, 256 MB and a 1-week lifespan.
ZIP upload caps at 50 MB. Bigger builds go over git or a mount.
Own container, own database. SSH lands you inside it — never the host, never another tenant.
Default 1 week; 1 hour to permanent at create time. Past a week needs a paid plan.
It stops, then waits before permanent deletion: 6 hours for guests, 12 hours on Free, 7 days on paid.
Yes — 7.1 RC 1 is a create-time option, always provisioned cold. WordPress 7.1 is due 19 August 2026.
No. Keep building locally; this is where the build meets a real server and a public URL.
Reset it to a clean install — same URL, same admin login — or delete it and start again.
Yes. /plugins/<slug> gives a guest a fresh WordPress with that plugin active, for 7 hours.
Nearly all of it. Local ZIP deploys are the exception — those go through the CLI.
Free plan, 2 sandboxes, no card.