Skip to main content
A deployment turns contracts into machines: gpus of a BASIS contract paired with gpus of the GPU contract for the same GPU and month. While it is open both sets of contracts are locked: they can’t be sold. Ops claims the request, and the machines are provisioned on Northflank, our hosting partner: a JupyterLab notebook on CUDA by default, or a public image you name, with the ports you ask to reach. Their addresses appear on the deployment once it is running. Where Northflank cannot run the configuration, ops provisions by hand and sends access by email. Only the current month can be deployed. Later months trade but wait for their month.

Request a deployment

POST /api/v1/compute/deployments · scope trade
200 with the deployment:
url is the first HTTP port’s address and each port gains its url once the deployment is active. northflank names the project and service for the Northflank CLI once you are a member of the project. Refusals are 400 with a code and the field it concerns: 503 when the exchange is unreachable.

Status

Ending a deployment releases its contracts; it does not consume them. They stay in your account and can be sold or deployed again while their month lasts. Deployments that are ending, or whose month is over, are torn down by a job that runs every ten minutes. ops_note carries anything ops wrote for you, such as how access was sent.

Stop a deployment

POST /api/v1/compute/deployments/{id}/end · scope trade Stops all of the deployment’s GPUs, or gpus of them.
200 with the deployment of the GPUs stopped. Stopping some of them splits those GPUs into a deployment of their own, with parent_id pointing at the one that keeps the rest, so ops tears down exactly those machines.
  • A requested deployment ends at once (ended): nothing was provisioned.
  • A claimed one goes to ending until ops has torn it down.

List your deployments

GET /api/v1/compute/deployments is what the Compute page’s Active Capacity table reads. It is session-only today and is coming to the API.