WordPress hosting for people who build the plugins.
Testing a plugin means running it in several environments at once. Most hosting is built for people who run one site, carefully.
Everything a plugin developer asks of a host.
Your staging is not one copy of production. It is one copy per scenario you support.
PHP versions in parallel, not in sequence
Supporting a range of PHP versions means running several at once. Switching is per site rather than per server, so the matrix is a set of sites rather than a migration.
Clones treated as disposable
A test matrix is a lot of copies with short lives. Cloning is fast and unlimited, because a host that rations it makes you test less than you meant to.
WP-CLI on every site, no ticket
Fixtures, generated users and bulk imports are CLI work. A panel-only host turns each one into a manual afternoon.
Debug output where visitors cannot see it
WP_DEBUG is togglable per site with logs written outside the webroot, so having it on somewhere is not a disclosure.
Multisite as an option, not a tier
Network compatibility is a real support burden, and it cannot be tested without a network to test it on.
The environments, in one place.
The overhead in this work is not writing the code, it is keeping half a dozen environments straight and knowing which one is on which version.
- PHP version per site at a glance
- Clone and reset from the dashboard
- One-click admin login on every install
- Restore any daily backup from the dashboard
A clone in less time than a coffee.
Clone speed decides how much you actually test. If a copy takes twenty minutes, the edge cases quietly stop being checked.
What we change for a plugin developer
These differ from a standard WordPress site on the same plan, and each follows from needing many environments rather than one good one.
| Setting | What we do | Why |
|---|---|---|
| PHP version | Switchable per install rather than per server | Testing across supported versions means running them simultaneously, not migrating one server back and forth between them. |
| WP_DEBUG | Toggleable per site with logs written outside the webroot | Debug output inside a public directory is a disclosure, and a developer needs it enabled somewhere permanently. |
| Cloning | Fast and unlimited, treated as a test matrix rather than a backup | A host that rations clones makes you test fewer scenarios than you intended to, and the ones dropped are always the awkward ones. |
| WP-CLI | Available on every site without a support request | Fixtures, user generation and bulk imports are command-line work, and a panel-only host converts each into manual effort. |
| Multisite | Available as an ordinary option rather than a plan tier | Network compatibility generates real support load, and it cannot be tested without a network available to test against. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can I run different PHP versions at the same time?
Is there a limit on clones?
Do I get WP-CLI without asking?
Can I leave WP_DEBUG on?
Is multisite available for testing?
Build your plugin on hosting shaped like a test matrix.
Free migration, PHP versions in parallel, and clones fast enough that you actually use them.