Pick MAI-1-preview for microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai or ranked in the top 15 on lm arena at launch. Pick Qwen3.6 35B A3B for extreme sparsity — only 3b of 35b parameters active per token, giving near-3b inference cost or runs at roughly 120 tokens per second on a single 24gb consumer gpu. Choose Qwen3.6 35B A3B if you need self-hosting or data privacy; MAI-1-preview if you want a managed API.
MAI-1-preview (Microsoft, US) and Qwen3.6 35B A3B (Alibaba, China) line up two different AI ecosystems against each other — a comparison that is as much about cost philosophy and openness as raw capability. MAI-1-preview is microsoft's first fully in-house foundation model - a strategic break from sole reliance on OpenAI, trained on ~15,000 H100 GPUs. Qwen3.6 35B A3B is a sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware. They diverge most on context window and open vs. closed weights — each quantified below from the models' real specs.
Key differences
Cost model: Qwen3.6 35B A3B ships open weights you can self-host (hardware cost only, no per-token fee), while MAI-1-preview is API-metered at Not published. Your choice depends on whether you want zero marginal cost at the price of running infrastructure.
Context window: Qwen3.6 35B A3B holds 2× more — 256K (~393 pages) vs 128K (~192 pages). But effective recall usually fades long before the advertised ceiling, so the bigger number only helps if the model reasons over it.
Recency: Qwen3.6 35B A3B is the newer model by about 8 months (released April 16, 2026), usually meaning fresher training data and capabilities.
Ecosystem: this is a US-vs-China matchup — they differ in pricing philosophy, data-residency options, and tooling ecosystems, not only benchmarks.
Specifications
Spec
MAI-1-preview
Qwen3.6 35B A3B
Provider
Microsoft (US)
Alibaba (China)
Released
August 28, 2025
April 16, 2026
Context window
128K (~192 pages)
256K (~393 pages)
Price (in/out)
Not published
Open weight (self-host / free)
Open weight?
No — API only
Yes — self-hostable
Modalities
text, code
text, image, code
SWE-Bench Verified
Not published
73.4%
MRCR v2 @ 1M
Not published
Not published
Who wins what
Microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI: MAI-1-preview — MAI-1-preview lists microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI among its strengths; Qwen3.6 35B A3B does not.
Ranked in the top 15 on LM Arena at launch: MAI-1-preview — MAI-1-preview lists ranked in the top 15 on LM Arena at launch among its strengths; Qwen3.6 35B A3B does not.
Trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment: MAI-1-preview — Qwen3.6 35B A3B is comparatively weak here — its SWE-Bench score comes from Alibaba's internal scaffold rather than the standard public harness
Extreme sparsity — only 3B of 35B parameters active per token, giving near-3B inference cost: Qwen3.6 35B A3B — Its 256K window holds about 2× more than MAI-1-preview's 128K in a single prompt.
Runs at roughly 120 tokens per second on a single 24GB consumer GPU: Qwen3.6 35B A3B — A sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware — and it carries the larger 256K context.
Apache 2.0 weights with a 256K native context, extensible to about 1M via YaRN: Qwen3.6 35B A3B — A sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware — and its weights are open while MAI-1-preview is API-only.
Largest single-prompt input: Qwen3.6 35B A3B — Its 256K window is about 2× larger than MAI-1-preview's 128K, fitting roughly 393 pages in one prompt.
Which should you pick?
Someone analysing very long documents or codebases: Qwen3.6 35B A3B — Larger 256K window fits more in one prompt.
A team with data-privacy or self-hosting needs: Qwen3.6 35B A3B — Open weights let you run it on your own hardware; MAI-1-preview is API-only.
Anyone whose priority is microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai: MAI-1-preview — It is specifically built for that.
Anyone whose priority is extreme sparsity — only 3b of 35b parameters active per token, giving near-3b inference cost: Qwen3.6 35B A3B — That is its strongest area.
An enterprise with regional data-residency rules: MAI-1-preview or Qwen3.6 35B A3B — Origin (US vs China) affects where data is processed and which compliance regime applies — check the provider's terms for your region.
MAI-1-preview: where it fits
Microsoft's first fully in-house foundation model - a strategic break from sole reliance on OpenAI, trained on ~15,000 H100 GPUs. Released August 28, 2025 by Microsoft, it is built for microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI, ranked in the top 15 on LM Arena at launch, trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment, and rolled into Copilot alongside OpenAI models, giving Microsoft a real second option.
Its trade-offs are real: a 'preview' release, not yet positioned as Microsoft's primary Copilot model, no public per-token API pricing - not sold as a standalone product, and distinct from Microsoft's later MAI-Thinking-1 reasoning model - an earlier, more general-purpose entry.
Qwen3.6 35B A3B: where it fits
A sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware. Released April 16, 2026 by Alibaba, it is built for extreme sparsity — only 3B of 35B parameters active per token, giving near-3B inference cost, runs at roughly 120 tokens per second on a single 24GB consumer GPU, apache 2.0 weights with a 256K native context, extensible to about 1M via YaRN, and preserves its reasoning across turns, which cuts the overhead of agentic loops.
Its trade-offs: loses to its smaller dense sibling Qwen3.6 27B on every coding benchmark, despite more total parameters, its SWE-Bench score comes from Alibaba's internal scaffold rather than the standard public harness, and all 35B parameters must stay resident in VRAM even though only 3B compute per token. As an open-weight model, its running cost is your own hardware rather than a per-token fee.
The bottom line for this matchup
The defining split here is open vs. closed. Qwen3.6 35B A3B gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. MAI-1-preview gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.
Frequently asked questions
Is MAI-1-preview or Qwen3.6 35B A3B better for coding?
Public SWE-Bench figures are not available for MAI-1-preview, so the honest test is your own repository — run an identical real bug through both. By design, MAI-1-preview leans toward microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai while Qwen3.6 35B A3B leans toward extreme sparsity — only 3b of 35b parameters active per token, giving near-3b inference cost, and that positioning usually predicts which feels better on your codebase.
Which is cheaper, MAI-1-preview or Qwen3.6 35B A3B?
Qwen3.6 35B A3B is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while MAI-1-preview is API-metered at Not published. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.
Which has the bigger context window?
Qwen3.6 35B A3B — 256K vs 128K, about 2× larger. Useful only if the model actually reasons over the full window, which not all do.
Can I use both MAI-1-preview and Qwen3.6 35B A3B together?
Yes — a multi-model platform like LumiChats gives you MAI-1-preview, Qwen3.6 35B A3B and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.
Which is newer, MAI-1-preview or Qwen3.6 35B A3B?
Qwen3.6 35B A3B — released April 16, 2026, about 8 months after MAI-1-preview.
MAI-1-preview vs Qwen3.6 35B A3B
Microsoft · US | Alibaba · China · Updated June 2026
Quick verdict
Pick MAI-1-preview for microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai or ranked in the top 15 on lm arena at launch. Pick Qwen3.6 35B A3B for extreme sparsity — only 3b of 35b parameters active per token, giving near-3b inference cost or runs at roughly 120 tokens per second on a single 24gb consumer gpu. Choose Qwen3.6 35B A3B if you need self-hosting or data privacy; MAI-1-preview if you want a managed API.
MAI-1-preview (Microsoft, US) and Qwen3.6 35B A3B (Alibaba, China) line up two different AI ecosystems against each other — a comparison that is as much about cost philosophy and openness as raw capability. MAI-1-preview is microsoft's first fully in-house foundation model - a strategic break from sole reliance on OpenAI, trained on ~15,000 H100 GPUs. Qwen3.6 35B A3B is a sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware. They diverge most on context window and open vs. closed weights — each quantified below from the models' real specs.
Key differences at a glance
▸Cost model: Qwen3.6 35B A3B ships open weights you can self-host (hardware cost only, no per-token fee), while MAI-1-preview is API-metered at Not published. Your choice depends on whether you want zero marginal cost at the price of running infrastructure.
▸Context window: Qwen3.6 35B A3B holds 2× more — 256K (~393 pages) vs 128K (~192 pages). But effective recall usually fades long before the advertised ceiling, so the bigger number only helps if the model reasons over it.
▸Recency: Qwen3.6 35B A3B is the newer model by about 8 months (released April 16, 2026), usually meaning fresher training data and capabilities.
▸Ecosystem: this is a US-vs-China matchup — they differ in pricing philosophy, data-residency options, and tooling ecosystems, not only benchmarks.
Side-by-side specs
Spec
MAI-1-preview
Qwen3.6 35B A3B
Provider
Microsoft (US)
Alibaba (China)
Released
August 28, 2025
April 16, 2026
Context window
128K (~192 pages)
256K (~393 pages)
Price (in/out)
Not published
Open weight (self-host / free)
Open weight?
No — API only
Yes — self-hostable
Modalities
text, code
text, image, code
SWE-Bench Verified
Not published
73.4%
MRCR v2 @ 1M
Not published
Not published
Who wins what
Microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI
MAI-1-preview
MAI-1-preview lists microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI among its strengths; Qwen3.6 35B A3B does not.
Ranked in the top 15 on LM Arena at launch
MAI-1-preview
MAI-1-preview lists ranked in the top 15 on LM Arena at launch among its strengths; Qwen3.6 35B A3B does not.
Trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment
MAI-1-preview
Qwen3.6 35B A3B is comparatively weak here — its SWE-Bench score comes from Alibaba's internal scaffold rather than the standard public harness
Extreme sparsity — only 3B of 35B parameters active per token, giving near-3B inference cost
Qwen3.6 35B A3B
Its 256K window holds about 2× more than MAI-1-preview's 128K in a single prompt.
Runs at roughly 120 tokens per second on a single 24GB consumer GPU
Qwen3.6 35B A3B
A sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware — and it carries the larger 256K context.
Apache 2.0 weights with a 256K native context, extensible to about 1M via YaRN
Qwen3.6 35B A3B
A sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware — and its weights are open while MAI-1-preview is API-only.
Largest single-prompt input
Qwen3.6 35B A3B
Its 256K window is about 2× larger than MAI-1-preview's 128K, fitting roughly 393 pages in one prompt.
Which should you pick?
Someone analysing very long documents or codebases
→ Qwen3.6 35B A3B
Larger 256K window fits more in one prompt.
A team with data-privacy or self-hosting needs
→ Qwen3.6 35B A3B
Open weights let you run it on your own hardware; MAI-1-preview is API-only.
Anyone whose priority is microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai
→ MAI-1-preview
It is specifically built for that.
Anyone whose priority is extreme sparsity — only 3b of 35b parameters active per token, giving near-3b inference cost
→ Qwen3.6 35B A3B
That is its strongest area.
An enterprise with regional data-residency rules
→ MAI-1-preview or Qwen3.6 35B A3B
Origin (US vs China) affects where data is processed and which compliance regime applies — check the provider's terms for your region.
MAI-1-preview: where it fits
Microsoft's first fully in-house foundation model - a strategic break from sole reliance on OpenAI, trained on ~15,000 H100 GPUs. Released August 28, 2025 by Microsoft, it is built for microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI, ranked in the top 15 on LM Arena at launch, trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment, and rolled into Copilot alongside OpenAI models, giving Microsoft a real second option.
Its trade-offs are real: a 'preview' release, not yet positioned as Microsoft's primary Copilot model, no public per-token API pricing - not sold as a standalone product, and distinct from Microsoft's later MAI-Thinking-1 reasoning model - an earlier, more general-purpose entry.
Qwen3.6 35B A3B: where it fits
A sparse 35B mixture-of-experts running on 3B active parameters — strong agentic coding at near-3B cost on consumer hardware. Released April 16, 2026 by Alibaba, it is built for extreme sparsity — only 3B of 35B parameters active per token, giving near-3B inference cost, runs at roughly 120 tokens per second on a single 24GB consumer GPU, apache 2.0 weights with a 256K native context, extensible to about 1M via YaRN, and preserves its reasoning across turns, which cuts the overhead of agentic loops.
Its trade-offs: loses to its smaller dense sibling Qwen3.6 27B on every coding benchmark, despite more total parameters, its SWE-Bench score comes from Alibaba's internal scaffold rather than the standard public harness, and all 35B parameters must stay resident in VRAM even though only 3B compute per token. As an open-weight model, its running cost is your own hardware rather than a per-token fee.
The bottom line for this matchup
The defining split here is open vs. closed. Qwen3.6 35B A3B gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. MAI-1-preview gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.
Want both MAI-1-preview and Qwen3.6 35B A3B without two subscriptions? LumiChats gives you these plus 40+ models under one ₹69/day pass (about $1/day) — draft with one, cross-check with the other.
Is MAI-1-preview or Qwen3.6 35B A3B better for coding?
Public SWE-Bench figures are not available for MAI-1-preview, so the honest test is your own repository — run an identical real bug through both. By design, MAI-1-preview leans toward microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai while Qwen3.6 35B A3B leans toward extreme sparsity — only 3b of 35b parameters active per token, giving near-3b inference cost, and that positioning usually predicts which feels better on your codebase.
Which is cheaper, MAI-1-preview or Qwen3.6 35B A3B?
Qwen3.6 35B A3B is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while MAI-1-preview is API-metered at Not published. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.
Which has the bigger context window?
Qwen3.6 35B A3B — 256K vs 128K, about 2× larger. Useful only if the model actually reasons over the full window, which not all do.
Can I use both MAI-1-preview and Qwen3.6 35B A3B together?
Yes — a multi-model platform like LumiChats gives you MAI-1-preview, Qwen3.6 35B A3B and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.
Which is newer, MAI-1-preview or Qwen3.6 35B A3B?
Qwen3.6 35B A3B — released April 16, 2026, about 8 months after MAI-1-preview.
Specifications and benchmarks reflect publicly reported figures as of June 2026 and may change as providers release updates. Always verify on your own workload.