AllocateDeepSeek R1 0528 NVFP4 vs Inkling
On provider list prices, Inkling costs $1.87 per million input tokens against $3 for DeepSeek R1 0528 NVFP4: 1.6x apart. Output is $4.68 against $7 (1.5x). On Allocate both bill at list plus the 7% transaction fee.
DeepSeek R1 0528 NVFP4
InklingSpecifications and provider list prices from the Allocate catalog, checked 2026-07-08. Billed price is list plus the 7% transaction fee.
What the numbers say
Take 1,000,000 requests a month at 1,200 input and 350 output tokens each. That workload costs $3,882 a month on Inkling and $6,050 on DeepSeek R1 0528 NVFP4 at list: a gap of $2,168, or 1.6x.
Inkling reads 1M tokens per request against 160K for DeepSeek R1 0528 NVFP4, 6.1x 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 for
- The lower list price ($1.87 in / $4.68 out per M tokens)
- The longer context window (1M vs 160K tokens)
- Fine-tuning under a permissive license (Apache 2.0)
Common questions
Which is cheaper, DeepSeek R1 0528 NVFP4 or Inkling?
Inkling, on this workload shape. At list prices it is $1.87/$4.68 per million tokens in and out against $3/$7 for DeepSeek R1 0528 NVFP4. Billed on Allocate: $2.00/$5.01 against $3.21/$7.49, list plus 7%.
Which has the bigger context window?
Inkling: 1,000,000 tokens (1M) against 163,840 (160K) for DeepSeek R1 0528 NVFP4.
Can I fine-tune DeepSeek R1 0528 NVFP4 or Inkling?
Both publish open weights (DeepSeek R1 0528 NVFP4: MIT; Inkling: 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.