How to set up Cloudways for managing multiple websites

Follow this tutorial and you will have Cloudways Autonomous configured with a deliberate server architecture, named applications, scoped team access, and tiered backup schedules — ready to manage between five and fifty websites without operational chaos.

Before You Start

This tutorial assumes you are setting up Cloudways Autonomous as a managed hosting layer for multiple client or project sites. If you only need a single personal site, this workflow is more structure than you need.

Expected Outcome

By the end of this tutorial your Cloudways Autonomous account will be in the following state:

Explore Cloudways Through Our Partner Link

• At least one server provisioned with a deliberate naming convention tied to client group or traffic tier
• Each website running as a separately named application, with staging and live environments clearly distinguished
• Team members added with access scoped to the specific applications they manage, not the full account
• Per-application backup schedules set according to client criticality — not a single blanket schedule across every site
• A documented threshold checklist in place to signal when a second server is warranted
• Domains pointed to the correct application with SSL provisioned

That combination — structured naming, isolated access, tiered backups, and a clear split-server trigger — is the operational foundation that scales from five sites to fifty without requiring a full audit every time you onboard a new client.

Getting Started: The First Three Setup Steps That Shape Everything Else

Most tutorials about how to set up Cloudways for managing multiple websites jump straight to "click Add Application." That skips the decisions that actually determine whether your setup stays manageable at 20 sites or turns into a support headache. These first three steps are where the operational architecture gets made or broken.

Step 1: Plan Your Server Structure Before You Provision Anything

The most consequential early decision is whether all your sites share one server or live across multiple. Cloudways Autonomous lets you host several applications on a single server, which keeps costs consolidated — but consolidation is a risk multiplier when a single misbehaving application can affect everything else running alongside it.

A practical starting point: group sites by client risk profile, not just by traffic. Review the provider's current service commitments and SLA terms before relying on them for a critical workflow. Sites with unpredictable traffic spikes — seasonal campaigns, event registrations — are also poor candidates for shared hosting alongside revenue-critical applications.

Step 2: Establish a Naming Convention Immediately

Getting started with Cloudways is fast — arguably too fast to force a naming pause. Resist the momentum. Application names, server labels, and staging environments created without a consistent convention become opaque within weeks. A practical format: [client-abbreviation]-[site-type]-[environment], for example acme-main-live or acme-main-staging. This structure surfaces intent at a glance and makes bulk operations — backups, access reviews, migrations — far less error-prone.

Step 3: Configure Application-Level Backups Before Going Live

How to use Cloudways backup settings correctly is not obvious from the default configuration. Cloudways Autonomous provides backup controls at the application level, which means you can tier backup frequency by client priority. Set mission-critical applications to the most frequent available schedule; lower-priority sites can use a less frequent cycle to manage storage costs. Verify each application's backup status individually — do not assume a server-level setting covers all applications beneath it.

Steps 4 to 6: Team Access, Backup Tiers, and Knowing When to Split Servers

With your applications running and domains pointed, the operational layer becomes the priority. These three steps address the governance decisions that most platform walkthroughs skip entirely — and where multi-site management either holds together or quietly falls apart.

Step 4: Scope Team Member Access Per Site

Cloudways Autonomous lets you invite team members and assign roles at the account level. A developer working on one client's site has no reason to touch another client's environment, and mixing access is one of the most common sources of accidental configuration changes in shared dashboards.

See How Cloudways Fits Your Workflow

Before you send any invitations, map out a simple access matrix: list each team member, the sites they actively work on, and the minimum permission level that lets them do their job without touching billing or server-level settings.

Step 5: Configure Per-Application Backup Schedules Tiered by Priority

Not every site on your account carries equal risk. A high-traffic client store warrants more frequent backups than an internal staging environment. Build a three-tier backup policy before you configure anything:

• Critical: Daily backups with the longest retention your plan supports — revenue-generating or client-contractual sites
• Standard: Daily or every-other-day backups — active but lower-stakes sites
• Low priority: Weekly backups — staging environments and internal tools

