Calculator
MiniMax M3.1 Flash: self-host or API?
Self-hosting
Derived (an estimate)Estimate. The API is cheaper below 1,219 million tokens a day. Above that, self-hosting wins only if the configuration is busy at least 61% of the time, and only at our higher throughput estimates; at our lowest estimate, even constant use would not pay off.
At 50% utilization · Cheapest API offer: $0.197 per million tokens at EmpirioLabs AI (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.
- Break-even volume
- 1,218.89 million tokens a day
- Throughput self-hosting needs
- 28,216 tokens per second
- At 50% utilization
- Throughput self-hosting needs
- 14,108 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
- Break-even utilization: Prudent Never (above 100%) · Median Never (above 100%) · Optimistic 60.3%
- Published figure used (opens in a new tab)
Rented configuration
8 x L40 48GB at CoreWeave
$240.00 a day · $10.00 an hour · Guaranteed · 384 GB of GPU memory · fp8
Checked Oct 31, 2026 Price page at the provider (opens in a new tab)
Calculation detail
Throughput scenarios
| Scenario | Tokens per second | Usable capacity (million tokens a day) | Break-even utilization | Self-hosted cost per million tokens | Against the cheapest API offer |
|---|---|---|---|---|---|
| Prudent | 4,022 | 173.75 | Never (above 100%) | $1.38 | Dearer |
| Median | 10,054.9 | 434.37 | Never (above 100%) | $0.553 | Dearer |
| Optimistic | 23,400.5 | 1,010.9 | 60.3% | $0.237 | Dearer |
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
- same architecture type, scaled by memory bandwidth and active weights (x1)
- 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 fp8; guaranteed tier prices as published by the provider; utilization 50%.
- Published figures are generally peak throughput measured at high concurrency; an interactive service with latency targets sustains less.
- 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). We treat a published output figure as if the GPUs only generated tokens, ignoring that the benchmark also read prompts: this understates the throughput of the whole configuration, which is the cautious side for self-hosting.
- Break-even = daily GPU cost / API price per million tokens (1,219 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.