This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
SpawnWP turns a fresh Debian or Ubuntu VPS into a self-hosted WordPress lab where developers can create isolated, disposable WP environments from a web cockpit. Build a plugin, test a theme, run QA tools, snapshot, reset or destroy the site when you’re done.
I built SpawnWP because I needed a simple, self-hosted way to create clean WordPress environments for plugin/theme development without reusing the same messy test site over and over again — and without depending on a hosted service for every experiment.
SpawnWP turns a fresh Debian or Ubuntu VPS into a WordPress lab where you can create disposable, isolated environments from a web cockpit.
The workflow is intentionally simple:
Bring a fresh VPS/Server Point two hostnames to it Run the installer Open the cockpit Create a clean WordPress environment from one of three built-in blueprints Work, test, snapshot, reset or destroy it
What’s included:
Isolated per-site WordPress stacks Multiple PHP versions Mailpit and Adminer Snapshots, reset and destroy actions WordPress.org-oriented QA tools Plugin Check Theme Check PHPCS/WPCS PHPStan Query Monitor HTTPS and separate cockpit hostname Optional opt-in telemetry MIT license
SpawnWP is not a hosting panel and it is not designed for production hosting or client accounts. It is meant for development, testing, demos and disposable WordPress labs on infrastructure you control.
The optional SpawnWP Deploy plugin is only a narrow one-time transfer helper for moving a finished site to a fresh target WordPress install. It is not required to use SpawnWP.
I’d really appreciate feedback from WordPress plugin/theme developers, especially on:
The installation flow The cockpit UX Missing QA tools What would make it more useful for WordPress.org submissions Whether the “self-hosted lab” positioning is clear enough
No comment highlights available yet. Please check back later!
About SpawnWP on Product Hunt
“Self-hosted disposable WordPress labs”
SpawnWP was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #66 on the daily leaderboard. SpawnWP turns a fresh Debian or Ubuntu VPS into a self-hosted WordPress lab where developers can create isolated, disposable WP environments from a web cockpit. Build a plugin, test a theme, run QA tools, snapshot, reset or destroy the site when you’re done.
SpawnWP was featured in Open Source (68.6k followers), WordPress (21.5k followers), Developer Tools (515.4k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 114.4k products, making this a competitive space to launch in.
Who hunted SpawnWP?
SpawnWP was hunted by Maurizio Savoni. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how SpawnWP stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Maurizio Savoni
Hey Product Hunt 👋
I’m Maurizio, the maker of SpawnWP.
I built SpawnWP because I needed a simple, self-hosted way to create clean WordPress environments for plugin/theme development without reusing the same messy test site over and over again — and without depending on a hosted service for every experiment.
SpawnWP turns a fresh Debian or Ubuntu VPS into a WordPress lab where you can create disposable, isolated environments from a web cockpit.
The workflow is intentionally simple:
Bring a fresh VPS/Server
Point two hostnames to it
Run the installer
Open the cockpit
Create a clean WordPress environment from one of three built-in blueprints
Work, test, snapshot, reset or destroy it
What’s included:
Isolated per-site WordPress stacks
Multiple PHP versions
Mailpit and Adminer
Snapshots, reset and destroy actions
WordPress.org-oriented QA tools
Plugin Check
Theme Check
PHPCS/WPCS
PHPStan
Query Monitor
HTTPS and separate cockpit hostname
Optional opt-in telemetry
MIT license
SpawnWP is not a hosting panel and it is not designed for production hosting or client accounts. It is meant for development, testing, demos and disposable WordPress labs on infrastructure you control.
The optional SpawnWP Deploy plugin is only a narrow one-time transfer helper for moving a finished site to a fresh target WordPress install. It is not required to use SpawnWP.
I’d really appreciate feedback from WordPress plugin/theme developers, especially on:
The installation flow
The cockpit UX
Missing QA tools
What would make it more useful for WordPress.org submissions
Whether the “self-hosted lab” positioning is clear enough
Repo:
https://github.com/tts-empire/sp...
Docs:
https://spawnwp.com/docs/
Thanks for checking it out!