Apply this policy consistently at the application level rather than the server level, so adding a new site forces a deliberate classification decision rather than inheriting a default you set months ago.

Step 6: Decide Whether to Split to a Second Server

Consolidation is convenient until it becomes a liability. Consider moving sites to a second server when any of these conditions appear:

• One application's traffic spikes are visibly degrading response times for others on the same server
• Your backup or deployment window for one site conflicts with another site's peak hours
• A security incident on one application creates unacceptable blast radius for unrelated clients

Troubleshooting Common Setup Problems When Managing Multiple Websites on Cloudways Autonomous

Even a well-planned multi-site setup on Cloudways Autonomous will surface friction points during initial configuration. The issues below are the ones teams encounter most often, along with the validation checks that confirm you have actually resolved them rather than masked them.

SSL Provisioning Failures

Let's Encrypt certificates require that your domain's DNS A record is fully propagated and pointing to your application's IP before you attempt provisioning. If you trigger SSL before propagation completes, the validation request fails silently in some dashboard states. Fix: confirm the A record resolves correctly from at least two external DNS lookup tools before returning to the SSL tab. Re-initiating the process after verified propagation resolves the majority of Let's Encrypt failures on this platform.

Wrong Application Selected During Domain Attachment

With many applications on a plan, it is easy to attach a domain to the wrong app — especially when application names have not followed a consistent naming convention. Do not rely solely on the dashboard confirmation message.

Staging Environment Receiving Live Traffic

If a staging application was cloned from a live app and the domain was not cleared from the staging instance, crawlers and users can reach it. Audit every staging application to confirm no production domain is attached. Set a staging-specific subdomain and password-protect the staging environment to eliminate the risk entirely.

Backup Jobs Not Running on Expected Schedule

Per-application backup schedules must be set individually; a server-level default does not cascade automatically to every application on that server. If a backup job shows no recent completion timestamp, verify the schedule was explicitly saved on that specific application's settings panel — not inherited from another app you configured earlier in the session.

Team Member Access Wider Than Intended

Access roles assigned at server level grant visibility across every application on that server. If a team member should see only a subset of client sites, those sites must live on a server where that member holds no server-level role. Confirm intended scope by logging in under the team member's credentials in a separate browser session before considering the governance setup complete.

Did It Work? Go-Live Checklist for Multi-Site Cloudways Autonomous Setups

Did It Work? Binary Checks

Run through these objective pass/fail items before treating any site as production-ready. Each check should return a clear yes or it needs attention — no guesswork.

• Each application resolves correctly at its assigned domain without redirecting to a Cloudways default page or an adjacent app.
• SSL is active and the browser shows a valid certificate for every domain — not just the primary one.
• Staging and live applications are named distinctly in the dashboard so no team member could confuse them under time pressure.
• Backup schedules reflect client priority tiers: high-value or transactional sites back up more frequently than low-traffic brochure sites.
• Every team member account is scoped to the applications they actually manage — no unnecessary cross-client access exists.
• Autoscaling is confirmed active on all applications, not just the one provisioned during initial setup.
• Cloudflare Enterprise CDN (included on Growth and above) is connected and propagating for each live domain.

Ready to Go Live?

Binary checks tell you the platform is configured. These subjective criteria tell you the operation is ready.

• You have a documented threshold — even an informal one — for when a site moves to its own isolated server rather than sharing resources.
• At least one team member other than the account owner can locate, clone, and restore any application without asking for guidance.
• You have reviewed which plan tier covers your aggregate bandwidth and disk needs across all active sites, not just the heaviest single site.
• Evaluate the workflow benefit against your own baseline rather than assuming a specific measured outcome.

If any of the readiness criteria above is uncertain, work through it before directing client traffic. The platform supports all of it; the setup discipline is your team's contribution.

Check Cloudways Fit and Current Options

Frequently Asked Questions

Current plans and pricing: Use our partner link to view current plans, pricing, and any available offers. Final pricing and promotional terms are set by the provider and may vary by plan, billing cycle, usage, region, and eligibility.