Team access
Invite members into the cockpit, share site visibility and keep platform-level controls with administrators.
Open source · Built with intention
What comesnext.
SpawnWP is growing from a focused single-admin lab into a stronger self-hosted workspace for WordPress teams — without turning into another hosted control plane.
This roadmap communicates direction, not deadlines. Priorities can change as the project learns from real-world use.
Planned — a committed product direction
Exploring — being evaluated, not committed
Already here — available in SpawnWP today
Now · Team foundation
One lab.
A whole team.
The first priority is safe collaboration and faster ways to reuse a working environment.
Fast local cloning
Duplicate a complete environment while regenerating its URL, credentials, salts, ports and private secrets.
Next · Developer workflows
Less repetition.
More momentum.
Once the team foundation is solid, SpawnWP can become easier to automate and connect to existing development workflows.
API tokens and CLI automation
Create, inspect, snapshot and destroy environments from trusted CI pipelines and local developer tools.
Git integration
Bring plugin and theme repositories into repeatable environments and run their build or test workflows consistently.
Safer temporary sharing
Demo Launcher can mediate protected, short-lived product demos and on-demand WordPress admin access without adding anonymous provisioning to the core.
In-browser terminal
A full interactive shell into each site's PHP container, straight from the cockpit — wp shell, Composer, Node and the whole QA toolchain without leaving the browser. The one-line WP-CLI console already ships as a first step.
Exploring · Compatibility
Broader testing.
Same boundaries.
Useful additions remain candidates until they can preserve SpawnWP's simple operations and secure defaults.
Optional WordPress Multisite
Create subdirectory Multisite environments for plugin and theme compatibility testing, with routing and lifecycle behavior designed specifically for the lab.
Already here · Shipped
Already in
your hands.
The foundation, plus the roadmap items already delivered and in use in the open-source project.
Isolated WordPress stacks
Independent Nginx, PHP, MariaDB, Mailpit and Adminer services for every environment.
Blueprints and snapshots
Repeatable starting states, database and media snapshots, restore controls and multiple PHP runtimes.
Reusable site templates
Capture a configured site — plugins, theme, media and content — as a versioned blueprint on your own server, then spawn fresh sites from it.
Disposable-site lifecycle
Give a site an optional lifetime; an hourly check removes expired sites, with a countdown badge and one-click extend or make-permanent.
WP-CLI console
Run WP-CLI inside any site straight from the cockpit, with its output streamed back live.
Secure web cockpit
Passkeys, TOTP fallback, recovery codes, HTTPS and loopback-only internal service ports.
Verified updates
Signed releases, dashboard updates and rollback without handing control to a hosted service.
Signed module foundation
Install separately released advanced workflows through verified, version-compatible packages while the open-source core retains provisioning and lifecycle control.
The boundary matters
Growth without losing the point.
SpawnWP will remain a controlled, self-hosted development lab. Its core will not become:
- An anonymous WordPress provisioning endpoint — an explicitly installed module must mediate public demo requests
- A Website-as-a-Service sales platform
- A production hosting control panel
- Continuous production staging synchronization
Follow the work
Built in the open.
Grounded in real use.
Watch the repository for implementation progress, release notes and the technical decisions behind each milestone.