Building a site on Cloudways: servers, applications and account verification

When you build a site on Cloudways, the server is the runtime environment, an application is a website inside it, and projects organize your work. Keeping these levels separate makes it easier to understand the difference between adding a website, adding a server and changing a plan. Do not let an installed WordPress site distract you from other resources in the account that are still generating charges.

This guide mainly follows the public documentation for Cloudways Flexible. Autonomous is a different product experience: check its own deployment and billing terms rather than applying Flexible server steps directly. No testing in a user's account was performed, and no speed ranking of cloud providers is offered. Choose according to your website's needs, available regions and actual account conditions.

Complete account activation and any individual verification requirements

Register through the official Cloudways entry point, using an email account you can continue to receive messages at, and follow the required email or other activation steps on screen. If the account is awaiting verification, save the message and the time it appeared, then confirm the next step through official support. This status is unrelated to DNS settings; changing the website's domain will not remove an account-level restriction.

No single document checklist or approval time applicable to every new account was found, so there is no promise that sending a particular set of documents will guarantee approval. If you receive a request for additional documents, first use your official account to confirm that the request is genuine, how to submit them and what is necessary, then handle the individual case. Do not send identity documents to an old email address copied from an online article, or create false details or duplicate accounts to try to bypass verification.

Check the billing units and stopping conditions before creating resources

Cloudways Flexible billing depends on the servers and add-ons you use, with charges calculated and invoiced under the applicable rules. Before creating anything, record the provider, size, region, estimated cost and extra services. A monthly estimate does not promise that multiple environments will cost the same total amount, nor does it remove storage, transfer or other applicable extras.

The official billing documentation warns that stopping a server or leaving it unused may not stop charges; different infrastructure providers may retain resources such as disks and IP addresses. When ending a trial or removing an environment, save your data first, then follow the product's process to delete unused resources and disable paid add-ons, and check subsequent invoices. A website with no visitors is not evidence that it costs nothing.

Choose a server for the work your website needs to do

In the Flexible server-creation flow, choose the application, provider, specifications and location. Start with the essential features and current data volume of your site; there is no need to choose the largest size immediately. If most readers are in Taiwan, include candidate regions in your tests, but remember that distance is only one factor. A region's name alone cannot guarantee actual loading speed.

Give servers, applications and projects distinct names, for example separating a live portfolio site from a test site. This reduces the chance of changing or deleting the wrong environment later. If you already have a server, first check which sites it hosts and its resource status, then decide whether to put the new application there or create a separate environment.

Add WordPress to the correct server

According to the Cloudways documentation, to add an application to an existing Flexible server, open Servers, select the target server, then use Add App or the corresponding application-creation entry. Choose the WordPress type you need, enter an application name and project, and submit the request. If the platform warns that PHP or database requirements are not met, check compatibility first rather than immediately upgrading an environment that hosts other live sites.

After creation, open application management, review the access details and temporary URL, and confirm that the WordPress dashboard works. The hosting management account, application login and WordPress administrator are separate levels and should be stored separately. Also check the site's name, time zone, administrative email and content so that initial installation details do not become the live settings by default.

1. Confirm that the account is usable and that you are using Flexible, and record server and add-on billing terms.
2. Create a server or choose to add an application to an existing one; check the location, specifications and effect on other sites.
3. Choose WordPress, assign recognizable application and project names, and wait for the platform's creation result.
4. Use the application access details to check the temporary site and dashboard, then organize live content, accounts and backup arrangements.

Connect the live domain through Domain Management

Cloudways' launch documentation treats domain management and DNS configuration as separate steps. First add the name you intend to use in the application's Domain Management, then use the details supplied by the platform to configure records at the active DNS service. The domain registrar, DNS host and Cloudways may be different companies; confirm the correct management location before each change.

Save the existing records before making changes, especially email and service-verification records. Keep the intended use of the main domain, www and other subdomains consistent, then install a certificate covering the required names and check HTTPS. If the site connects but email or form notifications do not work, inspect the email service and the application's sending configuration separately. A page opening successfully does not mean every integration is complete.

Check the site before launch and plan how to leave

As a visitor who is not signed in, check the homepage, articles, navigation, search and contact flow, then review the main layouts on a phone. If you are migrating a site, also compare the old site's images, attachments and required URLs to ensure the new environment has not lost data. Keep a rollback plan and the original service until the main functions and the destinations of new data have been verified, then handle any shutdowns.

After launch, record the backup frequency, available restore points, who handles updates and who checks invoices. Even for a short test, schedule when to export data and remove resources so the test site does not stay in the account indefinitely. Platform management is complete only when you can explain which server hosts the site, who can restore it and how to end charges when you stop using it.

Read the full description

Building on Cloudways involves checking four levels in order: account, server, application and live domain.

Checking HTTPS on Cloudways: DNS, certificates and renewal

Shared hosting, VPS and managed cloud hosting: how to choose for a small site

• Tutorials
• Apps & software
• Websites & e-commerce
• WordPress