How-to · operate a deployment

Operate Up

Keep each capability explicit and the trust boundary intact.

Update a site

Publish the same site name. Up activates the replacement only after every asset passes verification.

Change visibility

Open Manage beside a site. Choose company, restricted readers, or public. Public is never inferred and always requires explicit confirmation during first publish.

Add a backend

Build static files into ./dist.
Add ./dist/_worker.js for /api/* routes.
Keep secrets out of browser code.
Publish the folder through Up.

After publishing, Manage can enable SQLite, write secret capabilities, and create bounded schedules.

Respond to exposure

Set the site to company/restricted or disable its schedules first. Never expose the control Worker, private R2 bucket, or runtime keys.