Managed WordPress hosting for sites leaving GridPane.
GridPane manages servers you rent from somebody else, so leaving it involves two relationships rather than one - and they have to be unwound in the right order.
What leaving a management panel actually involves.
The panel is a layer on top of servers you own at a provider. Cancelling one does not touch the other.
The panel is not the host
Your servers live at DigitalOcean, Vultr, Linode or similar. Cancelling GridPane leaves them running and billing; cancelling the provider leaves the panel managing nothing.
Configuration the panel wrote
GridPane manages nginx, Redis and PHP-FPM settings on your behalf. Those live on the server rather than in WordPress, so they are captured before the server goes.
Its backup and cron integrations
Backups and scheduled tasks configured through the panel stop when the panel does, and nothing in WordPress records that they existed.
Certificates and their renewal
Certificates issued through the panel renew through the panel. New ones are issued here, and the old renewal is retired deliberately rather than left to fail quietly.
Whatever else is on those servers
A GridPane server frequently hosts several sites, including staging copies somebody set up and forgot. Those are enumerated before anything is destroyed.
Unwind in the right order.
The expensive mistake here is cancelling the panel first and discovering the servers are still billing, or destroying the servers and losing the only copy of their configuration.
- Panel and provider accounts both inventoried
- Server configuration captured before decommission
- Cutover at a time you choose
- Servers left running until you confirm
The tuning without the two invoices.
A well-configured GridPane server performs well. What changes is that the tuning stops being something you maintain across two vendors.
What we change when a site arrives from GridPane
These are specific to leaving a management panel, which is a different exercise from leaving a host.
| Setting | What we do | Why |
|---|---|---|
| Account structure | Panel and infrastructure provider treated as separate relationships | Cancelling GridPane leaves your servers running and billing at the provider, and cancelling the provider leaves the panel managing nothing. |
| Panel-written server config | nginx, Redis and PHP-FPM settings captured before decommission | The panel maintains those on the server rather than in WordPress, so destroying the server destroys the only record of them. |
| Panel backups and cron | Recreated as platform jobs before the panel is cancelled | Anything scheduled through the panel stops when it does, and WordPress holds no evidence that it ever existed. |
| Certificates | Reissued here, with panel-managed renewal retired deliberately | A certificate that renews through a cancelled panel expires silently on whatever the renewal date happened to be. |
| Server contents | Every site on every server enumerated before anything is destroyed | A panel-managed server commonly hosts staging copies and side projects nobody has thought about in a year. |
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.
If I cancel GridPane, do my servers go away?
Where is my server configuration stored?
What happens to backups I set up in the panel?
I have several sites across a few servers. Can they all move?
When should I cancel the panel subscription?
Leave GridPane without leaving servers billing behind you.
Free migration, configuration captured before anything is destroyed, and both accounts unwound in order.