Fine-Tune Cost Lab

Scenario · 13B parameters · LoRA or QLoRA

13B LoRA fine-tune on 100 million tokens: cost estimate

13 billion parameters, 100 million tokens, lora or qlora. The lowest estimate across 11 GPU entries is $4.28 on Vultr with MI355X, 1.7 h of GPU time at 35% MFU. An estimate, not a quote.

Step by step

The arithmetic

  1. 1. Training FLOPs. 4 × 13 × 10^9 parameters × 100 million tokens = 5.20 × 10^18 FLOPs. The forward pass costs about 2 x parameters x tokens and the backward pass about 2 x, because gradients for the frozen base weights are not computed. The small adapter matrices and QLoRA dequantisation are not counted.
  2. 2. Useful throughput per GPU. Dense BF16 TFLOPS × 10^12 × 35% MFU. The table gives it for each GPU.
  3. 3. GPU-hours. FLOPs ÷ throughput ÷ 3,600. For L40S (362.05 TFLOPS): 5.20 × 10^18 ÷ 1.27 × 10^14 ÷ 3,600 = 11 GPU-hours.
  4. 4. Wall-clock. GPU-hours ÷ 8 GPUs, assuming the work spreads evenly.
  5. 5. Cost. GPU-hours × each provider's lowest listed on-demand price per GPU-hour for that GPU.

Result

Estimated cost by GPU

GPUDense BF16 TFLOPSGPU-hours8 GPUsProvidersLowestMedianHighest
MI355X25001.6512 min2$4.28Vultr$9.24$14Oracle Cloud
MI300X1307.43.1624 min4$5.84Vultr$9.53$19Oracle Cloud
MI325X1307.43.1624 min2$6.31Vultr$9.15$12DigitalOcean (Paperspace)
H100 SXMpreliminary10004.1331 min6$12Thunder Compute$13$21Verda
GH2009904.1731 min2$8.30Vultr$18$27CoreWeave
H100 PCIepreliminary8005.1639 min2$13Hyperstack$14$15RunPod
L40S362.05111.4 h14$6.27Runcrate$17$40Oracle Cloud
A100 80GB312131.7 h12$14Thunder Compute$25$45Amazon Web Services
L40181.05232.8 h6$18Thunder Compute$21$29Runcrate
A40149.7283.4 h3$16RunPod$47$73Runcrate
A10125334.1 h4$33OVHcloud$64$106Microsoft Azure

Prices are each provider's lowest listed on-demand rate per GPU-hour, read 12 November 2026. Only GPUs whose maker prints a dense BF16 figure appear; the coverage page says which are out and why.

Sensitivity

What if MFU were different? (L40S)

MFU assumedGPU-hours8 GPUsLowest cost
20%202.5 h$11
35% (default)111.4 h$6.27
50%7.9860 min$4.39

The 20% and 50% rows are what-if inputs chosen to show sensitivity, not measurements. Lowest cost uses Runcrate at $0.55 per GPU-hour.

Try it

Change the assumptions

Estimate, step by step

  1. 1. Training FLOPs = 4 × 13 billion parameters × 100 million tokens = 5.20 × 10^18
  2. 2. Useful FLOP/s per GPU = 362.05 TFLOPS × 35% MFU = 1.27 × 10^14
  3. 3. GPU-hours = step 1 ÷ step 2 ÷ 3,600 = 11.4
  4. 4. Wall-clock on 8 GPUs = step 3 ÷ 8 = 1.4 h, assuming the work spreads evenly
  5. 5. Cost = step 3 × each provider's lowest listed price per GPU-hour
ProviderBilling$/GPU-hrEstimated cost
Runcrateours, liveper second$0.55$6.27
CloudRiftper second$0.69$7.87
Massed Computebilling not stated$0.97$11
RunPodper second$1.09$12
Koyebper second$1.20$14
Civoper hour$1.29$15
Crusoeper hour$1.50$17
DigitalOcean (Paperspace)per second$1.57$18
Vultrper hour$1.67$19
OVHcloudper hour$1.80$21
Amazon Web Servicesper second$1.86$21
Verdabilling not stated$2.00$23
CoreWeavebilling not stated$2.25$26
Oracle Cloudbilling not stated$3.50$40

Range $6.27 to $40, median $17 across 14 providers. An estimate, not a quote: real runs differ in utilisation, memory fit, communication and restarts, and providers that bill per hour round up.

Questions

13B LoRA fine-tune on 100 million tokens: common questions

How many FLOPs does this take?

About 5.20 × 10^18: 4 × 13 billion parameters × 100 million tokens. The forward pass costs about 2 x parameters x tokens and the backward pass about 2 x, because gradients for the frozen base weights are not computed. The small adapter matrices and QLoRA dequantisation are not counted.

What does it cost at the low end?

$4.28, on Vultr with MI355X at $2.59 per GPU-hour, for 1.7 GPU-hours.

Is this a quote?

No. It is an estimate from a stated formula and published list prices. Real runs differ in utilisation, memory fit and restarts, and the MFU is an assumption.

Why are some GPUs missing?

A GPU needs a dense BF16 figure printed by its maker. Those that print only a sparse figure are excluded rather than halved.

Related

Disclosure

Fine-Tune Cost Lab is published by the Runcrate team, who also run Runcrate, an AI cloud. Runcrate is listed in the table, marked "ours, live". It is sorted by price like every other row, with no pinned position. Other providers' prices are read from their own public pricing pages. We have no paid placement.