Sites

Create and manage hosted Sites, their domains, runtime, TLS, data and lifecycle.

A Site is the lifecycle boundary for a hosted workload. Its Control identity stays stable even when its primary hostname changes.

In this section

Create a SiteCreate a Site with the appropriate runtime, ingress, data and HTTPS policy.Domains and hostnamesAttach hostnames to a Site and understand the difference between Site identity, DNS and TLS.Site settingsChange Site identity, traffic, PHP, cache, resilience, WAF and redirect settings.TLS and certificatesIssue, import, reuse and attach TLS certificates to managed Sites.Storage and FilesBrowse and manage Site files, including resumable uploads, bulk actions and safe replacement.SFTP accessUse public-key SFTP with FileZilla or another SSH-capable client.Runtime migrationMove a Site to another installed supported runtime version using only choices Control has detected.Clone, export and import SitesMove a Control-managed Site using Control-native clone and encrypted Site export workflows.Site lifecycle and deletionUnderstand Site deletion, recovery and archived Site history.

Sites list

The Sites list separates workload state, runtime/application identity, TLS, storage, CPU/RAM and health so an issue in one area does not hide the others.

Runtime labels use a compact runtime · application form when Control knows the application, for example PHP 8.4 · WordPress or Docker · n8n.

Site workspace

Open a Site to manage hostnames, HTTPS, runtime settings, storage, databases and cache, SFTP, deployments, automation, performance and lifecycle actions.

Activity keeps historical operations. The Site headline reflects current observed workload health rather than preserving an older failure after the workload has recovered.

Hostnames

A Site can own its primary hostname and additional hostnames. For an apex Site, Control can manage the conventional www. companion and let you choose the preferred hostname without recreating the Site.

Changing the primary domain does not change the Site identity. DNS, certificate coverage and application configuration still need to be valid for the new hostname.

Delete a Site

Delete Site removes resources owned by that Site. You do not need to dismantle applications, jobs, mail or data attachments first.

Site-owned applications/private data, managed database attachments, Site backup schedules, Site-owned Mail Domains and their mailboxes/aliases/managed DNS, scheduled jobs, background workers, Site-owned tunnel routes, SFTP access, runtime configuration and Site files are removed as part of the Site lifecycle. Shared host-level resources are not deleted behind another Site's back.

Cloudflare Tunnel

If a Host tunnel is connected, a running Site can publish its hostname through the tunnel from the Site or Connectivity workspace. Public DNS and Access policy remain visible operator choices.