TOOLNAVIA / BUYING GUIDE
Cloudways Flexible Cancellation: Stop Billing by Deleting Resources, Not Pausing
The short answer
Cloudways Flexible cancellation is different from canceling a prepaid shared-hosting plan because Flexible is **pay-as-you-go and postpaid**. The key rule is simple: **stopping a server is not the same as stopping billing**. Cloudways says customers must delete billable servers/resources and deactivate paid add-ons to stop future charges.
At a glance
- Best for
- Flexible users planning to stop billing or permanently exit without losing data.
- Price model
- Pay-as-you-go postpaid; final charges depend on accrued resources
- Check first
- Stopped servers can still incur costs; final invoice may arrive later; account cancellation is permanent.
Delete billable resources before canceling the account
Cloudways' account-cancellation guide requires the account owner to back up or migrate data, delete active servers and deactivate add-ons before permanent account closure. Support cannot perform the final owner-only cancellation on your behalf.
If you only pause or stop a server, infrastructure/storage charges can continue. The safe billing test is not “is the server stopped?” but “are there any billable servers, resources or add-ons left?”
A final invoice can arrive after deletion
Cloudways bills postpaid, so deleting resources today does not erase usage already accumulated in the current billing period. The cancellation guide warns that a final invoice can still be issued in the following billing cycle. Save usage/billing screenshots before deleting resources so you can reconcile the final statement.
You do not have to close the whole account to stop billing
Cloudways says an account with no active billable servers and no paid add-ons can remain open without ongoing charges. If you only want to stop spending but may use Cloudways again, deleting billable resources can be less destructive than permanently canceling the entire account.
Back up before deleting servers
Cloudways documents recovery options for some deleted applications/servers when eligible backups still exist, but account cancellation itself is permanent and canceled-account data cannot be recovered. Treat provider recovery as a safety net, not your migration plan.
Keep an independent archive of files, database, application configuration, DNS records, SSL/integration settings and any mail service data that lives outside Cloudways.
Migrate and cut DNS before deleting the old path
Cloudways' current WordPress onboarding guide recommends verifying the migrated destination, performing a final sync, updating DNS, confirming the domain resolves to Cloudways and retaining a fallback before the previous host is canceled. The reverse move should use the same discipline: build the replacement, sync, switch DNS, verify traffic, then delete Cloudways resources.
Other hosts use different cancellation logic
HostPapa, Verpex, HostArmada and ChemiCloud are generally plan/term-based hosting products with different refund and retention rules. Their workflows do not change Cloudways' postpaid rule: billable resources and add-ons must be removed to stop future charges.
Exit checklist
Before leaving Flexible: inventory every server/application/add-on; download an independent backup; build and test the destination; perform final sync; switch DNS; verify traffic and external services; delete Cloudways servers/resources; deactivate paid add-ons; review estimated usage; wait for/reconcile the final postpaid invoice; then permanently cancel the account only if you no longer need it.
Affiliate disclosure: Toolnavia may earn a commission from an eligible Cloudways purchase; that does not change the postpaid billing or cancellation analysis.
