Command A+ vs MAI-1-preview

Cohere · Canada  |  Microsoft · US · Updated June 2026

Quick verdict

Pick Command A+ for cohere's newer, more efficient flagship - runs on just two h100 gpus, unusually lean for a 218b-parameter model or a 218b-total/25b-active moe released with open weights (apache 2.0) on hugging face. 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. Choose Command A+ if you need self-hosting or data privacy; MAI-1-preview if you want a managed API.

Command A+ (Cohere, Canada) and MAI-1-preview (Microsoft, US) line up two different AI ecosystems against each other — a comparison that is as much about cost philosophy and openness as raw capability. Command A+ is cohere's newer, leaner flagship - a 218B open-weight MoE tuned for efficiency (just two GPUs to run) and 48-language support. 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. They diverge most on context window and open vs. closed weights — each quantified below from the models' real specs.

Key differences at a glance

Side-by-side specs

SpecCommand A+MAI-1-preview
ProviderCohere (Canada) Microsoft (US)
ReleasedMay 19, 2026 August 28, 2025
Context window256K (unconfirmed) (~384 pages) 128K (~192 pages)
Price (in/out)Open weight (self-host / free) Not published
Open weight?Yes — self-hostable No — API only
Modalitiestext, code text, code
SWE-Bench VerifiedNot published Not published
MRCR v2 @ 1MNot published Not published

Who wins what

Cohere's newer, more efficient flagship - runs on just two H100 GPUs, unusually lean for a 218B-parameter model

Command A+

MAI-1-preview is comparatively weak here — a 'preview' release, not yet positioned as Microsoft's primary Copilot model

A 218B-total/25B-active MoE released with open weights (Apache 2.0) on Hugging Face

Command A+

Open weights make this possible at all — MAI-1-preview is API-only, so it cannot leave the vendor's servers.

Supports 48 languages, including all official EU languages

Command A+

Cohere's newer, leaner flagship - a 218B open-weight MoE tuned for efficiency (just two GPUs to run) and 48-language support — and it carries the larger 256K (unconfirmed) context.

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; Command A+ 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; Command A+ does not.

Trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment

MAI-1-preview

MAI-1-preview lists trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment among its strengths; Command A+ does not.

Largest single-prompt input

Command A+

Its 256K (unconfirmed) window is about 2× larger than MAI-1-preview's 128K, fitting roughly 384 pages in one prompt.

Which should you pick?

Someone analysing very long documents or codebases

Command A+

Larger 256K (unconfirmed) window fits more in one prompt.

A team with data-privacy or self-hosting needs

Command A+

Open weights let you run it on your own hardware; MAI-1-preview is API-only.

Anyone whose priority is cohere's newer, more efficient flagship - runs on just two h100 gpus, unusually lean for a 218b-parameter model

Command A+

It is specifically built for that.

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

That is its strongest area.

An enterprise with regional data-residency rules

MAI-1-preview or Command A+

Origin (Canada vs US) affects where data is processed and which compliance regime applies — check the provider's terms for your region.

Command A+: where it fits

Cohere's newer, leaner flagship - a 218B open-weight MoE tuned for efficiency (just two GPUs to run) and 48-language support. Released May 19, 2026 by Cohere, it is built for cohere's newer, more efficient flagship - runs on just two H100 GPUs, unusually lean for a 218B-parameter model, a 218B-total/25B-active MoE released with open weights (Apache 2.0) on Hugging Face, supports 48 languages, including all official EU languages, and positioned by Cohere as its 'most efficient and performant model to date'.

Its trade-offs are real: no official context window or per-token price published yet - both are estimated/unavailable, newer release with less independent benchmark verification than established flagships, and enterprise/multilingual focus rather than topping general reasoning leaderboards. As an open-weight model, its running cost is your own hardware rather than a per-token fee.

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: 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.

The bottom line for this matchup

The defining split here is open vs. closed. Command A+ 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 Command A+ and MAI-1-preview 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.

See pricing

Frequently asked questions

Is Command A+ or MAI-1-preview better for coding?

Public SWE-Bench figures are not available for either model, so the honest test is your own repository — run an identical real bug through both. By design, Command A+ leans toward cohere's newer, more efficient flagship - runs on just two h100 gpus, unusually lean for a 218b-parameter model while MAI-1-preview leans toward microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai, and that positioning usually predicts which feels better on your codebase.

Which is cheaper, Command A+ or MAI-1-preview?

Command A+ 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?

Command A+ — 256K (unconfirmed) vs 128K, about 2× larger. Useful only if the model actually reasons over the full window, which not all do.

Can I use both Command A+ and MAI-1-preview together?

Yes — a multi-model platform like LumiChats gives you Command A+, MAI-1-preview 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, Command A+ or MAI-1-preview?

Command A+ — released May 19, 2026, about 9 months after MAI-1-preview.

Related comparisons

Specifications and benchmarks reflect publicly reported figures as of June 2026 and may change as providers release updates. Always verify on your own workload.