Deploying

ccp deploy bundles your code, uploads it, and activates a deployment on Cluster's serverless runtime.

Deploy to Production

ccp deploy --prod
# ◼ Building Function...
# ◼ Creating Deployment...
# ◼ Uploading code...
# ◼ Deploying...
# ◼ my-app deployed!
# › https://my-app.clusterbase.dev

The --prod flag (alias: --production) makes this the active production deployment, served at https://{function-name}.clusterbase.dev.

Preview Deployments

Without --prod, you get a preview deployment with its own URL:

ccp deploy
# ◼ my-app deployed!
# › https://abc123.clusterbase.dev

Preview deployments are useful for testing changes before promoting to production.

Promote a Preview

Promote any preview deployment to production:

ccp promote <deployment-id>

This swaps the production deployment to the given deployment ID without redeploying.

Undeploy

Remove a specific deployment:

ccp undeploy <deployment-id>

List Deployments

ccp list        # or: ccp ls

Inside a linked project, shows all deployments for that function with their IDs, status, and timestamps.

Run outside a project (or in one that hasn't been deployed yet) and ccp ls instead lists every function in the organization — resolve the org with --org-id, the project config, or the interactive picker. See Functions → Managing Functions.

Deploy Options

How It Works

1. Bundle — your TypeScript/JavaScript is compiled into a single ESM bundle
2. Upload — the bundle (and any assets) are uploaded to Cluster's storage
3. Activate — Cluster publishes the new deployment to the runtime
4. Route — routes are created for {function-name}.clusterbase.dev and {deployment-id}.clusterbase.dev
5. Serve — the serverless runtime creates a V8 isolate and starts handling requests

First Deploy

On your first deploy, if .cluster/config.json doesn't have a function_id, CCP resolves one for you:

• Interactive: you're prompted to select an organization, then link an existing function or create a new one.
• Headless (no TTY or --yes): CCP auto-creates and links a new function named after your project (its package.json name, else the directory), with no prompts. A single-org account needs no flags; with multiple orgs pass --org-id (otherwise it errors listing them).

Either way the function ID is saved to .cluster/config.json for future deploys.

Build Without Deploying

To test the build step without deploying:

ccp build

This runs the bundler and reports any errors, but doesn't upload or activate anything.

Headless / CI Deploys

For CI pipelines and AI agents, set CCP_HEADLESS=1 and deploy never blocks on a prompt. On a single-org account, the first deploy needs no flags at all — it auto-creates the function:

export CCP_HEADLESS=1
ccp deploy --prod

With multiple organizations, name the target so CCP doesn't have to guess:

ccp deploy --prod --org-id "$ORG_ID"

To deploy to a pre-existing function (skip creation entirely), pass both ids:

ccp deploy --prod --org-id "$ORG_ID" --function-id "$FUNCTION_ID"

After the first deploy the IDs are written to .cluster/config.json; commit it to your repo and subsequent deploys reuse it with no flags. ccp link --org-id <id> --function-id <id> seeds that config without uploading code, when you want to link separately from the first deploy.

See Headless Mode for the full reference.