Deploying

Upload a folder or zip

No repo needed. Drop a folder or zip from the dashboard, or push your working directory with the CLI, and Orizon detects the stack from the actual files.

From the CLI

orizon deploy zips your current directory (skipping node_modules, .git, and build output), uploads it, creates a deployment, and streams the logs:

shell

cd my-app
orizon link --project proj_123
orizon deploy

From the dashboard

In the create or deploy flow, choose to upload a folder or a zip archive. Orizon extracts the archive, runs stack detection on the real files, and shows a configure step where you can confirm or adjust the detected build before it ships.

Not always staticUploads aren't assumed to be static sites. Orizon detects the real framework on the extracted files — including PHP — so an uploaded Node or PHP app builds and runs as a server, not as flat files.

What gets detected

The same detection used for repos runs on uploads: a Dockerfile or docker-compose.yml, Next.js, Go, Rust, PHP, Python, a Procfile, or a lone index.html for a static site. See Supported stacks.

Over the API

Upload a source archive to POST /uploads to get a sourceTarballUrl, then pass it when creating a deployment. This is exactly what the CLI does under the hood — see the Public API.

PHP & WordPress

How PHP apps are detected and served.

CLI

Deploy your working directory from the terminal.