In this article
Treat Metal GPU as dedicated infrastructure. The actual plan, location, support and related services matter more than the general bare-metal label.
Latitude.sh provides infrastructure including dedicated Metal GPU plans. Evaluate the server’s full lifecycle: preparation, management, operation and completion. Infrastructure control does not replace operating processes.
Official pages were checked on 1 November 2026. This review neither guarantees each plan in every location nor provides independent speed or tariff comparisons.
Define the order
Latitude.sh documentation distinguishes bare metal, VMs, storage and networking. Metal GPU requires a specific plan and site. Record accelerators, VRAM, CPU, RAM, disks and interconnects required by the model.
A physical configuration and VM remain different even when both use cloud interfaces. Check environment-installation options and engine compatibility. Multiple GPUs need a separate workload-distribution decision.
Prepare to begin
The official documentation describes account setup and verification, projects and management methods. Confirm the account can create the required resource before the experiment date. A public product card does not establish a start time.
Prepare a secret-free environment description: image, versions, model and parameters. Test automation on a bounded launch first. API or CLI access helps only when another participant understands and can reproduce the configuration.
Read the plan’s costs
The pricing catalogue shows configurations and conditions. Clarify charging unit, duration, commitments and included resources. Do not confuse a whole multi-card node’s price with one device’s rate.
Include storage, networking and helper services. Compare longer commitments with real team availability and demand. A lower illustrative rate does not mean lower expense for unused capacity.
The reviewed catalogue includes multi-card HGX plans. Calculate the complete ordered node and topology. If the application uses only part of it, show that rather than assuming full useful utilisation.
Test a self-managed server
Suppose a team wants environment control for a continuously running model. Its pilot checks deployment, artifact preservation, API and ordinary-restart recovery, alongside software and hardware support procedures.
The result must demonstrate repeatable operation, not generation alone. A needed configuration change becomes another stage. Another plan or location requires separate validation even under the same brand.
Compare with your site
A rented dedicated node provides a complete infrastructure reference. Owned servers also require electricity, cooling, networking and someone on site. Renting Latitude.sh and supplying your own machine to an operator are different scenarios.
Review placement options and dedicated-resource choices.