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.
The panel is a layer on top of servers you own at a provider. Cancelling one does not touch the other.
Your servers live at DigitalOcean, Vultr, Linode or similar. Cancelling GridPane leaves them running and billing; cancelling the provider leaves the panel managing nothing.
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.
Backups and scheduled tasks configured through the panel stop when the panel does, and nothing in WordPress records that they existed.
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.
A GridPane server frequently hosts several sites, including staging copies somebody set up and forgot. Those are enumerated before anything is destroyed.
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.
A well-configured GridPane server performs well. What changes is that the tuning stops being something you maintain across two vendors.
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. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, configuration captured before anything is destroyed, and both accounts unwound in order.