Skip to content

Same-model provider benchmark

Google Vertex vs SiliconFlow: LLM provider comparison

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

Google Vertex

49 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
36 text, 6 image, 3 video, 2 embeddings, 1 speech, 1 transcription

SiliconFlow

36 indexed models

Headquarters
Singapore
Server regions
United States
Model types
35 text, 1 embeddings

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

5.08× typical advantage

3 exact models with complete recent speed data

Lowest token cost

$0.2619 / 1M

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

Most models available

49 models

Complete catalog coverage across all indexed modalities

Shared-model benchmark summary

MetricGoogle VertexSiliconFlow
Typical 500-token response6.83 s33.11 s
Typical response start0.42 s1.86 s
Typical output speed78.0 tok/s16.0 tok/s
Blended token price$0.502 / 1M$0.2619 / 1M
Typical route uptime97.94%94.21%

Visual comparison

Price and performance charts

Google VertexSiliconFlow
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 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.

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

Shared text models

5 exact models · newest first

ModelGoogle VertexSiliconFlow
Gemma 4 26B A4BWinner · SiliconFlow

google/gemma-4-26b-a4b-it

Google Vertex
Blended price
$0.3 / 1M
500-token response
24.23 s
Response starts
0.42 s
Output speed
21.0 tok/s
Route uptime
97.94%
Context
262.1K
Route
google-vertex/global
SiliconFlow
Blended price
$0.2133 / 1M
500-token response
21.58 s
Response starts
1.58 s
Output speed
25.0 tok/s
Route uptime
99.95%
Context
262.1K
Route
siliconflow/fp8

deepseek/deepseek-v3.2

Google Vertex
Blended price
$0.9333 / 1M
500-token response
N/a
Response starts
N/a
Output speed
N/a
Route uptime
N/a
Context
163.8K
Route
google-vertex
SiliconFlow
Blended price
$0.3127 / 1M
500-token response
22.45 s
Response starts
1.61 s
Output speed
24.0 tok/s
Route uptime
99.75%
Context
163.8K
Route
siliconflow/fp8
DeepSeek V3.1Winner · Google Vertex

deepseek/deepseek-chat-v3.1

Google Vertex
Blended price
$0.9667 / 1M
500-token response
6.51 s
Response starts
1.19 s
Output speed
94.0 tok/s
Route uptime
99.89%
Context
163.8K
Route
google-vertex/us-west2
SiliconFlow
Blended price
$0.5133 / 1M
500-token response
33.11 s
Response starts
1.86 s
Output speed
16.0 tok/s
Route uptime
94.21%
Context
163.8K
Route
siliconflow/fp8
gpt-oss-120bWinner · Google Vertex

openai/gpt-oss-120b

Google Vertex
Blended price
$0.18 / 1M
500-token response
6.83 s
Response starts
0.42 s
Output speed
78.0 tok/s
Route uptime
95.91%
Context
131.1K
Route
google-vertex/global
SiliconFlow
Blended price
$0.1833 / 1M
500-token response
44.57 s
Response starts
2.90 s
Output speed
12.0 tok/s
Route uptime
64.12%
Context
131.1K
Route
siliconflow/fp8

openai/gpt-oss-20b

Google Vertex
Blended price
$0.13 / 1M
500-token response
N/a
Response starts
N/a
Output speed
N/a
Route uptime
N/a
Context
131.1K
Route
google-vertex/us-central1
SiliconFlow
Blended price
$0.0867 / 1M
500-token response
42.99 s
Response starts
1.33 s
Output speed
12.0 tok/s
Route uptime
99.35%
Context
131.1K
Route
siliconflow/fp8

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.

Google Vertex vs SiliconFlow analysis

How Google Vertex and SiliconFlow compare for AI inference

Google Vertex and SiliconFlow share 5 indexed text models, including Gemma 4 26B A4B, DeepSeek V3.2, DeepSeek V3.1, gpt-oss-120b, gpt-oss-20b. Google Vertex 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

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

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