Delivery modes and operating boundary
Fluidstack documents managed Kubernetes and managed Slurm on bare-metal AI infrastructure, with health checks and observability; Kubernetes is positioned for training and inference, while Slurm is presented for batch training.
These are orchestration offerings on bare-metal clusters, not interchangeable with a simple GPU VM or a token-metered serverless API. Managed control-plane features do not remove the need to validate application-level reliability and security.
Computraq is prelaunch. Naming this provider here does not mean that Computraq hosts workloads on it, has tested its integration, or has a commercial relationship with it.
Buyer and procurement preparation
Use these questions to prepare a comparable, workload-specific evaluation. Product names describe the provider’s published offering; they do not establish availability for a particular account.
- Determine whether Kubernetes or Slurm better matches the workload and team skills; request details on single tenancy, cluster sizing, support, capacity terms and service levels.
- Confirm storage performance, network topology, cluster access, health-check behavior, and which hardware repair tasks the provider owns.
- Record the exact allocation, renewal/termination terms and observability/support deliverables in the quote.
Developer and operator evidence
Before selecting capacity, create a small acceptance plan that records the model and revision, input shape, runtime, GPU configuration, concurrency, target latency or job completion, and recovery expectations. Provider documentation is evidence of product design, not proof that this workload has been tested.
- Test Kubernetes scheduling or Slurm submission using the intended container and distributed training/inference workflow.
- Review node health signals, failure behavior, checkpointing, user management and access controls before loading sensitive datasets.
- Benchmark the full path from storage to GPU and across nodes, not just device-level compute.