Create a new project on Swigs Cloud and put it online over HTTPS, hosted in Switzerland. Two ways to provide the code, use exactly one: repo for a public git repository, or directory to send a folder from this machine (defaults to the current folder). Static sites (plain HTML, Vite, React, Vue, Angular, Svelte) and Node apps are detected automatically; a site exported from Lovable, v0 or Bolt deploys as is, with no build configuration. The project name becomes the subdomain unless slug says otherwise. Returns immediately with the final URL: the build then takes one to two minutes, poll project_status to know when it is live. To change a site you already deployed, use update_site — calling deploy again would create a second project and use up another slot of the quota.

Replace the content of a project you already deployed and build the new version. The address does not change and no new project is created, so it does not use up a slot of your quota. Prefer it over calling deploy again whenever you are changing an existing site. Files missing from the folder are removed from the site.

List your Swigs Cloud projects: name, state, address and identifier.

State of one project. running means the site is live, failed means the build did not succeed — call logs to see why. Any other state means the build is still working.

Build log of the latest deployment. Call it when project_status reports failed.

Build and deploy the project again from its current source. Use it after fixing something in the repository, or to retry a failed build. The address does not change.

Set or remove environment variables on a project, then redeploy so they take effect. Variables you do not mention are kept; an empty value removes one. Never returns the values, only the names.

Permanently delete a project: the site goes offline, its address is released and its data is destroyed. This cannot be undone. Ask the user to confirm before calling it.