Skip to content
ProviderBench home

Same-model provider benchmark

Fireworks vs StreamLake: LLM provider comparison

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

Fireworks

8 indexed models

Headquarters
United States
Server regions
N/a
Model types
8 text

StreamLake

20 indexed models

Headquarters
China
Server regions
N/a
Model types
20 text

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

Fireworks

1.74× typical advantage

5 exact models with complete recent speed data

Lowest token cost

StreamLake

$1.2317 / 1M

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

Most models available

StreamLake

20 models

Complete catalog coverage across all indexed modalities

Shared-model benchmark summary

MetricFireworksStreamLake
Typical 500-token response9.40 s23.14 s
Typical response start1.23 s2.42 s
Typical output speed61.5 tok/s26.0 tok/s
Blended token price$1.8547 / 1M$1.2317 / 1M
Typical route uptime98.20%97.71%

Visual comparison

Price and performance charts

FireworksStreamLake
500-token response by shared model

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

Fireworks 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.

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

Shared text models

5 exact models · newest first

ModelFireworksStreamLake
GLM 5.2Winner · Fireworks

z-ai/glm-5.2

Fireworks
Blended price
$2.4 / 1M
500-token response
11.65 s
Response starts
1.23 s
Output speed
48.0 tok/s
Route uptime
99.00%
Context
1M
Route
fireworks
StreamLake
Blended price
$1.6524 / 1M
500-token response
20.26 s
Response starts
2.40 s
Output speed
28.0 tok/s
Route uptime
99.81%
Context
1M
Route
streamlake/fp8
DeepSeek V4 ProWinner · StreamLake

deepseek/deepseek-v4-pro

Fireworks
Blended price
$2.32 / 1M
500-token response
34.18 s
Response starts
2.93 s
Output speed
16.0 tok/s
Route uptime
98.35%
Context
1M
Route
fireworks
StreamLake
Blended price
$0.9512 / 1M
500-token response
27.98 s
Response starts
2.98 s
Output speed
20.0 tok/s
Route uptime
93.71%
Context
1M
Route
streamlake/fp8
DeepSeek V4 FlashWinner · Fireworks

deepseek/deepseek-v4-flash

Fireworks
Blended price
$0.1867 / 1M
500-token response
7.79 s
Response starts
1.04 s
Output speed
74.0 tok/s
Route uptime
98.04%
Context
1M
Route
fireworks
StreamLake
Blended price
$0.1288 / 1M
500-token response
13.31 s
Response starts
1.94 s
Output speed
44.0 tok/s
Route uptime
98.66%
Context
1M
Route
streamlake/fp8
Kimi K2.6Winner · Fireworks

moonshotai/kimi-k2.6

Fireworks
Blended price
$1.9667 / 1M
500-token response
6.99 s
Response starts
0.41 s
Output speed
76.0 tok/s
Route uptime
N/a
Context
262.1K
Route
fireworks
StreamLake
Blended price
$1.77 / 1M
500-token response
23.14 s
Response starts
3.91 s
Output speed
26.0 tok/s
Route uptime
97.94%
Context
256K
Route
streamlake/fp8
GLM 5.1Winner · Fireworks

z-ai/glm-5.1

Fireworks
Blended price
$2.4 / 1M
500-token response
9.40 s
Response starts
1.27 s
Output speed
61.5 tok/s
Route uptime
87.25%
Context
202.8K
Route
fireworks
StreamLake
Blended price
$1.656 / 1M
500-token response
25.14 s
Response starts
2.42 s
Output speed
22.0 tok/s
Route uptime
96.76%
Context
200K
Route
streamlake/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.

Fireworks vs StreamLake analysis

How Fireworks and StreamLake compare for AI inference

Fireworks and StreamLake share 5 indexed text models, including GLM 5.2, DeepSeek V4 Pro, DeepSeek V4 Flash, Kimi K2.6, GLM 5.1. Fireworks 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

Fireworks has 8 indexed models and lists no 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

Compare with other providers

Explore qualified alternatives with the most shared measured models. Recommendations include comparisons for both Fireworks and StreamLake.

Fireworks vs DeepInfra

8 shared model benchmarks

StreamLake vs NovitaAI

16 shared model benchmarks

Fireworks vs AtlasCloud

7 shared model benchmarks

StreamLake vs SiliconFlow

12 shared model benchmarks

Fireworks vs Parasail

7 shared model benchmarks

StreamLake vs Venice

12 shared model benchmarks