Start typing to search.
Same-model provider benchmark
Compare Google Vertex and StreamLake 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 States20 indexed models
ChinaAt a glance
There is no overall score. Each winner answers one specific question using only directly comparable data.
Fastest on shared models
1.17× typical advantage
3 exact models with complete recent speed data
Lowest token cost
$0.5256 / 1M
3 exact models using a 1K-input/500-output mix
Most models available
49 models
Complete catalog coverage across all indexed modalities
Visual comparison
Google VertexEstimated 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.
USD per 1 million tokens using a 1,000-input/500-output mix. Lower is better.
StreamLake has the lower typical price ratio across 3 priced shared models.
| Model | Google Vertex | StreamLake |
|---|---|---|
 GLM 4.7Winner · Google Vertex z-ai/glm-4.7 | Google Vertex
| StreamLake
|
 DeepSeek V3.2Winner · StreamLake deepseek/deepseek-v3.2 | Google Vertex
| StreamLake
|
 Qwen3 235B A22B Instruct 2507Winner · Google Vertex qwen/qwen3-235b-a22b-2507 | Google Vertex
| StreamLake
|
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 StreamLake analysis
Google Vertex and StreamLake share 3 indexed text models, including GLM 4.7, DeepSeek V3.2, Qwen3 235B A22B Instruct 2507. Google Vertex 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; StreamLake has 20 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 StreamLake.
14 shared model benchmarks
15 shared model benchmarks
12 shared model benchmarks
14 shared model benchmarks
10 shared model benchmarks
12 shared model benchmarks
