Skip to content

Same-model provider benchmark

Chutes vs Crusoe: LLM provider comparison

Compare Chutes and Crusoe on 3 exact shared text models. ProviderBench keeps speed, price, and catalog coverage separate so naturally faster model catalogs cannot distort the result.

Chutes

9 indexed models

Headquarters
United States
Server regions
N/a
Model types
9 text

Crusoe

7 indexed models

Headquarters
United States
Server regions
N/a
Model types
7 text

At a glance

Metric winners

There is no overall score. Each winner answers one specific question using only directly comparable data.

Fastest on shared models

1.45× typical advantage

3 exact models with complete recent speed data

Lowest token cost

$1.1633 / 1M

3 exact models using a 1K-input/500-output mix

Most models available

9 models

Complete catalog coverage across all indexed modalities

Shared-model benchmark summary

MetricChutes(0)Crusoe(0)
SpeedChutes20.51 sCrusoe34.64 s
TTFTChutes2.46 sCrusoe0.83 s
TPSChutes29.0 tok/sCrusoe15.0 tok/s
UptimeChutes61.78%Crusoe91.12%
BlendedChutes$1.1633 / 1MCrusoe$1.3756 / 1M
Green value Better comparable resultRed value Worse comparable result

Visual comparison

Price and performance charts

ChutesCrusoe
500-token response by shared model

Estimated seconds using recent median response-start and output-speed data. Lower is better.

Chutes has the lower typical same-model response ratio across 3 measured models.

Blended token price by shared model

USD per 1 million tokens using a 1,000-input/500-output mix. Lower is better.

Chutes has the lower typical price ratio across 3 priced shared models.

Shared text models

3 exact models · newest first

ModelChutes(0)Crusoe(0)
Kimi K2.6Winner · Chutes
Chutes
Speed— Best comparable value
13.07 s
TTFT— Best comparable value
1.17 s
TPS— Best comparable value
42.0 tok/s
Uptime— Best comparable value
99.27%
Context
262.1K
Route
chutes/int4
Blended— Best comparable value
$1.6067 / 1M
Crusoe
Speed— Worst comparable value
34.64 s
TTFT— Worst comparable value
1.31 s
TPS— Worst comparable value
15.0 tok/s
Uptime— Worst comparable value
56.00%
Context
262.1K
Route
crusoe/bf16
Blended— Worst comparable value
$1.6333 / 1M
GLM 5.1Winner · Crusoe
Chutes
Speed— Worst comparable value
20.51 s
TTFT— Worst comparable value
3.27 s
TPS— Worst comparable value
29.0 tok/s
Uptime— Worst comparable value
28.70%
Context
202.8K
Route
chutes/fp8
Blended— Best comparable value
$1.68 / 1M
Crusoe
Speed— Best comparable value
5.89 s
TTFT— Best comparable value
0.39 s
TPS— Best comparable value
91.0 tok/s
Uptime— Best comparable value
100.00%
Context
202.8K
Route
crusoe/fp8
Blended— Worst comparable value
$2.2667 / 1M
Gemma 4 31BWinner · Chutes
Chutes
Speed— Best comparable value
58.02 s
TTFT— Worst comparable value
2.46 s
TPS— Best comparable value
9.0 tok/s
Uptime— Worst comparable value
61.78%
Context
131.1K
Route
chutes/fp4
Blended— Best comparable value
$0.2033 / 1M
Crusoe
Speed— Worst comparable value
84.17 s
TTFT— Best comparable value
0.83 s
TPS— Worst comparable value
6.0 tok/s
Uptime— Best comparable value
91.12%
Context
262.1K
Route
crusoe
Blended— Worst comparable value
$0.2267 / 1M

A per-model winner combines blended price and estimated 500-token response time with equal proportional weight. Ties and rows missing either measurement receive no badge. Comparison data calculated . Values use one deterministic route per provider and model; missing measurements remain visible as N/a.

Chutes vs Crusoe analysis

How Chutes and Crusoe compare for AI inference

Chutes and Crusoe share 3 indexed text models, including Kimi K2.6, GLM 5.1, Gemma 4 31B. Chutes has the stronger typical response-time result on the directly measured set.

Same-model speed evidence

3 shared models currently have complete response-start and output-speed measurements on both providers. The speed comparison uses per-model ratios before taking the median, so naturally faster model catalogs do not improve the result.

Token pricing on one workload

3 shared models have complete input and output prices on both providers. Prices use the same 1,000-input/500-output-token mix and are normalized to one million tokens for readability.

Catalog and deployment differences

Chutes has 9 indexed models and lists no published server regions; Crusoe has 7 models and lists no regions. Verify data residency, privacy terms, limits, and production latency directly before choosing.

Related same-model benchmarks

Compare with other providers

Explore qualified alternatives with the most shared measured models. Recommendations include comparisons for both Chutes and Crusoe.