Compute

Container workloads on Scalix Cloud — run them on Scalix Run

Overview

Run your containers and long-running services on Scalix Run — deploy a container image, get autoscaling, health checks, revisions, and zero-downtime rollouts. Run is the supported path for executing container workloads today.

The separate /v1/compute/deployments API is a legacy surface kept for API compatibility and is not available yet — see Compute API status below.

Deploy a service (Scalix Run)

Deployments build from a container image in the registry (push with scalix-cloud builds, or bring your own image):

bash

scalix-cloud run deploy \
  --name api-server \
  --image api.scalix.world/<project-id>/api:v1.2 \
  --port 8080 \
  --min-instances 1 \
  --max-instances 10

See Scalix Run for the full deploy, scale, and rollback workflow.

Compute API status

The /v1/compute/deployments endpoints have no scheduler behind them — they do not create, store, or run anything today. Every request to this surface, regardless of method or authentication, currently returns HTTP 501:

json

{
  "error": "Compute deployments are coming soon and not available yet. To run containers today, use Scalix Run (/v1/services) or Functions (/v1/functions).",
  "code": "COMPUTE_COMING_SOON",
  "coming_soon": true
}

To run containers, use Scalix Run. For event-driven code, use Functions. The endpoint surface is listed in the Compute API reference so integrations can prepare for it, but nothing executes behind it yet.

Supported Runtimes (Scalix Run builds)

Images are built from your repository, with the runtime auto-detected:

Runtime	Auto-detected From
Node.js	`package.json`
Python	`requirements.txt`, `pyproject.toml`
Go	`go.mod`
Rust	`Cargo.toml`
Docker	`Dockerfile`

Rollouts and rollback (Scalix Run)

bash

# View services
scalix-cloud run list
 
# Roll back to the previous revision
scalix-cloud run rollback <service-id>