ModelRun
4 indexed models
- Headquarters
United States- Server regions
- United States
- Model types
- 4 text
Same-model provider benchmark
ModelRun vs Together: LLM provider comparison
Compare ModelRun and Together on 3 exact shared text models. ProviderBench keeps speed, price, and catalog coverage separate so naturally faster model catalogs cannot distort the result.
Together
19 indexed models
- Headquarters
- United States
- Server regions
- N/a
- Model types
- 17 text, 2 transcription
At a glance
Metric winners
There is no overall score. Each winner answers one specific question using only directly comparable data.
Shared-model benchmark summary
| Metric | ModelRun | Together |
|---|---|---|
| Typical 500-token response | 6.85 s | 5.21 s |
| Typical response start | 0.90 s | 0.54 s |
| Typical output speed | 84.0 tok/s | 107.0 tok/s |
| Blended token price | $1.2489 / 1M | $1.58 / 1M |
| Typical route uptime | 98.64% | 99.29% |
Visual comparison
Price and performance charts
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.
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.
| Model | ModelRun | Together |
|---|---|---|
 Kimi K2.7 CodeWinner · ModelRun moonshotai/kimi-k2.7-code | ModelRun
| Together
|
Kimi K2.6Winner · Together moonshotai/kimi-k2.6 | ModelRun
| Together
|
 Gemma 4 31BWinner · ModelRun google/gemma-4-31b-it | ModelRun
| Together
|
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.
ModelRun vs Together analysis
How ModelRun and Together compare for AI inference
ModelRun and Together share 3 indexed text models, including Kimi K2.7 Code, Kimi K2.6, Gemma 4 31B. 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
ModelRun has 4 indexed models and lists 1 published server region; Together has 19 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 ModelRun and Together.
