Developers
Start here
Sign up, get a key, run one command. The full reference lives in the docs site; this is the shortest path from zero to a running GPU.
Quickstart
Zero to GPU
Create an account
A company email and a payment method. Verification is automatic for most domains; regulated sectors get a short KYC step instead.
Issue an API key
Scoped to a project and a role. Keys can be rotated, expired and audited from the console or the API.
Launch a pod
One command with a GPU type, a count and an image. SSH details and a Jupyter URL come back in the response.
-H "Authorization: Bearer $MSL_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"gpu": "l40s",
"count": 1,
"image": "msl/vllm:0.6",
"region": "pnq1",
"idle_timeout_s": 900
}
{ "id": "pod-3c9x1a", "state": "starting" }
name = "llama-ft"
region = "bom1"
gpu_type = "h100-sxm"
node_count = 8
fabric = "infiniband-400g"
scheduler = "slurm"
volume {
tier = "shared-fs"
size = "120Ti"
}
}
Reference
The rest of it
REST reference
Every endpoint, with request and response schemas and a live sandbox.
↗SDKPython and Go
Typed clients with retries, pagination and streaming logs built in.
↗IaCTerraform provider
Pods, clusters, volumes, buckets, VPCs and IAM as code.
↗ImagesBase containers
CUDA, ROCm, PyTorch, vLLM and TensorRT images, rebuilt weekly.
↗GuidesMigration guides
Moving from AWS, GCP, Azure and on-premise, with the gotchas named.
↗StatusStatus and incidents
Per-region health, maintenance windows and full post-incident reports.