Compare/Apertus 70B Instruct vs Qwen3.8 27B (medium)

Apertus 70B InstructvsQwen3.8 27B (medium)

Side-by-side comparison of pricing, 12 benchmarks, and generation speed.

Swiss AI Initiative

Apertus 70B Instruct

Input
$0.82/M
Output
$2.92/M
Speed
TTFT
Alibaba

Qwen3.8 27B (medium)

Input
$0.5/M
Output
$3/M
Speed
65 tok/s
TTFT
3.02s

Winner by Category

Cheaper
Qwen3.8 27B (medium)
Faster (tok/s)
Qwen3.8 27B (medium)
Lower Latency
Qwen3.8 27B (medium)
Benchmarks (0-2)
Qwen3.8 27B (medium)

Pricing Comparison

MetricApertus 70B InstructQwen3.8 27B (medium)
Input ($/M tokens)$0.82$0.5
Output ($/M tokens)$2.92$3
Cost for 1M input + 100K output tokens:
Apertus 70B Instruct$1.11
Qwen3.8 27B (medium)$0.80

Speed Comparison

Output Speed (tokens/s) — higher is better
Apertus 70B Instruct
Qwen3.8 27B (medium)
65 tok/s
Time to First Token (seconds) — lower is better
Apertus 70B Instruct
Qwen3.8 27B (medium)
3.02s

Editorial Analysis

Verdict. Qwen3.8 27B (medium) takes the aggregate benchmark matchup 2–0 across 2 categories. Real workloads usually care about a handful of specific tasks — see the per-benchmark table above.

Pricing. Both models sit in the budget bracket for output-token pricing. At 1.0× the per-million-token cost, Apertus 70B Instruct is meaningfully cheaper if your traffic is output-heavy (long completions, document generation, agent loops). Apertus 70B Instruct makes more sense when output volume is low and absolute reasoning quality justifies the premium.

Strengths. Apertus 70B Instruct is strongest on Intelligence Index (2.0). Qwen3.8 27B (medium) leads on Coding Index (56.1), Intelligence Index (44.5).

Speed. Speed data is incomplete for this pair; benchmark and price should decide.

Provider. Swiss AI Initiative and Alibaba sell to overlapping but distinct developer audiences: Swiss AI Initiative tends to ship frontier reasoning models with premium positioning, while Alibaba often prices more aggressively. Your existing vendor relationships, billing, and SLA preferences may matter as much as the raw numbers above.

Workload cost. Workload scenarios (per million requests at 30M input + 15M output tokens): Apertus 70B Instruct costs $68.40 ($821/year); Qwen3.8 27B (medium) costs $60.00 ($720/year). At a smaller 5M-input/2M-output scale (single-developer tool or prototype): Apertus 70B Instruct ≈ $9.94/run, Qwen3.8 27B (medium) ≈ $8.50/run. At agent/realtime scale (200M input / 100M output per million requests): Apertus 70B Instruct ≈ $456/run, Qwen3.8 27B (medium) ≈ $400/run. Qwen3.8 27B (medium) becomes more attractive at higher volume — the absolute per-token pricing difference compounds when you ship at scale.

Recommendation. Both models have legitimate use cases — the right answer depends on whether you are optimizing for benchmark ceiling, latency, or unit cost. Start with the cheaper / faster model, evaluate against your specific task, and only switch if the upgrade shows a meaningful lift.

Benchmark Comparison

Data from Artificial Analysis API — 12 benchmarks

Intelligence Index
2.044.5
Coding Index
56.1
Math Index
GPQA Diamond
MMLU-Pro
LiveCodeBench
AIME 2025
MATH-500
Humanity's Last Exam
SciCode
IFBench
TerminalBench
Apertus 70B Instruct0 wins
2 winsQwen3.8 27B (medium)

Frequently Asked Questions

Which is cheaper, Apertus 70B Instruct or Qwen3.8 27B (medium)?

Qwen3.8 27B (medium) is cheaper overall. Its blended price (3:1 input/output ratio) is $1.13/M tokens vs $1.34/M for Apertus 70B Instruct.

Which model performs better on benchmarks?

Qwen3.8 27B (medium) wins 2 out of 12 benchmarks compared to 0 for Apertus 70B Instruct. See the detailed benchmark chart above for per-category results.

Which is faster for real-time applications?

Qwen3.8 27B (medium) generates tokens faster at 65 tok/s vs — tok/s. However, Qwen3.8 27B (medium) has lower time-to-first-token (3.02s vs —s).

When should I use Apertus 70B Instruct vs Qwen3.8 27B (medium)?

Choose based on your priorities: Qwen3.8 27B (medium) for lower cost, Qwen3.8 27B (medium) for stronger benchmark performance, and Qwen3.8 27B (medium) for faster generation. For latency-sensitive apps, check the TTFT comparison above.