Skip to main content
Click Compute in the rail. This is where contracts become machines. The Compute page

​
What the page shows

  • Free Capacity has one tile per contract you hold for the month shown, with the GPU Contract it pairs with and the Available Contracts: held, less any in a resting sell or already deployed. Step through months with the arrows, or switch Month to Year to see every month at once.
  • Balance on the right lists every contract you hold. Filter it to BASIS or GPU.
  • Active Capacity at the bottom is your deployments: the BASIS and GPU contracts, identifier, region, GPUs, term and Status.
Free Capacity by year

​
What you need

A deployment pairs a provider’s BASIS contract with the GPU contract for the same GPU and month, one for one. To deploy 8 GPUs of BBA-10-26 you need 8 free BBA-10-26 and 8 free H100SXM-10-26. Buy the BASIS on Offtake and the GPU contract on the markets, or the other way round. Only the current month deploys. Later months show on the page but their tiles wait.

​
Add a deployment

  1. Click Activate on a tile, or Add Deployment in Active Capacity.
  2. Check the BASIS Contract, its Identifier, Region and Term, and how many Free BASIS contracts and Free GPU contracts you have.
  3. Enter GPUs to deploy, up to the Max shown.
  4. Click Continue, then confirm.
Add Deployment The deployment appears in Active Capacity as requested. From here the contracts are locked: they stay yours, but can’t be sold until the deployment ends.

​
What happens next

​
Stop a deployment

Click Stop on the row. You can stop all of its GPUs or some of them; stopping some splits them into their own row so ops tears down exactly those machines. A deployment that ops hasn’t claimed yet ends at once; a running one shows ending until it is torn down. At the end of the month every deployment ends and its contracts are released. The contracts stay yours: a deployment locks them, it does not use them up. From code: Deployments.