Start typing to search.
Same-model provider benchmark
Compare Google Vertex and Nebius on 3 exact shared text models. ProviderBench keeps speed, price, and catalog coverage separate so naturally faster model catalogs cannot distort the result.
49 indexed models
United States
europe-west1 · Belgium
europe-west4 · NetherlandsGlobalus-central1 · United Statesus-east5 · United Statesus-south1 · United Statesus-west2 · United States13 indexed models
NetherlandsAt a glance
There is no overall score. Each winner answers one specific question using only directly comparable data.
Fastest on shared models
1.03× typical advantage
3 exact models with complete recent speed data
Lowest token cost
$0.2844 / 1M
3 exact models using a 1K-input/500-output mix
Most models available
49 models
Complete catalog coverage across all indexed modalities
| Metric | Google Vertex | Nebius |
|---|---|---|
| Typical 500-token response | 6.83 s | 13.68 s |
| Typical response start | 0.42 s | 0.52 s |
| Typical output speed | 78.0 tok/s | 38.0 tok/s |
| Blended token price | $0.4467 / 1M | $0.2844 / 1M |
| Typical route uptime | 99.96% | 97.93% |
Visual comparison
Google VertexEstimated seconds using recent median response-start and output-speed data. Lower is better.
Nebius has the lower typical same-model response ratio across 3 measured models.
USD per 1 million tokens using a 1,000-input/500-output mix. Lower is better.
Nebius has the lower typical price ratio across 3 priced shared models.
| Model | Google Vertex | Nebius |
|---|---|---|
 gpt-oss-120bWinner · Google Vertex openai/gpt-oss-120b | Google Vertex
| Nebius
|
 Qwen3 235B A22B Instruct 2507Winner · Nebius qwen/qwen3-235b-a22b-2507 | Google Vertex
| Nebius
|
 Llama 3.3 70B InstructWinner · Google Vertex meta-llama/llama-3.3-70b-instruct | Google Vertex
| Nebius
|
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 Nebius analysis
Google Vertex and Nebius share 3 indexed text models, including gpt-oss-120b, Qwen3 235B A22B Instruct 2507, Llama 3.3 70B Instruct. Nebius has the stronger typical response-time result on the directly measured set.
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.
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.
Google Vertex has 49 indexed models and lists 7 published server regions; Nebius has 13 models and lists no regions. Verify data residency, privacy terms, limits, and production latency directly before choosing.
Related same-model benchmarks
Explore qualified alternatives with the most shared measured models. Recommendations include comparisons for both Google Vertex and Nebius.
