Build → deploy chain

How a Build project becomes a live Worker on your account.

#Frameworks

  • HTML — static pages with an inline Code | Preview tab.
  • Worker — Cloudflare Worker scripts; the Run button deploys a preview.
  • React — React apps with an inline live preview.
  • Astro / Next.js — on the roadmap (a CF Containers build pipeline); creating them is blocked server-side until it ships, so the UI can’t promise what the platform can’t do.

#What Deploy actually does

  1. The API decrypts your organisation’s Cloudflare token (requires the member role or higher).
  2. Your project files are bundled into a Worker script; the entry file is index.js, worker.js or the first JS/TS file.
  3. The script is uploaded with a PUT to accounts/<your-account>/workers/scripts/<name> — the worker name is deterministic: sstm-<org>-<project>.
  4. You get the live workers.dev URL back; the deploy is recorded with id, timestamp and status, and the worker name shows on the project card.

Previews resolve your account’s own workers.dev subdomain through the Cloudflare API — nothing is hosted on sSystm’s side.