Skip to content
ProviderBench home

Same-model provider benchmark

Alibaba Cloud Int. vs Google Vertex: LLM provider comparison

Compare Alibaba Cloud Int. 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.

Alibaba Cloud Int.

48 indexed models

Headquarters
Singapore
Server regions
SingaporeChina
Model types
45 text, 2 video, 1 transcription

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

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

Alibaba Cloud Int.

1.50× typical advantage

4 exact models with complete recent speed data

Lowest token cost

Google Vertex

$0.624 / 1M

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

Most models available

Google Vertex

49 models

Complete catalog coverage across all indexed modalities

Shared-model benchmark summary

MetricAlibaba Cloud Int.Google Vertex
Typical 500-token response8.07 s15.69 s
Typical response start0.59 s0.61 s
Typical output speed75.0 tok/s65.3 tok/s
Blended token price$0.7683 / 1M$0.624 / 1M
Typical route uptime100.00%100.00%

Visual comparison

Price and performance charts

Alibaba Cloud Int.Google Vertex
500-token response by shared model

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

Alibaba Cloud Int. has the lower typical same-model response ratio across 4 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

ModelAlibaba Cloud Int.Google Vertex
DeepSeek V3.2

deepseek/deepseek-v3.2

Alibaba Cloud Int.
Blended price
$0.6175 / 1M
500-token response
28.11 s
Response starts
1.79 s
Output speed
19.0 tok/s
Route uptime
99.18%
Context
131.1K
Route
alibaba
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
Qwen3 Next 80B A3B ThinkingWinner · Alibaba Cloud Int.

qwen/qwen3-next-80b-a3b-thinking

Alibaba Cloud Int.
Blended price
$0.325 / 1M
500-token response
4.75 s
Response starts
0.51 s
Output speed
118.0 tok/s
Route uptime
100.00%
Context
131.1K
Route
alibaba
Google Vertex
Blended price
$0.5 / 1M
500-token response
5.10 s
Response starts
0.59 s
Output speed
111.0 tok/s
Route uptime
100.00%
Context
262.1K
Route
google-vertex/global
Qwen3 Next 80B A3B InstructWinner · Alibaba Cloud Int.

qwen/qwen3-next-80b-a3b-instruct

Alibaba Cloud Int.
Blended price
$0.325 / 1M
500-token response
5.67 s
Response starts
0.67 s
Output speed
100.0 tok/s
Route uptime
100.00%
Context
131.1K
Route
alibaba
Google Vertex
Blended price
$0.5 / 1M
500-token response
3.71 s
Response starts
0.58 s
Output speed
160.0 tok/s
Route uptime
100.00%
Context
262.1K
Route
google-vertex/global
Qwen3 Coder 480B A35BWinner · Alibaba Cloud Int.

qwen/qwen3-coder

Alibaba Cloud Int.
Blended price
$2.275 / 1M
500-token response
12.51 s
Response starts
1.40 s
Output speed
45.0 tok/s
Route uptime
N/a
Context
262.1K
Route
alibaba/opensource
Google Vertex
Blended price
$0.7467 / 1M
500-token response
91.58 s
Response starts
14.66 s
Output speed
6.5 tok/s
Route uptime
N/a
Context
262.1K
Route
google-vertex/us-south1
Qwen3 235B A22B Instruct 2507Winner · Alibaba Cloud Int.

qwen/qwen3-235b-a22b-2507

Alibaba Cloud Int.
Blended price
$0.299 / 1M
500-token response
10.46 s
Response starts
0.46 s
Output speed
50.0 tok/s
Route uptime
99.97%
Context
131.1K
Route
alibaba
Google Vertex
Blended price
$0.44 / 1M
500-token response
26.28 s
Response starts
0.63 s
Output speed
19.5 tok/s
Route uptime
99.96%
Context
262.1K
Route
google-vertex/us-south1

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.

Alibaba Cloud Int. vs Google Vertex analysis

How Alibaba Cloud Int. and Google Vertex compare for AI inference

Alibaba Cloud Int. and Google Vertex share 5 indexed text models, including DeepSeek V3.2, Qwen3 Next 80B A3B Thinking, Qwen3 Next 80B A3B Instruct, Qwen3 Coder 480B A35B, Qwen3 235B A22B Instruct 2507. Alibaba Cloud Int. has the stronger typical response-time result on the directly measured set.

Same-model speed evidence

4 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

Alibaba Cloud Int. has 48 indexed models and lists 2 published server regions; Google Vertex has 49 models and lists 7 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 Alibaba Cloud Int. and Google Vertex.

Alibaba Cloud Int. vs DeepInfra

17 shared model benchmarks

Google Vertex vs NovitaAI

12 shared model benchmarks

Alibaba Cloud Int. vs SiliconFlow

13 shared model benchmarks

Google Vertex vs Amazon Bedrock

12 shared model benchmarks

Alibaba Cloud Int. vs Venice

11 shared model benchmarks

Google Vertex vs Anthropic

10 shared model benchmarks