--- title: "Salad Cloud Review (2026): Consumer GPU Pricing & Specs" slug: "salad-review" meta_description: "Salad Cloud review (2026): Rent consumer RTX 4090 and RTX 3090 GPUs at batch rates. Compare Salad Container Engine pricing, security, and batch AI trade-offs." schema_type: "review" author: "ahmad-nugraha" primary_keyword: "salad cloud review" secondary_keywords: - "salad review" - "salad compute" - "saladcloud review" - "salad gpu cloud" - "salad cloud pricing" - "salad container engine" - "saladcloud gpu pricing rtx 4090 2026" search_intent: "commercial-investigation" commercial: true published_at: "2026-07-22" updated_at: "2026-08-24" status: "published" human_reviewed_by: "ahmad-nugraha" human_reviewed_at: "2026-08-24" sources: - id: salad-pricing title: "Salad Cloud Pricing" publisher: "Salad" url: "https://salad.com/pricing" accessed_at: "2026-08-24" source_type: primary - id: salad-about title: "About Salad" publisher: "Salad" url: "https://salad.com/about" accessed_at: "2026-08-24" source_type: primary - id: salad-security title: "Security and Trust on SaladCloud" publisher: "Salad" url: "https://salad.com/security" accessed_at: "2026-08-24" source_type: primary - id: salad-docs title: "SaladCloud Documentation" publisher: "Salad" url: "https://docs.salad.com/" accessed_at: "2026-08-24" source_type: primary - id: salad-sce title: "Salad Container Engine (SCE)" publisher: "Salad Documentation" url: "https://docs.salad.com/container-engine/" accessed_at: "2026-08-24" source_type: primary - id: runpod-pricing title: "GPU Cloud Pricing" publisher: "RunPod" url: "https://www.runpod.io/pricing" accessed_at: "2026-08-24" source_type: primary - id: runpod-pods title: "Pods overview" publisher: "RunPod Documentation" url: "https://docs.runpod.io/pods/overview" accessed_at: "2026-08-24" source_type: primary - id: vast-pricing title: "GPU Pricing - Live Platform Rates" publisher: "Vast.ai" url: "https://vast.ai/pricing" accessed_at: "2026-08-24" source_type: primary --- Evaluating decentralized compute providers requires analyzing trade-offs between low hourly rates and variable host environments. In this detailed salad cloud review, we analyze how Salad Cloud leverages idle consumer gaming hardware via the Salad Container Engine to offer GPU compute at significantly lower prices than traditional datacenter platforms[cite id="salad-docs"]. [key-takeaways] - **Unbeatable batch pricing**: Container instances are listed at varying batch priority rates for RTX 4090 and RTX 5090 GPUs; see the pricing table below or the [GPU lookup](/lookup/gpu/rtx-4090/) for current verified pricing[cite id="salad-pricing"]. - **No charge for cold boot**: Billing commences only after your container finishes pulling images and transitions to a running state on host nodes[cite id="salad-pricing"]. - **Decentralized node pool**: Salad claims over 2 million registered nodes and more than 60,000 active GPUs supplied by individual PC owners worldwide[cite id="salad-about"]. - **Stateless execution model**: Containers run with ephemeral storage and no direct SSH access, requiring external object storage for state persistence[cite id="salad-sce"]. - **Compliance limitations**: Lack of SOC 2, HIPAA, or PCI-DSS certifications restricts enterprise deployment for sensitive regulated data[cite id="salad-security"]. [/key-takeaways] ## Salad Cloud review: Quick verdict Salad Cloud is a decentralized GPU network that aggregates over 60,000 consumer GPUs (including NVIDIA RTX 4090 and RTX 3090 cards) to deliver low-cost compute for batch AI inference, image generation, and video transcoding.[cite id="salad-about"][cite id="salad-pricing"] By executing workloads inside isolated Hyper-V virtual containers on retail PCs, Salad achieves hourly batch rates up to 70% lower than traditional clouds with zero egress fees and free cold boots.[cite id="salad-pricing"][cite id="salad-security"] However, ephemeral container storage, variable network speeds, and the absence of SOC 2 or HIPAA compliance make it unsuitable for real-time customer-facing APIs or regulated financial workloads.[cite id="salad-security"][cite id="salad-sce"] ## How Salad Cloud works and service model Salad Cloud operates on a peer-to-peer compute model that fundamentally differs from hyperscale datacenters or managed bare-metal providers[cite id="salad-docs"]. Salad Cloud organizes customer container workloads across three operational tiers[cite id="salad-sce"]: 1. **Salad Portal & API**: The entry point where developers define container groups, specify environment variables, configure hardware requirements (VRAM, vCPUs, RAM), and select target priority levels[cite id="salad-sce"]. 2. **Salad Container Engine (SCE)**: The orchestration layer that monitors available compute capacity across the peer-to-peer network, evaluates node stability using Trust Ratings, and deploys container images to verified hosts[cite id="salad-sce"]. 3. **Distributed Consumer Nodes**: Individual host machines owned by retail PC users worldwide. Each node runs containers inside isolated Linux virtual machines via Hyper-V, executing workloads on GPUs such as the RTX 3090, RTX 4090, or RTX 5090[cite id="salad-about"][cite id="salad-security"]. ### The decentralized node network Rather than owning data center racks, Salad aggregates compute capacity from retail PC owners who share their idle hardware in exchange for rewards[cite id="salad-about"]. Salad reports a global pool exceeding 2 million total registered nodes and over 60,000 available GPUs[cite id="salad-about"]. Workloads are scheduled through the Salad Container Engine (SCE), which packages Docker containers and deploys them to compatible host nodes across the network[cite id="salad-sce"]. ### Container execution environment Salad does not provide full virtual machines, root access, or direct SSH connections to host nodes[cite id="salad-sce"]. Compute instances run exclusively as standard OCI-compliant container groups[cite id="salad-sce"]. Because nodes run on Windows host systems using WSL2 and Hyper-V isolation, a small portion of GPU memory may be reserved by the host OS, resulting in slightly less than 100% available VRAM[cite id="salad-sce"]. Container filesystems are strictly ephemeral; any data written locally is permanently destroyed when a container stops or gets reassigned to a different node[cite id="salad-sce"]. ## Salad Cloud pricing and node priority tiers Salad Cloud uses a dynamic, priority-based pricing structure where cost corresponds directly to workload allocation priority[cite id="salad-pricing"]. | GPU Model | VRAM | Batch Hourly Rate | Standard Hourly Rate | Priority Hourly Rate | |---|---|---|---|---| | NVIDIA RTX 3080 | 10GB | $0.080[cite id="salad-pricing"] | $0.110[cite id="salad-pricing"] | $0.140[cite id="salad-pricing"] | | NVIDIA RTX 3090 | 24GB | $0.150[cite id="salad-pricing"] | $0.220[cite id="salad-pricing"] | $0.310[cite id="salad-pricing"] | | NVIDIA RTX 4090 | 24GB | $0.204[cite id="salad-pricing"] | $0.340[cite id="salad-pricing"] | $0.480[cite id="salad-pricing"] | | NVIDIA RTX 5090 | 32GB | $0.294[cite id="salad-pricing"] | $0.450[cite id="salad-pricing"] | $0.620[cite id="salad-pricing"] | ### Priority level mechanics - **Batch priority**: The lowest hourly rate[cite id="salad-pricing"]. Containers can be interrupted or preempted when higher-priority workloads request capacity. Ideal for stateless queues. - **Standard priority**: Provides balanced node reservation for general processing tasks[cite id="salad-pricing"]. - **Priority tier**: Gives containers maximum retention priority on active nodes[cite id="salad-pricing"]. ### Zero-cost cold boot policy A major financial advantage of Salad Cloud is its billing model for container setup. Traditional cloud providers charge per minute from the moment an instance begins booting, including slow container image pulls. Salad Cloud charges $0.00 during the initial image download and initialization phase[cite id="salad-pricing"]. Metered billing starts only when your container passes health checks and reaches a running status[cite id="salad-sce"]. ### Bandwidth and egress pricing Salad Cloud does not assess separate network egress fees for standard outbound data transfers[cite id="salad-pricing"]. This makes it highly economical for data-intensive workloads such as video rendering or bulk image output. ## Important features and platform security Deploying containerized applications on consumer hardware introduces unique security and reliability requirements. ### Container security and host isolation Salad enforces bidirectional isolation to safeguard both customer workloads and host PCs[cite id="salad-security"]: - **Hyper-V Virtualization**: Containers execute inside isolated Linux virtual machines managed by Hyper-V[cite id="salad-security"]. Host users cannot view memory contents or inspect container storage. - **Encrypted credentials**: Registry authentication tokens and environment secrets are encrypted in transit and at rest[cite id="salad-security"]. Private registry keys are discarded immediately after pulling container layers[cite id="salad-security"]. - **No inbound network access by default**: Containers do not expose open ports to the host local area network[cite id="salad-security"]. Outbound network connections route through secure proxy gateways[cite id="salad-security"]. ### Trust rating system To manage node quality, Salad uses an automated Trust Rating algorithm that continuously measures host uptime, hardware stability, and network bandwidth[cite id="salad-security"]. Nodes with high trust scores are prioritized for standard and priority container allocations, while unproven or unstable nodes are assigned low-priority batch workloads[cite id="salad-security"]. ### Regulatory compliance limitations Salad explicitly documents that its network is not certified for enterprise compliance standards such as SOC 2 Type II, HIPAA, or PCI-DSS[cite id="salad-security"]. Organizations handling protected health information, financial transactions, or classified data must not deploy those workloads on Salad Cloud[cite id="salad-security"]. ## Who should use Salad Cloud Salad Cloud is an optimal compute platform for specific architecture patterns: - **Asynchronous batch inference**: Processing queue-backed jobs where individual node restarts do not impact overall system completion[cite id="salad-sce"]. - **AI image and video generation**: Running Stable Diffusion or ComfyUI pipelines (see our roundup of the [best GPU cloud for Stable Diffusion](/best-gpu-cloud-for-stable-diffusion/)) that write output directly to AWS S3 or Google Cloud Storage[cite id="salad-sce"]. - **Cost-sensitive AI startups**: Teams looking for the [best cheap GPU cloud](/best-cheap-gpu-cloud/) to maximize compute hours per dollar[cite id="salad-pricing"]. - **3D rendering and transcoding**: Rendering Blender scenes or encoding video files where free egress reduces operational overhead[cite id="salad-pricing"]. ## Who should skip Salad Cloud You should choose alternative provider architectures if: - You require low-latency, real-time HTTP API endpoints with guaranteed sub-100ms cold start times[cite id="salad-sce"]. - Your workload requires root VM access, custom kernel modules, or persistent block storage attached to instances[cite id="salad-sce"]. - You operate under mandatory SOC 2, HIPAA, or ISO 27001 regulatory compliance requirements[cite id="salad-security"]. - You require high-speed multi-GPU interconnects like NVLink for large-scale distributed model training[cite id="salad-sce"]. ## Alternatives to Salad Cloud Comparing Salad against alternative cloud hosts helps determine whether decentralized compute fits your requirements. ### Salad Cloud vs RunPod RunPod offers dedicated data center instances with persistent disk storage, template pods, and root terminal access[cite id="runpod-pods"]. While RunPod's verified on-demand rates for consumer GPUs are listed higher than Salad's batch priority levels, RunPod provides predictable hardware performance and persistent storage; see the [GPU lookup](/lookup/gpu/rtx-4090/) for current verified pricing[cite id="runpod-pricing"]. Read our detailed [RunPod review](/runpod-review/) for complete technical specifications. ### Salad Cloud vs Vast.ai Vast.ai operates a marketplace connecting renters to individual host servers[cite id="vast-pricing"]. Unlike Salad's container-only abstraction, Vast.ai grants direct SSH access, configurable persistent storage, and full VM management[cite id="vast-pricing"]. However, pricing on Vast.ai varies by individual host operator. Review our [Vast.ai review](/vast-ai-review/) to compare marketplace mechanics. ### Salad Cloud vs TensorDock TensorDock provides low-cost virtual machines across independent regional datacenters. TensorDock includes root SSH access and persistent storage, catering to users who need full server control rather than containerized batch processing. See our [TensorDock review](/tensordock-review/) for platform details. ## Pros and cons [pros-cons] + **Exceptional value**: Batch priority rates for RTX 4090 and RTX 5090 are listed at a discount to traditional clouds; see the pricing table above for current verified rates[cite id="salad-pricing"]. + **Zero-cost cold boots**: No billing while pulling container images or running startup scripts[cite id="salad-pricing"]. + **No egress fees**: Outbound data transfers are included without extra bandwidth charges[cite id="salad-pricing"]. + **Vast capacity**: Access to over 60,000 consumer GPUs globally[cite id="salad-about"]. - **Stateless storage**: Ephemeral container filesystems require external object storage[cite id="salad-sce"]. - **Variable cold starts**: Image pull times depend on consumer host internet bandwidth[cite id="salad-sce"]. - **No SSH or root access**: Execution restricted to managed container groups[cite id="salad-sce"]. - **No enterprise compliance**: Lacks SOC 2, HIPAA, and PCI-DSS security certifications[cite id="salad-security"]. [/pros-cons] ## Research methodology and sources GPU Picks evaluates cloud compute platforms using official documentation, published pricing tables, and architectural specifications[cite id="salad-docs"]. We do not conduct hands-on performance benchmarks or publish subjective testing metrics. For details on our evidence principles, visit our [methodology page](/methodology/), inspect live node pricing in our [Salad provider lookup](/lookup/provider/salad/), review specs in our [RTX 4090 lookup](/lookup/gpu/rtx-4090/) and [A100 lookup](/lookup/gpu/a100/), or browse all instances in our [GPU lookup tool](/lookup/). [faq] ## Is Salad Cloud cheaper than traditional cloud providers? Yes, Salad Cloud's batch pricing model offers hourly rates up to 70% lower than traditional cloud providers by aggregating idle consumer gaming hardware[cite id="salad-pricing"]. ## Does Salad Cloud charge for container startup time? No, Salad Cloud does not charge for cold boot or container initialization[cite id="salad-pricing"]. Metered billing begins only when your container passes health checks and reaches a running state[cite id="salad-sce"]. ## Can I attach persistent disk storage to Salad containers? No, Salad Cloud container instances use ephemeral local filesystems[cite id="salad-sce"]. All persistent data must be saved to external cloud object storage like AWS S3 or Google Cloud Storage[cite id="salad-sce"]. ## How does Salad Cloud secure containers on consumer PCs? Salad isolates containers inside Linux virtual machines using Hyper-V hardware virtualization[cite id="salad-security"]. Container memory and storage are protected from host inspection, and registry credentials are encrypted[cite id="salad-security"]. ## Does Salad Cloud support root SSH access? No, Salad Container Engine runs managed container groups without direct SSH access or root virtual machine terminals[cite id="salad-sce"]. ## What GPUs are available on Salad Cloud? Salad offers consumer GPUs including the NVIDIA RTX 3080, RTX 3090, RTX 4090, and RTX 5090, depending on active host node availability[cite id="salad-pricing"]. [/faq]