Cloudflare
12 indexed models
- Headquarters
United States- Server regions
- N/a
- Model types
- 12 text
Same-model provider benchmark
Cloudflare vs Fireworks: LLM provider comparison
Compare Cloudflare and Fireworks on 3 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
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
1.12× typical advantage
3 exact models with complete recent speed data
Lowest token cost
Equal result
Tie
3 exact models using a 1K-input/500-output mix
Most models available
12 models
Complete catalog coverage across all indexed modalities
Shared-model benchmark summary
| Metric | Cloudflare | Fireworks |
|---|---|---|
| Typical 500-token response | 10.35 s | 11.65 s |
| Typical response start | 0.79 s | 1.23 s |
| Typical output speed | 52.0 tok/s | 52.0 tok/s |
| Blended token price | $2.1111 / 1M | $2.1111 / 1M |
| Typical route uptime | 99.85% | 99.00% |
Visual comparison
Price and performance charts
FireworksEstimated seconds using recent median response-start and output-speed data. Lower is better.
Cloudflare 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.
Neither provider has a clear token-price advantage.
| Model | Cloudflare | Fireworks |
|---|---|---|
 GLM 5.2Winner · Cloudflare z-ai/glm-5.2 | Cloudflare
| Fireworks
|
 Kimi K2.7 CodeWinner · Cloudflare moonshotai/kimi-k2.7-code | Cloudflare
| Fireworks
|
Kimi K2.6Winner · Fireworks moonshotai/kimi-k2.6 | Cloudflare
| Fireworks
|
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.
Cloudflare vs Fireworks analysis
How Cloudflare and Fireworks compare for AI inference
Cloudflare and Fireworks share 3 indexed text models, including GLM 5.2, Kimi K2.7 Code, Kimi K2.6. Cloudflare 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
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.
Catalog and deployment differences
Cloudflare has 12 indexed models and lists no published server regions; Fireworks has 8 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 Cloudflare and Fireworks.
