test post asdf
The homepage is somebody else’s typing test
Three drafts called “test”, and a widget someone dragged out to see what happened.
Give every prospect their own working copy
A screenshot shows what your plugin looks like. Four minutes inside a real install tells someone whether it is worth paying for.
demo link · acme-pro
Acme Forms
Try the Pro build
Conditional logic, payments and Stripe entries, already wired up.
Trusted by
SandyWP / the shared demo problem
Nobody lands in a demo the last visitor wrecked
resets every 24h
The reset is a promise, not a guarantee
Until the cron misses a run and your plugin sits deactivated all weekend.
login: demo / demo
The credentials in the footer stopped working
A visitor changed the password to see if they could. Now every evaluation stops at the login screen.
the alternative
Stop resetting the demo. Stop sharing it.
Each click provisions a separate WordPress install from your template. Break one, and the next visitor still walks into something clean — because they walk into a different site.
SandyWP / how it works
Four steps to a demo you never have to babysit
Stage it the way a buyer should meet it
Install your product, switch on the settings that make the case, fill it with content that isn’t Hello World.
Freeze that exact site
Save it as a template: WordPress and PHP version, plugins, theme, content, settings, database.
Turn the launch link on
Add your branding. Decide whether visitors walk straight in or leave an email first.
Let them in, one click deep
Each click builds a fresh copy and drops that visitor into wp-admin with a magic login.
SandyWP / two demo surfaces
Where your product lives decides which link you hand out
free · on wordpress.org
Your demo link already exists. You just haven’t typed it.
Swap the domain on your wordpress.org URL. That link builds a fresh site with your plugin installed and activated, and the visitor never makes an account.
- Paste it in a readme, a listing, or a tweet
- No setup — published slugs work today
- The sandbox belongs to the visitor, not to you
instant launcher
https://app.sandywp.com/plugins/your-plugin-slug
https://app.sandywp.com/themes/your-theme-slug
premium · custom · white-labelled
Selling something the directory has never seen? Ship a template.
A Pro build, a rebranded fork, a plugin wired to a demo account — none of those are a public slug. Build the site once, save it as a template, share its launch link.
- Your logo, headline and button copy
- Optional email before the demo starts
- Re-save whenever the product moves on
template launch link
https://app.sandywp.com/launch/acme-pro-demo
email gate: on powered-by: hidden
the cloner
The best demo content is content that already exists
A clean WordPress with three lorem-ipsum posts looks like a prototype. Install the free Cloner on a site you already have, and one click packages its database and wp-content into a sandbox — then save that as your template.
- One plugin install, one approval — no FTP
- The source site is only ever read
- Large sites upload in resumable chunks
clone · one click
live site
acmeforms.com
sandbox copy
acme-demo-source
template
acme-pro-demo
What changes when the demo is theirs
evaluation
They test the product, not a recording
A video proves it worked once, on your machine. A sandbox lets them check the thing they actually doubted.
isolation
The demo can’t be wrecked, because it isn’t shared
Every launch is a separate install. Whatever one visitor breaks, the next lands somewhere else entirely.
white label
It’s your product in the demo, not ours
Your logo, headline, button copy and background on the launch page, plus a “Hide Powered by SandyWP” toggle.
lead capture
A click can leave you an address
Turn the email gate on and every launch files an address, with a timestamp, under that template.
no ops
Nothing to host, patch, or reset on a cron
No demo server to keep alive, no restore job to babysit. Copies expire and clean themselves up.
live calls
Start the demo mid-sentence
They ask “can it do X?” — paste the link into chat. The follow-up call becomes optional.
slack
Someone asks for a demo in the channel. Someone answers with one.
Mention the bot and a real WordPress comes back in the thread. Name up to ten
wordpress.org plugins to preinstall, pin a version with wp: 6.8, or attach a
plugin ZIP to put your unreleased build on it.
- Mentions only — no slash commands
@SandyWP loginmakes the site theirs- Deleting a site needs a button press
#acme-x-prospect
Priya
Prospect wants the Pro build with payments before Thursday.
Marco
@SandyWP create a site wp: 6.8 with woocommerce, contact-form-7
SandyWPapp
Ready — acme-demo-3.sandywp.dev · 2 plugins installed
SandyWP / staying current
A demo is only persuasive while it is still true
git deployment
Your demo shows what you merged this morning
Point the demo sandbox at a GitHub branch and every push redeploys into wp-content. Re-save the template when you’re happy; copies already open are untouched.
Git deploymentwordpress beta
Answer “will this survive the next WordPress?” with a link
Build the same demo on WordPress 7.1 Beta 3, due 19 August 2026. Pre-release versions always provision cold, so allow a few extra seconds.
WordPress beta testingSandyWP / where the link goes
Put it wherever “book a demo” is currently losing people
- wordpress.org readme
- marketplace listing
- pricing page, next to Pro
- cold email
- the docs page
- booth QR code
- a support reply
SandyWP / what it costs
Demo infrastructure, priced like a side project
Free
$0/ forever
- 2 active sandboxes
- 256 MB storage
Plus
$7/ mo
- 10 active sandboxes
- 5 GB storage
Pro
$17/ mo
- 25 active sandboxes
- 15 GB storage
Max
$27/ mo
- 50 active sandboxes
- 30 GB storage
Yearly is ten months’ price. The Free tier needs no card.
You choose who a demo is charged to
“Visitor pays” leaves your limit untouched. “My account pays” uses your slots, and shows “demo unavailable” once they’re full.
The wordpress.org launchers never touch your quota
A launcher visitor gets a sandbox created under their own session, not your account.
Concurrency is the number, not total demos
A guest demo lives 7 hours, then expires with a 6-hour grace period before deletion.
What you’re actually comparing it to
Roughly $0.50–$0.70 per sandbox per month on Pro and Max — against a VPS bill plus whoever maintains it.
SandyWP / the rest of the box
Not everything here is a sales tool. Some of it helps anyway.
Have an agent build the demo for you
51 MCP tools behind one OAuth approval: an agent can create the sandbox, save the template, hand back the link.
AI & MCPScript the demo refresh instead of clicking it
Create a sandbox, deploy a plugin ZIP, push a local install — all from a terminal.
The CLIFind out what a prospect actually broke
Flip WP_DEBUG on that sandbox and read its debug.log in the dashboard.
Debug modeFix the demo without leaving your editor
Paid plans get a real shell in the sandbox, and can mount its files as a local folder.
SSH & SFTPSandyWP / good to know
What sales and product teams ask
Does each visitor really get their own site?
Yes — a separate WordPress install with its own database, files and URL, isolated from every other sandbox.
Do they need to sign up?
No. Launcher links and ungated template links work with no account. With the email gate on, they type one address.
How long does a demo last?
A guest demo runs 7 hours, then expires and is deleted after a 6-hour grace period. Signed-in visitors get their own plan’s lifespan.
Can I hide SandyWP’s branding?
On the launch page, yes — full branding plus a “Hide Powered by SandyWP” toggle. The demo site itself still sits on a sandywp.dev subdomain.
Can I collect emails from demo launches?
Yes, through the optional email gate. Addresses and timestamps show up in the dashboard, API and MCP — a list, not a CRM integration, and it syncs nowhere on its own.
What if my product isn’t on wordpress.org?
Use a template. Build the site once with your premium build installed and share its launch link; templates don’t care where the code came from.
Can I see who launched a demo?
Only email-gated launches, and only the address and timestamp. There is no usage-analytics dashboard — no session length, no click paths.
What stops someone abusing the link?
Guest limits: one active sandbox per visitor and three per IP, capped at five creates per visitor and fifteen per IP inside the rate-limit window.
Can I change the demo after people are using it?
Refine the source sandbox and re-save the template. New launches get the new state; copies already open are untouched.
Stop describing it. Let them use it.
Free account, one template, a link every prospect can click.