Skip to content

Publish with Swebsy Hosting

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.

Publish free on yourname.swebsy.site; custom domains are paid. A free account with a verified email can publish one site with SSL — no card and no trial. Paid plans add more sites, custom domains, hosted forms, and badge removal.

Compared with the other targets:

Swebsy Hosting GitHub Pages Cloudflare Pages
Setup Sign in, click Publish 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 Paid plans and trial Not available Not available
  1. Click Publish at the right of the topbar. The menu shows the address your site will get and whether it is live.

  2. Click Publish in the menu. Signed out, you create a free account and verify your email next, and the publish carries on by itself.

The Publish menu open in the Swebsy top bar, showing the site's swebsy.site address as not live yet and a Publish button.
The Publish menu shows where the site goes and whether it is live.

There is no naming step. The first publish picks a readable address for you: your site’s title (rosa-bakery), or your account’s name (sam-rivera) while the site still carries a template’s sample title. If that address is taken, it uses a close one such as samrivera or sam-rivera-site. On your first site, a template’s sample business name is replaced with your account’s name in the published page titles; a title you wrote yourself is never changed. The live screen says what it picked, with Change address and Rename.

Every publish to Swebsy Hosting is one step — from the Publish menu, from Publish update in Settings, or from Try again after a failed publish. If a publish has something worth a look, such as a warning about the site’s files, the Deploy review opens first to show it.

After you download your site as a ZIP, Swebsy offers to put it online too. Not now hides that offer for the site for a week.

Right after the first publish, nobody has the link yet, so changing it costs nothing: on the live screen, click Change address, type the address you want (it is checked as you type, and free ones close to a taken address are offered), and click Save. The site republishes at the new address while the screen stays open. If that publish fails, the site stays at its old address and the screen says why.

Later, change it from Settings:

The Deployment tab of Site Settings offering three cards: Swebsy Hosting, tagged Popular, GitHub Pages, and Cloudflare Pages.
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. Next to the Swebsy address under Domains, click Edit (or Choose).

  4. Type the address you want. Your name or business works best, like sam-rivera. It is checked as you type.

  5. Click Save address.
Swebsy Hosting settings, with the site's swebsy.site address under Domains.
Swebsy Hosting settings hold the site's address, its published versions, and the custom domain section.

Changing the address of a site that has been published asks you to confirm first, naming both addresses: links to the old address stop working, and someone else can take it. A live site moves straight away — the confirm button is Change address and publish. An offline site moves at your next publish. If the address you type is taken, free ones close to it are offered under the field.

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.

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

A site published on the Free plan follows a few extra rules, mostly to keep swebsy.site safe from phishing for everyone:

  • The “Made with Swebsy” badge stays on. It can’t be removed, and a publish without it is refused. Badge removal comes with a paid plan.
  • No password fields. A page containing <input type="password"> is refused.
  • 20 publishes a day per account. The Pro trial has the same limit.
  • No form submissions. A form on a Free site does not accept submissions; hosted forms are paid.

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.

Free accounts can write 100 MB a day to the cloud, shared by publishes and cloud backups. The allowance resets at midnight UTC. When you reach it, Publish says when you can publish again, and a site that is already live stays online.

Republishing reuses files that haven’t changed since the last version, so only your edits are uploaded. A reused file counts a tenth of its size toward the daily allowance.

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.

On the Free plan you can roll back only to versions that were published on the Free plan. A version published while you were on a paid plan or trial can’t be rolled back to — republish the site instead.

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. The Publish menu reads Offline · this address is still yours, and Publish puts the site back up at that address. Those retained versions continue to count toward storage; unpublishing does not reclaim their bytes.

Once a site is published, use the Custom domain panel below the deployment list to serve it from a hostname you own. Custom domains are paid (Starter, Pro, or the Pro trial). See Custom domains.

Common issues

Publish → Swebsy Hosting asks you to sign in — you are signed out. Create a free account (or sign in) and verify your email; the publish carries on afterwards.

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

“That address is taken” — someone else is using it. Addresses are first come, first served across all Swebsy accounts; pick one of the free ones offered next to it. An address Swebsy picked for you is simply picked again.

Publishing refused with a plan message — you are at your plan’s published-site limit (1 on Free), 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.

Free site refused: badge or password field — a page is missing the “Made with Swebsy” badge, or contains a password field. The message names the file; restore the badge or remove the password field, then publish again.

Free publish limit reached — Free and trial accounts can publish 20 times a day. Try again tomorrow.

“You can publish again today (or tomorrow) at …” — a Free account has written its 100 MB to the cloud for the day. It resets at midnight UTC; your live site stays online meanwhile.

Roll back refused on the Free plan — that version was published on a paid plan or trial. Republish the site instead.

Site went offline on its own — if your subscription ended, the account moves to the Free plan when the 30-day grace period closes: your newest site that meets the Free rules (badge on, no password fields) stays live on its swebsy.site address, custom domains stop working, and other sites go offline. The deployments are retained; resubscribe and republish from Previous versions.