Skip to content

Same-model provider benchmark

AtlasCloud vs ModelRun: LLM provider comparison

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

AtlasCloud

31 indexed models

Headquarters
United States
Server regions
N/a
Model types
26 text, 5 video

ModelRun

4 indexed models

Headquarters
United States
Server regions
United States
Model types
4 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.67× typical advantage

3 exact models with complete recent speed data

Lowest token cost

$1.4389 / 1M

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

Most models available

31 models

Complete catalog coverage across all indexed modalities

Shared-model benchmark summary

MetricAtlasCloudModelRun
Typical 500-token response19.36 s13.99 s
Typical response start2.12 s0.50 s
Typical output speed29.0 tok/s40.0 tok/s
Blended token price$1.6978 / 1M$1.4389 / 1M
Typical route uptime97.60%99.20%

Visual comparison

Price and performance charts

AtlasCloudModelRun
500-token response by shared model

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

ModelRun has the lower typical same-model response ratio across 3 measured models.

Blended token price by shared model

USD per 1 million tokens using a 1,000-input/500-output mix. Lower is better.

ModelRun has the lower typical price ratio across 3 priced shared models.

Shared text models

3 exact models · newest first

ModelAtlasCloudModelRun
Kimi K2.7 CodeWinner · ModelRun

moonshotai/kimi-k2.7-code

AtlasCloud
Blended price
$1.9667 / 1M
500-token response
17.69 s
Response starts
1.30 s
Output speed
30.5 tok/s
Route uptime
N/a
Context
262.1K
Route
atlas-cloud/int4
ModelRun
Blended price
$1.8167 / 1M
500-token response
3.35 s
Response starts
0.46 s
Output speed
173.0 tok/s
Route uptime
98.81%
Context
262.1K
Route
modelrun/fp4
Kimi K2.6Winner · ModelRun

moonshotai/kimi-k2.6

AtlasCloud
Blended price
$1.9667 / 1M
500-token response
23.39 s
Response starts
4.16 s
Output speed
26.0 tok/s
Route uptime
96.35%
Context
262.1K
Route
atlas-cloud/int4
ModelRun
Blended price
$1.6 / 1M
500-token response
13.99 s
Response starts
1.49 s
Output speed
40.0 tok/s
Route uptime
98.64%
Context
262.1K
Route
modelrun/fp4
Kimi K2.5Winner · ModelRun

moonshotai/kimi-k2.5

AtlasCloud
Blended price
$1.16 / 1M
500-token response
19.36 s
Response starts
2.12 s
Output speed
29.0 tok/s
Route uptime
98.85%
Context
262.1K
Route
atlas-cloud/int4
ModelRun
Blended price
$0.9 / 1M
500-token response
16.12 s
Response starts
0.50 s
Output speed
32.0 tok/s
Route uptime
99.76%
Context
262.1K
Route
modelrun/fp4

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.

AtlasCloud vs ModelRun analysis

How AtlasCloud and ModelRun compare for AI inference

AtlasCloud and ModelRun share 3 indexed text models, including Kimi K2.7 Code, Kimi K2.6, Kimi K2.5. ModelRun 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

AtlasCloud has 31 indexed models and lists no published server regions; ModelRun has 4 models and lists 1 region. Verify data residency, privacy terms, limits, and production latency directly before choosing.