Create a Site

Use Create Site to create a new hosted workload under a new Control Site identity.

Choose the runtime

Select PHP, Node.js, Python, Static, Reverse Proxy, Docker or Docker Compose according to the workload. The form shows only options supported by the components available on the host.

Quick Install and applications

Choose a ready-made application from Quick Install, or start from Applications → Install Application. Curated applications, private recipes and Custom Image workloads still create ordinary Sites and remain inside the normal Site lifecycle.

Some applications ask for setup values such as an administrator email, password, Site name or timezone. Required fields must be completed before the plan can be created. Control protects password and token fields during setup.

Ingress binding

• Shared uses normal hostname-based routing on the host.
• Specific IP binds the Site to a selected host address.
• Dedicated IP · Catch-all reserves an address for one hostname-routing Site, such as a Micro CMS Bridge host serving externally managed domains.

Add additional public addresses under Server → Host Networking before selecting them for Site ingress.

Database and cache

Eligible PHP, Node.js and Python Sites can create Site-owned data at creation time or later. Where offered, choose SQLite for a Site data file or Site-owned MariaDB for a separate database service dedicated to that Site. Independent managed MariaDB/PostgreSQL databases can also be created under Server → Databases and attached to eligible Sites.

Redis can use a Site-owned service or the legacy shared Redis attachment. Choose the hosting mode before attaching a new cache; an existing cache is not moved automatically just because the setting changes.

HTTPS

Site creation establishes the workload and HTTP ingress first. Enable managed HTTPS after DNS is ready, or attach a suitable shared/imported certificate. Certificate failure does not require recreating the Site.

Primary and www hostnames

For an apex hostname, Control can attach the conventional www. companion and later set the preferred hostname. A subdomain does not automatically gain a www. variant.

Review before creating

Review the hostname, runtime, ingress, storage/data choices and HTTPS intent before submitting the plan. Creation continues on the server if you close the browser.