Point it at a repo
Paste the URL, pick the branch, and say where the files go: plugin, theme, or a wp-content folder.
git push is the deploy button
Connect a GitHub repo to a sandbox and deploy a plugin, theme, or the whole wp-content folder into it. By hand, on every push, or from any tag you name.
repository
github.com/acme/acme-blocks
wp-content/plugins/acme-blocks
mainPrivateAuto-deploy
deployments
a91f3c2 fix: guard empty gallery push
4d2e0b8 feat: block variations push
7c10ba5 release: 1.3.2 manual
e42d918 chore: bump tested up to push
Trusted By
Connect it once, then forget it
Deploy now
One click clones that branch and syncs it into the sandbox. The commit and its message land in the history.
Hand it the webhook
Paste the webhook URL into your repo settings. From then on every push to that branch deploys itself.
Reach for a tag
Need the version that shipped the bug? Deploy any tag or branch once, without moving your configured branch.
What a deploy actually does
plugin · theme · wp-content
You choose where it lands
wp-content/plugins/your-folder, wp-content/themes/your-folder, or straight into wp-content. That folder belongs to git: delete a file in the repo and the next deploy deletes it on the site.
shallow clone
A copy, not a build
One ref, one commit deep. The .git directory is stripped and the tree is copied in as it sits. No install step, no bundler, so commit what you want running.
www-data
Ordinary files afterwards
The synced folder is owned by the web user, so the file manager, SSH, SFTP and WordPress itself keep working on it like any other plugin.
Reproduce the bug against the release that shipped it
A customer is on v1.3.2 and you are three months past it. Deploy that tag into a sandbox for one run, watch it break, then go back to your branch.
- ✓ Deploy any tag or release, or any other branch
- ✓ Branch and tag lists read live from the remote
- ✓ One-off: your configured branch and webhook never move
deploy a branch or tag
BranchesTags
One-off deploy. Configured branch stays main.
What developers ask
Does my repo have to be public?
No. Choose Private and SandyWP generates an SSH deploy key on connect, then shows you the public half. Add it to your repository as a read-only deploy key and clones authenticate with it.
Is there a build step?
No. The clone is copied in exactly as committed, so whatever is in the repo is what runs. If your plugin needs compiling, commit the built files or run the build yourself over SSH.
What happens to files I edited on the sandbox?
The destination folder is replaced on every deploy, so edits inside it are overwritten. Everything else on the site, including the database, is left alone.
How many repositories can one sandbox have?
One. The branch, folder name and auto-deploy setting are all editable afterwards, and disconnecting leaves the deployed files and the history in place.
Can an agent deploy for me?
Yes. Connecting a repository, listing its branches and tags, and triggering a deployment are all MCP tools, so an assistant can ship the change and read debug.log without you switching windows.
Connect a repo. Push. Look at it.
Free account, a sandbox, and a deploy in the time it takes to paste a URL.