Orchestral App Platform V0.5

V0.5 is a single-host developer preview. It accepts a Dockerfile-based App, builds and stores an OCI image, starts a resource-limited container, and returns a Tenant-owned subdomain URL. Node, Bun, and Python use the same contract.

An App contains Dockerfile and orchestral.yaml:

version: 1
name: invoice-review
category: operations
healthPath: /healthz

The App must listen on 0.0.0.0 using PORT; the platform supplies PORT=8080.

Run locally

Requirements: Node.js 22 or newer, npm, Docker Engine, and Docker BuildKit.

Start the pinned CNCF Distribution Registry 3 service:

docker compose up -d registry

Use one platform-process token and one token per Tenant. In three terminals, start the Control Plane, Build Worker, and Runtime Gateway:

ORCH_PLATFORM_TOKEN=replace-with-a-platform-token \
ORCH_TENANT_TOKENS='{"demo":"replace-with-a-tenant-token"}' \
PLATFORM_PUBLIC_PORT=8080 \
npm start

ORCH_CONTROL_PLANE_URL=http://127.0.0.1:3000 \
ORCH_PLATFORM_TOKEN=replace-with-a-platform-token \
ORCH_REGISTRY=127.0.0.1:5000 \
node src/build-worker.mjs

ORCH_CONTROL_PLANE_URL=http://127.0.0.1:3000 \
ORCH_PLATFORM_TOKEN=replace-with-a-platform-token \
PORT=8080 \
node src/runtime-gateway.mjs

Deploy and list Apps with the public CLI package:

ORCH_PLATFORM_URL=http://127.0.0.1:3000 \
ORCH_TOKEN=replace-with-a-tenant-token \
npm exec --yes --package=@digiveda/[email protected] -- orch deploy --dir . --subdomain invoice-review

ORCH_PLATFORM_URL=http://127.0.0.1:3000 \
ORCH_TOKEN=replace-with-a-tenant-token \
npm exec --yes --package=@digiveda/[email protected] -- orch apps

Codex skill

Copy or link skills/orch-app into a Codex skills directory, then ask Codex: “Use $orch-app to deploy this App as invoice-review.” The skill reads ORCH_PLATFORM_URL and ORCH_TOKEN from the environment.

Verify

npm run check
npm test
npm run test:integration

The Docker acceptance test starts an isolated local Registry and deploys Node, Bun, and Python examples through the real CLI-to-hostname path.

Boundary

V0.5 has no central Git service, managed secrets or databases, persistent App volumes, stages, rollback command, browser Catalog, custom-domain automation, or production-grade isolation. Registry TLS and authentication are required before moving its traffic across hosts.