SiteLaunch docs.
Practical notes for creating, editing, deploying, and maintaining a hosted site.
1. Create your first site
Open your dashboard and select New site. Choose a display name and a unique subdomain slug. SiteLaunch creates a starter index.html for you.
The slug is part of the public address, so avoid personal information. Use lowercase letters, numbers, and hyphens.
2. Edit and publish
Open Studio from your site card. Create or upload HTML, CSS, JavaScript, image, and other static files. Relative links work well when files are kept in the same site.
Keep a main index.html. Save and publish when ready. Replacing an existing live file may require explicit confirmation, and eligible plans can use deployment history to roll back.
3. Understand quotas
Limits can apply to the number of sites, the number of files per site, the size of a single file, and total storage. The server checks these limits when files are written; refreshing the page will not bypass them.
Compare plan capabilities →4. Add a custom domain
Open Project settings, add a hostname you control, create the displayed CNAME record at your DNS provider, then select Check status & SSL. SiteLaunch uses Cloudflare for SaaS to provision the custom hostname and manage its TLS certificate. Both the hostname and certificate must report active before the site is served on that hostname.
The SiteLaunch platform owner must first enable Cloudflare for SaaS on the provider zone, configure its fallback origin and Worker route, then set the Worker secret CF_API_TOKEN and variable CF_SAAS_ZONE_ID. Apex/root domains depend on support for CNAME flattening or Cloudflare for SaaS apex proxying.
5. Read error codes
400 invalid input · 401 sign-in required · 403 access denied · 404 resource missing · 409 conflict · 413 limit exceeded · 429 rate limited · 5xx server or upstream issue.
Use the copy-diagnostics control on an error page when asking support for help. It copies a request ID, status code, method, and address—not your password or file contents.