TOOLNAVIA / BUYING GUIDE
Cloudways Stop Application Access: The Master User Still Has a Route
The short answer
At a glance
- Best for
- Temporary application closures with named owners for access and scheduled-work recovery.
- Price model
- Use currentDigitalOceanPremium2GB configuration;serverusage,backups andadd-ons affect total.
- Check first
- Master directory access, databases and backups remain; no complete process-isolation or billing-stop guarantee.
Verdict: buy for the documented temporary boundary
Cloudways Flexible can suit an owner who wants to restrict an application temporarily without deleting it. Its Application Access control has a specific boundary: the website and application credentials stop working, application cron pauses, but the master user retains directory access and database/backups remain active. This is not complete administrator isolation.
This guide analyzes documentation. No application, server, credential, cron job, billing record or website setting was operated.
Review the exact Flexible offer. Toolnavia may earn a commission on an eligible purchase.
Write the closure goal before choosing the switch
An unfinished development app, a temporary business closure and a suspected credential problem have different requirements. State whether you need to stop public browsing, suspend a particular user's file access, pause scheduled work or address a wider privileged-access concern.
The provider says both the normal domain and temporary website URL become inaccessible. That is useful for the documented web boundary; it does not establish the state of every external copy, distribution layer or separate integration. Do not infer an HTTP status code from the word inaccessible.
If the goal is to let selected reviewers browse, inspect a supported preview arrangement instead. A switch that blocks web access is not automatically a selective client-review service.
Account for the master-user exception
Cloudways distinguishes master credentials, which reach applications across the server, from application-specific credentials. The stopped application's master route remains documented. Turning off application access therefore does not revoke every privileged maintenance path.
Keep a separate inventory of who has master or platform authority and who owns access review. An unresponsive homepage cannot demonstrate that credentials have been revoked. If the requirement is to remove a person's access, evaluate the actual credential and role controls for that requirement rather than assuming this visibility switch does it.
Paused cron creates a resumption responsibility
The guide explicitly pauses scheduled cron configured for the application while retaining database and backup services. Do not extend that statement to every independently supervised worker or external scheduler. Inventory the business work that normally depends on those schedules.
Before resuming, decide how to review work that became due during the pause. A reminder, cleanup operation and billing task may require different treatment. Do not replay every missed operation blindly. These are planning questions, not measured Cloudways job behavior or a performed recovery test.
The useful capabilities are a reversible app switch, the web gate, application-credential restriction and cron pause while data services remain. Their boundaries are part of their value, not incidental exceptions.
Compare pause meanings instead of importing them
WordPress.com's Private mode permits approved logged-in viewers and disables certain external features. That is its visibility model, not a feature inherited by a self-hosted Cloudways site.
Shopify separately warns that third-party app charges can continue on Pause and Build. Its plan and billing rules do not apply to Cloudways; they demonstrate why a word such as pause needs a service-specific definition. Check the actual retained Cloudways resources and invoice rather than treating this access toggle as a cancellation record.
Google's current temporary-closure guidance generally prefers limiting functionality over a prolonged whole-site closure when preserving Search presence matters. That is a separate decision from restricting an unpublished app. No Cloudways response or indexing result was tested here.
Accept both the closure and the return
For a proposed authorized exercise, use a disposable application and harmless scheduled work. Record intended web and credential restrictions, the remaining master route and retained data services. Verify the documented scope, then re-enable and accept the intended application and scheduled-work result. No exercise was performed.
Confirm the exact Premium 2GB configuration, usage, backups and add-ons in the selected offer and bill. The multiple DigitalOcean plan tables do not justify a universal quote or a zero-cost pause promise.
Choose Flexible when this maintained boundary suits the application. A reversible switch is useful only when someone also owns what continues running and what must happen when access returns.