Skip to main content

Deploy from the console

The console is the quickest way to deploy if you have a folder and a browser.

Create a project​

  1. Open the console and select Projects in the sidebar, then New project.
  2. Enter a project name, such as q3-variance. It becomes the address q3-variance.apps.<domain>. Names are 3 to 40 lowercase letters, digits and dashes, starting with a letter.
  3. Drop a project folder on the drop zone. Vite / React, Node, Python, a Dockerfile, or plain HTML all work. The console reads the folder locally and shows what it detected; node_modules, .git, dist and .env files are skipped.
  4. Select Deploy. Status streams live while the deployment is queued, building and deploying. When it's ready the project's Overview opens with the production URL and the preview URL.
tip

The same page shows Or deploy from your tools with a ready-to-copy CLI command and the MCP setup for Claude Code, already pointing at your installation.

Deploy a new version​

On the project's Overview, use Deploy a new version and drop the folder again. Production switches once the new build is healthy. To build without switching production, use the CLI with --preview.

Watch it​

  • Deployments lists every deployment with its status, kind (for example vite-static or node), preview URL, and Promote / Roll back actions.
  • Logs shows the build output and the runtime output of the selected deployment.

Who can deploy​

  • Creating a project needs the Builder Hub role (everyone, unless your admin restricted it).
  • Deploying to an existing project needs to be its owner, have the developer app role on it, or be an Org Admin or a Delegated Admin whose scope covers the owner. Auditors can view but not deploy.
  • If your organization's licence has expired past its grace period, new projects and deploys are paused; running apps keep serving.
Was this page helpful?