Publish with Swebsy Hosting

Before you start

• A Swebsy account on a paid plan or active trial

• The site saved to the cloud

Swebsy Hosting publishes your site to yourname.swebsy.site in one click. Unlike GitHub Pages or Cloudflare Pages, there is no third-party account to create and no API token to paste — SSL, the CDN, forms, custom domains, and rollback are handled for you in Swebsy.

Why we recommend it (the honest version)

It is the shortest route from the editor to a live site: pick a name and publish. Also, full disclosure, paid Swebsy Hosting helps fund Swebsy. Fewer setup steps for you and revenue for us — a suspiciously convenient arrangement for everyone.

Compared with the other targets:

	Swebsy Hosting	GitHub Pages	Cloudflare Pages
Setup	Sign in, save to cloud, pick a name	GitHub repo + token	Cloudflare project + account ID + token
Management	Entirely inside Swebsy	GitHub and Swebsy	Cloudflare and Swebsy
Rollback	Built in, one click	Through git history	Through Cloudflare
Custom domain	Built in	Configure with GitHub and your DNS	Configure with Cloudflare and your DNS
Swebsy Forms inbox	Included	Not available	Not available

Pick your address

The Deployment tab is where you pick a host. Once you have, the cards collapse to a single row and Change brings them back.

1. Click Settings in the topbar, then open the Deployment tab.

2. Select Swebsy Hosting as the deployment provider. If this site already publishes somewhere else, click Change on the provider row first.

3. Type the subdomain you want, or click use a suggestion from your site title.

4. Click Check.

Choosing Swebsy Hosting reveals the subdomain field, Publish now, and the custom domain section.

Expected result

“yourname.swebsy.site is available — saved”. The choice is stored with the site; you do not need to save separately.

Subdomains are 3–63 characters, lowercase letters, numbers, and inner hyphens. A short list of names is reserved (things like www, api, admin, support, and swebsy itself) to keep published sites from impersonating Swebsy infrastructure.

Publish

1. Click Publish now in the Deployment tab, or close Settings and choose Deploy → Deploy to Swebsy Hosting from the topbar.

2. The Deploy review modal opens, showing what will be uploaded.
3. Click Deploy now.

Once Swebsy Hosting is configured, publishing is always available from the Deploy menu.

Check the destination and generated site before clicking Deploy now.

Expected result

A green Live tag with your URL, an Open link, and a Copy link button. The publish button becomes Publish update for subsequent releases.

Published sites count against your plan: 3 on Starter, 10 on Pro, 1 during the trial. Published files also count toward your storage limit — see Plans & billing.

A published site may contain up to 500 files, each up to 10 MB. Only web file types are accepted: HTML, CSS, JavaScript, images, fonts, common audio and video, PDF, and the usual metadata files. Archives and executables are rejected.

Roll back to a previous version

The three most recent deployments are retained. Earlier ones appear under Previous versions with the time they were published and their file count.

1. Find the version you want under Previous versions.
2. Click Roll back, then confirm.

The live site switches immediately, and the version you rolled away from stays in the list so you can roll forward again. Nothing is re-uploaded — the files are already there, which is why this is instant.

Rollback is separate from version history

Rollback swaps which published build is being served. It does not change the project you are editing. To take the editable project back to an earlier state, use version history instead.

Take a site offline

Click Unpublish, then confirm. Visitors see a “site offline” page.

Your deployments are kept and your subdomain stays reserved to you, so republishing later is one click from Previous versions — no re-upload and nobody can take the name in the meantime. Those retained versions continue to count toward storage; unpublishing does not reclaim their bytes.

Your own domain

Once a site is published, use the Custom domain panel below the deployment list to serve it from a hostname you own. See Custom domains.

Common issues

“Sign in to publish with Swebsy Hosting” — sign in from the Swebsy home page, then reopen Settings.

“Save this site to the cloud first” — Swebsy Hosting publishes your cloud copy. Click Save to Cloud in the Studio topbar, then come back.

Publish button is disabled — pick and check a subdomain first.

“This subdomain is already taken” — someone else is using it. Names are first come, first served across all Swebsy accounts.

Publishing refused with a plan message — you are at your plan’s published-site limit, or storage is full. Unpublishing another site can free a published-site slot, but retained deployments still count toward storage; remove unused project assets or upgrade to free capacity.

Site went offline on its own — if your subscription ended, published sites go offline when the 30-day grace period closes. The deployments are retained; resubscribe and republish from Previous versions.