Skip to content

Same-model provider benchmark

CoreWeave vs Google Vertex: LLM provider comparison

Compare CoreWeave and Google Vertex on 5 exact shared text models. ProviderBench keeps speed, price, and catalog coverage separate so naturally faster model catalogs cannot distort the result.

CoreWeave

20 indexed models

Headquarters
United States
Server regions
United States
Model types
20 text

Google Vertex

51 indexed models

Headquarters
United States
Server regions
europe-west1 · Belgiumeurope-west4 · NetherlandsGlobalus-central1 · United Statesus-east5 · United Statesus-south1 · United Statesus-west2 · United States
Model types
38 text, 6 image, 3 video, 2 embeddings, 1 speech, 1 transcription

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.24× typical advantage

5 exact models with complete recent speed data

Lowest token cost

$0.5487 / 1M

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

Most models available

51 models

Complete catalog coverage across all indexed modalities

Shared-model benchmark summary

MetricCoreWeave(0)Google Vertex(0)
SpeedCoreWeave9.06 sGoogle Vertex7.36 s
TTFTCoreWeave0.29 sGoogle Vertex0.56 s
TPSCoreWeave57.0 tok/sGoogle Vertex74.0 tok/s
UptimeCoreWeave99.84%Google Vertex97.80%
BlendedCoreWeave$0.586 / 1MGoogle Vertex$0.5487 / 1M
Green value Better comparable resultRed value Worse comparable result

Visual comparison

Price and performance charts

CoreWeaveGoogle Vertex
500-token response by shared model

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

Google Vertex has the lower typical same-model response ratio across 5 measured models.

Blended token price by shared model

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

Google Vertex has the lower typical price ratio across 5 priced shared models.

Shared text models

5 exact models · newest first

ModelCoreWeave(0)Google Vertex(0)
DeepSeek V3.1Winner · Google Vertex
CoreWeave
Speed— Worst comparable value
9.97 s
TTFT— Best comparable value
0.35 s
TPS— Worst comparable value
52.0 tok/s
Uptime— Best comparable value
100.00%
Context
161K
Route
coreweave/fp8
Blended— Best comparable value
$0.9167 / 1M
Google Vertex
Speed— Best comparable value
7.23 s
TTFT— Worst comparable value
0.82 s
TPS— Best comparable value
78.0 tok/s
Uptime— Worst comparable value
96.26%
Context
163.8K
Route
google-vertex/us-west2
Blended— Worst comparable value
$0.9667 / 1M
gpt-oss-120bWinner · CoreWeave
CoreWeave
Speed— Best comparable value
5.92 s
TTFT— Best comparable value
0.36 s
TPS— Best comparable value
90.0 tok/s
Uptime— Best comparable value
99.68%
Context
131.1K
Route
coreweave/fp4
Blended— Best comparable value
$0.0733 / 1M
Google Vertex
Speed— Worst comparable value
7.36 s
TTFT— Worst comparable value
0.51 s
TPS— Worst comparable value
73.0 tok/s
Uptime— Worst comparable value
99.34%
Context
131.1K
Route
google-vertex/global
Blended— Worst comparable value
$0.18 / 1M
gpt-oss-20bWinner · CoreWeave
CoreWeave
Speed— Best comparable value
4.18 s
TTFT— Best comparable value
0.28 s
TPS— Best comparable value
128.0 tok/s
Uptime— Best comparable value
87.61%
Context
131.1K
Route
coreweave/fp4
Blended— Best comparable value
$0.0633 / 1M
Google Vertex
Speed— Worst comparable value
7.51 s
TTFT— Worst comparable value
2.08 s
TPS— Worst comparable value
92.0 tok/s
Uptime— Worst comparable value
49.35%
Context
131.1K
Route
google-vertex/us-central1
Blended— Worst comparable value
$0.13 / 1M
Qwen3 Coder 480B A35BWinner · Google Vertex
CoreWeave
Speed— Worst comparable value
9.06 s
TTFT— Best comparable value
0.29 s
TPS— Worst comparable value
57.0 tok/s
Uptime
N/a
Context
262.1K
Route
coreweave/bf16
Blended— Worst comparable value
$1.1667 / 1M
Google Vertex
Speed— Best comparable value
7.32 s
TTFT— Worst comparable value
0.56 s
TPS— Best comparable value
74.0 tok/s
Uptime
100.00%
Context
262.1K
Route
google-vertex/us-south1
Blended— Best comparable value
$0.7467 / 1M
Llama 3.3 70B InstructWinner · Google Vertex
CoreWeave
Speed— Worst comparable value
18.01 s
TTFT— Best comparable value
0.15 s
TPS— Worst comparable value
28.0 tok/s
Uptime— Best comparable value
100.00%
Context
128K
Route
coreweave/fp16
Blended— Best comparable value
$0.71 / 1M
Google Vertex
Speed— Best comparable value
7.75 s
TTFT— Worst comparable value
0.28 s
TPS— Best comparable value
67.0 tok/s
Uptime— Worst comparable value
99.71%
Context
128K
Route
google-vertex
Blended— Worst comparable value
$0.72 / 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.

CoreWeave vs Google Vertex analysis

How CoreWeave and Google Vertex compare for AI inference

CoreWeave and Google Vertex share 5 indexed text models, including DeepSeek V3.1, gpt-oss-120b, gpt-oss-20b, Qwen3 Coder 480B A35B, Llama 3.3 70B Instruct. Google Vertex has the stronger typical response-time result on the directly measured set.

Same-model speed evidence

5 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

5 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

CoreWeave has 20 indexed models and lists 1 published server region; Google Vertex has 51 models and lists 7 regions. Verify data residency, privacy terms, limits, and production latency directly before choosing.