Worker-based provisioning
A dedicated worker pulls a job, builds your sandbox, and reports back. Same architecture in dev, staging, and prod.
SandyWP keeps the surface small on purpose. No templates, no team plans, no custom domains yet. Just disposable WordPress that works.
Every sandbox is a real WordPress install on real Docker, not a screenshot or a shared multisite.
A dedicated worker pulls a job, builds your sandbox, and reports back. Same architecture in dev, staging, and prod.
Each site gets its own WordPress + PHP container. Plugins crash? Your other sandboxes are unaffected.
A dedicated database inside shared MariaDB. Your data lives alone, your queries run alone.
wp-content uploads, plugins, themes — every sandbox gets its own volume. Nothing leaks.
Forget password emails and credential resets. Sandboxes are made to be opened.
A signed link drops you straight into wp-admin as the admin user. No email round-trip.
Each sandbox gets a predictable URL like `{slug}.sandbox.yourdomain.com`. Pattern is configurable in V1.
Production deployments terminate TLS at Traefik with ACME. Your sandbox URLs are HTTPS by default.
Sandboxes are short-lived on purpose. Less to remember, less to clean up, less to pay for.
Anonymous visitors can spin up a site without an account. It expires automatically the next day.
Sign up for free and your sandboxes stick around a full week instead. Same flow, longer lifetime.
Expired sandboxes are torn down by the worker. Database, files, route, container — all gone. No leftover invoices.
SandyWP exposes its own guts. Workers, jobs, failures, and cleanup live in an admin surface, not in SSH sessions.
See live workers, in-flight jobs, recent failures, and cleanup state from one screen.
Workers report their health and capacity continuously. No more guessing if a node is alive.
A `/health` endpoint for uptime monitors, load balancers, and your own dashboards.
Stuck sandboxes? Trigger cleanup directly from admin without SSHing into the box.
SandyWP is in beta. We are honest about what is in V1 and what is not. Here is what is explicitly out of scope today:
Most of these are on the roadmap. None are in V1. We would rather ship sandboxes that work than features that almost work.