InferIndex
Language, English, EN
Account

Calculator

Kimi K2.5: self-host or API?

Self-hosting

No throughput figure

The API is cheaper below 614 million tokens a day. Above that, self-hosting wins only if the whole configuration (all GPUs together) delivers at least 14,222 tokens per second, input and output together, while serving at 50% utilization (7,111 if it were busy all the time).

At 50% utilization · Cheapest API offer: $0.781 per million tokens at NanoGPT (3:1 input:output mix)

Hardware rental only: the hourly price the provider publishes for the machine. It does not count the engineering to deploy and run the model, monitoring, redundancy, start-up time, or storage and network costs billed separately.

How it is calculated

Break-even volume
614.36 million tokens a day
Throughput self-hosting needs
14,222 tokens per second
At 50% utilization
Throughput self-hosting needs
7,111 tokens per second
If busy all the time

At least this many input plus output tokens per second, all GPUs together, while serving.

What published figures show

No throughput figure for this model on this configuration.

Settings

More settings
Or describe your requests

Instead of tokens per day: the three fields go together, and your own input:output mix is used.

Rented configuration

8 x RTX PRO 6000 96GB at CoreWeave

$480.00 a day · $20.00 an hour · Guaranteed · 768 GB of GPU memory · int4

Checked Oct 31, 2026 Price page at the provider (opens in a new tab)

Calculation detail

Cheapest of 19 current standard offers, promotions, unstable prices, off-peak prices without published hours and unverified prices far below those of the other providers excluded Checked Oct 31, 2026

Assumptions

  • We have no measured, derived or estimated throughput for this model on this card, and we have not assessed inference-engine support for it.
  • Hardware rental only: the hourly price the provider publishes for the machine. It does not count the engineering to deploy and run the model, monitoring, redundancy, start-up time, or storage and network costs billed separately.
  • Configuration: we pick the cheapest one whose weights fit. If a configuration costing up to 25% more has a measured throughput, we pick it instead; failing that, one with a derived throughput; failing that, one with a published lower bound that settles the verdict; among equals, the cheaper. A configuration whose throughput is only a wide estimate is never preferred over the cheapest. This is our rule, not a technical requirement.
  • Quantization int4; guaranteed tier prices as published by the provider; utilization 50%.
  • Throughput is aggregate (input and output tokens, 3:1). Published figures in generated tokens are converted with a prefill/generation speed ratio of 3 (prudent), 5 (median) and 8 (optimistic).
  • Break-even = daily GPU cost / API price per million tokens (614 million tokens a day). Self-hosting is cheaper only if the average utilization you can sustain exceeds break-even / raw capacity (the break-even utilization of each scenario), whatever the number of GPUs.

Same answer as JSON