In this article
Compare the actual VM and site with CPU, RAM and storage included. Cloud customers and hardware suppliers make different decisions and have different economics.
TensorDock describes a host network connected through shared access tools. Teams can select compute, while equipment owners face another possible participation route. Begin with your role and the actual offer.
Current to 1 November 2026, this review uses official pages without reproducing superiority claims or independently testing hosts.
Select the actual GPU VM
TensorDock documentation explains the platform and host model. Record GPU, VRAM, CPU, RAM, disks and location. The same card does not establish the rest of the node’s characteristics across offers.
Define minimum and preferred model requirements. This avoids both paying for unused capacity and choosing an overly tight resource for its rate. Validate context and concurrency requirements with a test.
Read all cost components
The Cloud GPU page separates GPU and other resources and describes host-dependent offers. Compare the complete configuration: accelerator price can be only part of the total.
Record period, purchasing mode and storage terms. Check stopping behaviour and how to finish with required artifacts. Compare longer commitments with confirmed schedules and project budgets.
The reviewed public table includes H100 and A100 alongside RTX 4090 and RTX 3090. This illustrates variety, not equal inference suitability. Begin with memory and the whole currently available resource.
Separate customer and hosting roles
A supplier network does not automatically accept every home GPU. Owners must check current requirements, permitted sites and operational duties. A renter’s rate cannot answer those questions.
Decide which tasks you want to perform: hardware maintenance, environment setup or model-service management. Marketplaces and inference operators can allocate them differently. Clear responsibility is more informative than the broad phrase “rent out GPUs”.
Test a small model’s requirements
Suppose a team selects one VM and adjusts only necessary host resources. It uses identical tests for loading, quality, latency and recovery, preserving configuration for repetition on the same or another suitable offer.
A site change requires another networking and storage check. One successful VM is not a guarantee across the host network. Tie findings to configuration and period so comparisons remain useful.
Discuss your own hardware
A cloud catalogue can clarify the characteristics needed from an available server. Owner payment and cooperation terms remain separate. Retail rental rates cannot become an income forecast for your machine.
Review onboarding stages and heterogeneous fleets.