FAQ section
Machine images, containers, NVMe behavior, addresses, and bandwidth.
06
Machine images, containers, NVMe behavior, addresses, and bandwidth.
The catalog lists Ubuntu, PyTorch, vLLM, ComfyUI, Ollama, JAX, ROCm, and Debian starting points. Image availability depends on GPU vendor compatibility; for example, ROCm targets supported AMD configurations.
Link to this answer ↗
The intended dedicated-node service provides administrative access so customers can update packages, run containers, and configure their workload. Customers remain responsible for licenses, security updates, and compatibility with the selected hardware.
Link to this answer ↗
The account lifecycle treats local NVMe as part of the instance. Stopping preserves its allocation during the paid term or grace period; final deletion depends on the provisioning integration and retention policy. Do not treat local NVMe as a backup.
Link to this answer ↗
The catalog can quote extra NVMe storage, a dedicated public IPv4 address, additional bandwidth, and a private colocation VLAN. Availability, limits, and the exact period price should be confirmed before deployment.
Link to this answer ↗
Do not assume either. The deployment quote and documentation must state included transfer, purchased increments, enforcement behavior, and any overage policy. Backups exist only when a specific backup or persistent-storage product is selected and documented.
Link to this answer ↗