The fees the sticker price hides

A cheap $/hr can turn expensive on egress, storage, or coarse billing increments. Every cell below was verified at the provider's own documentation; "not published" means exactly that, which is itself worth knowing.

Verified cells link to their source. Green egress cells = flat free egress (6 of 18 providers); conditional or in-region-only free is not highlighted. Corrections: [email protected]. Licensed under CC BY 4.0 with attribution.

Data egress costs: what leaving the cloud costs

Data egress cost is the fee for moving data out of a cloud: downloading trained model weights, exporting datasets, or streaming results to another provider. Ingress (uploading in) is usually free; egress is where the surprises live. Of the 18 GPU clouds in the matrix, 6 publish flat free egress, 6 charge for it or attach conditions (per-GB rates, included-bandwidth caps, or free only in-region), and 6 do not publish a rate at all. "Not published" is worth treating as a question to ask before you commit, not as free.

Same verified cells as the full matrix above, sliced to transfer fees; each verified value links to the provider page it was read from. Why it matters: a big checkpoint or dataset leaving a per-GB-egress cloud can cost more than the compute that produced it, and the gap between a free-egress neocloud and a hyperscaler's tiered egress compounds with every export. If your workflow moves large artifacts between clouds regularly, weight the egress column as heavily as the $/hr sticker on the live price table.

Why this matters more than the $/hr

Three patterns to watch. First, egress: moving a trained model or dataset out of a cloud with per-GB egress can cost more than the training run. Second, storage while stopped: some providers keep billing for attached storage when the instance is off. Third, billing increments: per-second billing makes bursty work dramatically cheaper than per-hour billing at the same $/hr rate. The calculator and the live table cover the compute side; this page covers the rest.

Cite this matrix

Referencing the fee or egress matrix in an article, paper or dashboard? Cite the version you retrieved (cells verified 2026-07-07):

APA

GPU Rental Prices. (2026). GPU Cloud Fees and Egress Matrix [Data set]. gpurentalprices.com. Retrieved 2026-08-22, from https://gpurentalprices.com/fees

BibTeX

@misc{gpufees_2026,
  title  = {GPU Cloud Fees and Egress Matrix},
  author = {{GPU Rental Prices}},
  year   = {2026},
  howpublished = {\url{https://gpurentalprices.com/fees}},
  note   = {Cells verified at provider documentation 2026-07-07. Accessed 2026-08-22}
}

HTML

<a href="https://gpurentalprices.com/fees">GPU Cloud Fees and Egress Matrix</a>. GPU Rental Prices, 2026. Accessed 2026-08-22.

Free under CC BY 4.0 with a visible link to gpurentalprices.com. Live price data and the full dataset: Data & API.