AllocateDeepSeek R1 0528 NVFP4 vs Inkling FP4
On provider list prices, Inkling FP4 costs $1 per million input tokens against $3 for DeepSeek R1 0528 NVFP4: 3.0x apart. Output is $4.05 against $7 (1.7x).
DeepSeek R1 0528 NVFP4
Inkling FP4Specifications and provider list prices from the Allocate catalog, checked 2026-07-21.
What the numbers say
Take 1,000,000 requests a month at 1,200 input and 350 output tokens each. That workload costs $2,618 a month on Inkling FP4 and $6,050 on DeepSeek R1 0528 NVFP4 at list: a gap of $3,433, or 2.3x.
Inkling FP4 reads 512K tokens per request against 160K for DeepSeek R1 0528 NVFP4, 3.2x the window. That decides which one can take whole documents without splitting them.
Choose DeepSeek R1 0528 NVFP4 for
- Fine-tuning under a permissive license (MIT)
Choose Inkling FP4 for
- The lower list price ($1 in / $4.05 out per M tokens)
- The longer context window (512K vs 160K tokens)
- Fine-tuning under a permissive license (Apache 2.0)
Common questions
Which is cheaper, DeepSeek R1 0528 NVFP4 or Inkling FP4?
Inkling FP4, on this workload shape. At list prices it is $1/$4.05 per million tokens in and out against $3/$7 for DeepSeek R1 0528 NVFP4. Billed on Allocate: $1.07/$4.33 against $3.21/$7.49.
Which has the bigger context window?
Inkling FP4: 524,288 tokens (512K) against 163,840 (160K) for DeepSeek R1 0528 NVFP4.
Can I fine-tune DeepSeek R1 0528 NVFP4 or Inkling FP4?
Both publish open weights (DeepSeek R1 0528 NVFP4: MIT; Inkling FP4: Apache 2.0), so both can be fine-tuned. On Allocate the trained weights stay inside your boundary and belong to you.
Related comparisons
Run the numbers on your workload
Or don’t choose. On Allocate a route name is the contract: point yours at one model today, swap to the other tomorrow, and compare them on your live traffic with per-token metering.