Deployments

Compute deployment endpoints — current status and Scalix Run equivalents

To run container workloads, deploy them as a Scalix Run service — that is the supported execution path.

Status: not available yet

The /v1/compute/deployments endpoints (create, list, get, scale, restart, rollback, delete, instances, logs, versions) are kept for API compatibility but have no scheduler behind them. Every call currently returns HTTP 501 — no deployment is created, stored, or run:

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
}

The CLI's scalix-cloud logs <deployment-id> command targets this surface and reports the same unavailability.

Do it with Scalix Run instead

Task	Command
Deploy	`scalix-cloud run deploy --name api-server --image api.scalix.world/<project-id>/api:v1.2 --port 8080`
List services	`scalix-cloud run list`
Scale	`scalix-cloud run scale <service-id> --min-instances 1 --max-instances 10`
Environment variables	`scalix-cloud run deploy ... --env KEY=VALUE` (repeatable)
Logs	`scalix-cloud run logs <service-id>`
Roll back	`scalix-cloud run rollback <service-id>`
Delete	`scalix-cloud run delete <service-id>`

See Scalix Run for the full workflow, or the Compute API reference for the live /v1/run/services REST endpoints.