Developer Hosting

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.

PHP version per siteClones as a test matrixFree migration
Per-site PHP switchingUnlimited clonesWP-CLI on every siteDaily backupsFree SSL24/7 support
Built for the matrix

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.

7.4 through 8.5Per install

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.

Operations

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
Test sites
Across versions
6 installs
PHP versions
In parallel
7.4 – 8.5
WP-CLI
Available
all sites
Nightly backup
Replicated offsite
running
Performance

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.

Per-site
PHP switching
Unlimited
clones
NVMe
storage on every plan
MagicWP clone45 ms
Manual export and import1400 ms
Plugin-based migration700 ms

Illustrative comparison of producing a working copy of a site by each method. Your numbers depend on site size.

Configuration

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.

SettingWhat we doWhy
PHP versionSwitchable per install rather than per serverTesting across supported versions means running them simultaneously, not migrating one server back and forth between them.
WP_DEBUGToggleable per site with logs written outside the webrootDebug output inside a public directory is a disclosure, and a developer needs it enabled somewhere permanently.
CloningFast and unlimited, treated as a test matrix rather than a backupA host that rations clones makes you test fewer scenarios than you intended to, and the ones dropped are always the awkward ones.
WP-CLIAvailable on every site without a support requestFixtures, user generation and bulk imports are command-line work, and a panel-only host converts each into manual effort.
MultisiteAvailable as an ordinary option rather than a plan tierNetwork compatibility generates real support load, and it cannot be tested without a network available to test against.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Can I run different PHP versions at the same time?
Yes, per site rather than per server. That is the difference between having a test matrix and repeatedly migrating one environment between versions to check each one.
Is there a limit on clones?
No, and that is deliberate. Rationing clones does not save resources so much as it quietly reduces how much you test, and the scenarios dropped first are always the difficult ones.
Do I get WP-CLI without asking?
On every site, immediately. Generating fixtures and test users is command-line work, and needing a ticket for shell access turns a two-minute job into an afternoon.
Can I leave WP_DEBUG on?
Yes, per site, with logs written outside the webroot. Debug output in a publicly reachable directory is a disclosure, which is why most hosts make you choose between visibility and safety.
Is multisite available for testing?
Yes, as a normal option rather than an upgrade. Network compatibility is one of the biggest sources of plugin support tickets and the hardest thing to test without a network.

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.