Snapshot Β· 2026-06-03

State of Local AI

Comprehensive, multi-source analysis of the current best open-weights models and the hardware to run them on, as of mid-2026. Each chapter answers one question: which model is best for coding and agents, which hardware fits each budget from $1,500 to $50,000, when 27/35B stops being enough and a 256 GB or 512 GB cluster becomes the next step, where AMD and Apple compete with NVIDIA, and how electricity factors into a 5-year ownership cost.

New to local AI? Read our beginner's guide first β€” the hardware, the software, and your first model in plain language.

The threshold and the fork β€” MoE vs Dense

Qwen 3.6-27B β€” a 27B dense model from Alibaba, comfortable in 20 GB at Q4 β€” posts SWE-Bench Verified 77.2, Terminal-Bench 2.0 59.3, and LiveCodeBench 80.4. Closed-API peers score in the high 70s to mid-80s on the same axes. Six months ago this gap was a chasm; today it's narrow enough that for IDE-integrated coding, autonomous agent loops, and personal assistants, a used RTX 3090 is a primary platform, not a budget compromise.

The catch: open-weights LLMs come in two architectures with completely different hardware appetites, and "the best model" is two different models depending on which you buy for. Dense models β€” Qwen 3.6-27B, Mistral Medium 128B, the bulk of two years of local AI β€” engage every parameter on every token. They want bandwidth and tensor throughput; an RTX 5090 with 1.8 TB/s of GDDR7 is built for them. Mixture-of-Experts (MoE) models β€” DeepSeek V4-Pro at 1.6 T total, Kimi K2.6 at 1 T, gpt-oss-120B β€” route each token to a small "active" subset while keeping the rest resident in memory. They want capacity at modest bandwidth: 128 GB of LPDDR5X on a Strix Halo, 256 GB pooled across two DGX Sparks, multi-card pools. Same $5,000 budget, very different hardware.

Where the balance sits today: dense narrowly leads on every benchmark an open-weights MoE under 128 GB can run. Frontier MoE models still beat dense in absolute terms, but they need 600-900 GB of VRAM, which puts them in data-center territory. For the consumer and prosumer tiers this page covers, dense wins by default.

How we got here

A year ago this page would have read the other way. Qwen 3's flagship was a 122B-A10B MoE that ran cleanly on a 128 GB Strix Halo or DGX Spark and beat the same vendor's 27B dense across the board β€” "stretch to 128 GB unified memory" was real advice for the model-quality gain alone. Qwen 3.6 changed two things at once. The new dense scored noticeably higher than its predecessors; the new consumer-fitting MoE shrank to 35B-A3B (35 billion total, 3 billion active). The smaller MoE still edges the prior-generation 80 GB on coding and agent benchmarks despite using a quarter the memory β€” but trails the same-generation 27B dense by roughly four points on every axis. No larger Qwen 3.6 MoE has shipped to fill the 80 GB tier, which leaves a unified-memory buyer running prior-generation Qwen 3.5 for best-in-class MoE.

  1. MoE edge Β· slight

    Qwen 3 era (pre-2026-04)

    Qwen 3 122B-A10B MoE outperformed the same-vendor 27B-class dense on coding and agents while remaining deployable on 96-128 GB unified-memory builds. 10 B active params gave it real per-token compute on Strix Halo / DGX Spark. High-memory MoE builds had a clear quality edge over dense-only consumer GPU builds at the same price tier.

  2. Dense edge Β· slight

    Qwen 3.6 era (2026-04 onward)

    Qwen 3.6 shipped a strong 27B dense (SWE-V 77.2, TB2 59.3, MMLU-Pro 86.2) and a much smaller consumer-fitting MoE β€” 35B total with only 3 B active params (down from Qwen 3's 122B-A10B's 10 B active). The 22 GB Qwen 3.6-35B-A3B-MoE (SWE-V 73.4, TB2 51.5, LCB 80.4) actually edges the same-vendor prior-gen 80 GB 3.5-122B-A10B-MoE (SWE-V 72.0, TB2 49.4, LCB 78.9) on the coding/agents axes despite using 4Γ— less memory β€” the bigger MoE only wins MMLU-Pro and HLE by small margins. Net effect: dense gains a slight edge at the consumer-card tier AND the MoE upgrade path to unified-memory hardware (Strix Halo, DGX Spark, 128 GB GB10 OEMs) no longer unlocks a meaningfully better coding/agent MoE than a single 24 GB GPU. Frontier MoE (DeepSeek V4-Pro 80.6, Kimi K2.6 80.2) still leads in absolute terms but requires 600-900 GB to deploy.

The buyer takeaway: 128 GB unified memory doesn't currently unlock a better coding or agent model than 24 GB already runs. That doesn't make MoE-capable hardware a bad purchase β€” it shifts what you're buying it for. A Strix Halo or DGX Spark earns its keep on memory ceiling (running gpt-oss-120B locally instead of renting an H100), on power efficiency, and on documented scaling paths to bigger clusters. Just don't buy unified-memory hardware expecting the accessible-tier MoE to outclass Qwen 3.6-27B in 2026 β€” that's the wrong year.

What to run

Claude Code, OpenClaw, Hermes, Cline, and Aider all share the same coding-and-agent workflow shape. The picks below are the strongest open-weights model for that workflow on each side of the dense/MoE fork β€” same job, two columns, one of them for the hardware you actually own.

Dense

High-bandwidth consumer GPUs β€” RTX 5090, 4090, 3090, AMD R9700

Top pick

Qwen 3.6 27B (dense)

Top of both axes that matter for the unified Claude Code / OpenClaw / Hermes / Cline / Aider workflow: SWE-V 77.2 (essentially tied with Mistral Medium 128B's 77.6 at 4Γ— less VRAM) AND TB2 59.3 (only dense model below 200B with a defensible agent-driving score). Same model wins coding and agent driving β€” they're the same workflow.

Runner-up

Mistral Medium 3.5 128B

SWE-V 77.6 on a 128B dense β€” strictly higher than Qwen 3.6-27B on coding but TB2 not measured and needs 80 GB VRAM. The Pro 6000 Blackwell / dual-5090 pick when dense coding quality is paramount and the agent-driving axis is secondary.

Fits in 24-32 GB VRAM

Qwen 3.6 27B (dense)

Same as `best` β€” vramMinQ4=20 GB fits a single 3090/4090/5090. The 'one consumer GPU' ceiling in the dense space for the unified coding/agent workflow.

Mixture-of-Experts

Large unified memory β€” Strix Halo, DGX Spark, multi-card workstations

Top pick

DeepSeek V4-Pro 1.6T (MoE)

Open-weights leader on both axes: SWE-V 80.6 (1.6T-MoE, 49B active) AND TB2 67.9 (top score across architectures). LiveCodeBench 93.5 is also the highest open mark. Sustains tool-calling over long autonomous loops β€” the model frontier-class agent driving was designed for. Requires 900 GB to deploy.

Runner-up

Kimi K2.6 1T (MoE)

SWE-V 80.2, SWE-Pro 58.6 (top open mark on the harder coding bench), TB2 66.7 β€” within 1.2 pts of V4-Pro across the board. 1T-MoE with 32B active and 600 GB minimum β€” fits 8-H100 / 4-DGX Spark clusters where V4-Pro doesn't.

Fits in ≀ 128 GB unified memory

Qwen 3.6 35B-A3B (MoE)

Strongest MoE under 128 GB on both axes: SWE-V 73.4 + TB2 51.5 at vramMinQ4=22 GB. Edges the same-vendor prior-gen qwen3-5-122b-a10b-moe (vram 80, SWE-V 72.0, TB2 49.4) despite using 4Γ— less memory β€” the 128 GB unified-memory tier (Strix Halo, DGX Spark) does NOT currently unlock a better coding/agent MoE than the 22 GB pick. Its dense sibling (Qwen 3.6-27B, SWE-V 77.2 / TB2 59.3) still beats it β€” dense-edge framing holds.

Where to run it

A GPU or AI box has three knobs that matter for inference: total memory (how big a model fits), memory bandwidth (how fast weights can be re-read for every token, which sets tokens-per-second on decode), and TFLOPS / raw compute (which sets prompt-processing speed β€” how fast the model reads your input before the first token comes out β€” and also matters for training). Newer cards quote that compute as FP8 (8-bit floating-point); older Ampere / RDNA3 / Apple cards only have an INT8 (integer) path β€” same 8-bit width, slightly different number format. Putting numbers on the split: a comparable-quality MoE (Qwen 3.5 122B-A10B vs Qwen 3.6 27B dense) needs roughly 4Γ— the total memory β€” you still have to hold all 122 B of weights β€” but only about one-third the bandwidth and one-third the compute per token, because only 10 B of those weights actually stream through the chip each step. So a dense build wants less memory but faster bandwidth and more compute; an MoE build wants 4Γ— the memory and can get by with bandwidth and compute that are roughly 3Γ— lower. That's why a Mac Studio or Strix Halo box with 128 GB of slow unified memory can punch above its weight on a 100B-class MoE, while a dual-RTX-5090 stack with fast memory but only 64 GB total is built for dense.

Hardware picks below are bracketed by price ceiling β€” not because $1,500 and $3,000 are sacred numbers, but because the tradeoff shape genuinely changes. Under $2,000 the dense card is the whole story and MoE just barely opens up on a single 32 GB Intel B70. Around $3,000 unified memory becomes affordable. At $5,000 the dense-vs-MoE choice is a real fork between two well-supported platforms. Above $10,000 you can reasonably have both. Each bracket shows the dense pick, the MoE pick, and the cross-vendor alternative beneath in plain prose β€” every named card links to its hardware page and its buy CTA.

Under $1,500

Dense

Single RTX 3090 (used) build $1.5k +16.7% Β· 20d 24 GB Β· 936 GB/s Β· 285 TOPS INT8

24 GB CUDA Ampere at the legendary used $1,500 price point β€” runs every dense 27B-class model at Q4 with 32K context. Mature CUDA stack means day-1 vLLM / llama.cpp / TRT-LLM compatibility, no software workarounds. Power: ~350 W under load (~$125/year at 8 h/day, $0.15/kWh). Extensibility: standard ATX PCIe β€” drop a second 3090 in for 48 GB at the $2.6k tier (rtx-3090-x2) when you outgrow this.

Best for: 27-32B dense @ Q4 (Qwen 3.6-27B, qwen3-coder-30b, qwen3-32b)

Buy on Amazon (used) Setup guide β†’

MoE

Single Intel Arc Pro B70 build $1.8k +5.9% Β· 20d 32 GB Β· 608 GB/s Β· 367 TOPS INT8

Single Intel Arc Pro B70 32 GB at $1,700 β€” the cheapest path to running a SOLAI-blessed MoE locally. 32 GB of GDDR6 fits Qwen 3.6-35B-A3B at Q4 (~18 GB weights + 8 GB KV cache @ 32K) with comfortable headroom. Power: ~220 W active β€” about 60 % of a 3090. ipex-llm SYCL kernels run the A3B routing well; expect ~25 tok/s decode. Extensibility: standard PCIe β€” drop in a second B70 for 64 GB at the $2.9k tier when you outgrow this.

Best for: 35B-A3B MoE @ Q4 (qwen3-6-35b-a3b)

Buy on Amazon Setup guide β†’

At ≀$1,500 you're choosing the cheapest viable single-card build. The mature pick: a used RTX 3090 24 GB β€” day-1 vLLM, TRT-LLM, ComfyUI, every CUDA-bound tool works out of the box, and 24 GB fits every 27B-class dense model at Q4. Stretching slightly over: Intel Arc Pro B70 32 GB trades software maturity for 33 % more VRAM β€” enough that Qwen 3.6-35B-A3B MoE fits at Q4, which makes this the cheapest MoE-capable build on the page (the unified-memory alternative, Strix Halo 128, doesn't start until $2,700). AMD R9700 32 GB is the fastest AMD-per-dollar option on RDNA4 + ROCm 7+. Pick the 3090 for zero software gaps; pick the B70 if you want MoE on the cheap and accept a 2-6 week lag on new-model launch-day support; pick the R9700 for AMD-on-RDNA4 throughput at the same memory tier.

Also worth considering at this budget

Under $3,000

Dense

Single RTX 4090 build $3.2k +28% Β· 20d 24 GB Β· 1008 GB/s Β· 661 TF FP8

24 GB Ada Lovelace at $2,500 β€” the dense sweet spot under $3k. Pushes Qwen 3.6-27B to Q5 via vLLM + Marlin with 32K context. Mature CUDA stack with day-1 vLLM / TRT-LLM. Power: ~410 W active (~$147/year at 8 h/day). Extensibility: standard ATX, dual-card path lives at the $5k tier β€” just plan PSU capacity (~1.2 kW for x2) at build time.

Best for: 27-32B dense @ Q5

Buy on Amazon Setup guide β†’

MoE

AMD Ryzen AI Max+ 395 (128 GB) $2.8k +3.7% Β· 20d 128 GB Β· 256 GB/s Β· 128 TOPS INT8

$2,700 buys 128 GB unified memory (96 GB usable) at 256 GB/s bandwidth β€” the cheapest MoE-capable build. Runs gpt-oss-120B at Q4 with 32K context (~47 tok/s) via Vulkan / ROCm llama.cpp. Power: ~120 W active β€” the most efficient build in the entire dataset, ~$43/year at 8 h/day (a third of what a 4090 costs to run). Extensibility: limited β€” RAM is soldered LPDDR5X, but you can chain two boxes over 10 GbE at the $5,500 'strix-halo-x2' tier to double the pooled memory.

Best for: 120B-class MoE @ Q4 (gpt-oss-120b, qwen3-6-35b-a3b)

Buy on Amazon Setup guide β†’

The first bracket where MoE becomes viable AND where vendor choice opens up. The dense path: RTX 4090 24 GB is the CUDA headline (~410 W, fast 27-32B Q5 decode), but AMD R9700 32 GB buys the same VRAM $500 cheaper on RDNA4 + ROCm 7, and AMD W7800 32 GB adds workstation-chassis warranty for the same memory tier. Intel Arc Pro B70 x2 64 GB is the cheapest path to 64 GB of dense VRAM if SYCL/ipex-llm fits your workflow. The MoE path: Strix Halo 128 is the headline unified-memory pick β€” runs 120B-class MoE at ~120 W, the lowest power bill of any build on the page. The B70 x2 also straddles the line β€” at 64 GB it fits Qwen 3.6-35B-A3B with room for a second concurrent agent, and it has a documented x4 / x8 upgrade path. Pick the 4090 if you want the dominant software stack; pick the R9700 or B70 x2 if you want more VRAM per dollar and can live with a younger ecosystem; pick Strix Halo if you want 120B-class MoE at minimal wattage.

Also worth considering at this budget

Under $5,000

Dense

Single RTX 5090 build $4.9k +28.6% Β· 20d 32 GB Β· 1792 GB/s Β· 838 TF FP8

Still the dense-tier pick β€” no consumer card between $3,500 and the Pro 6000 Blackwell at $10,500 unseats it. $5k headroom means a high-end host PC (PCIe 5.0, DDR5, 1 kW PSU) rather than a stretched mid-tier build. Power: ~520 W active (~$187/year at 8 h/day; jumps to ~$680/year if you run it 24/7). Extensibility: standard ATX β€” dual-5090 is the next step at the $7-10k tier with a 1.6 kW PSU.

Best for: 27-32B dense @ Q5/Q6 with quality host

Buy on Amazon Setup guide β†’

MoE

NVIDIA DGX Spark (128 GB) $4.7k 128 GB Β· 273 GB/s Β· 250 TF FP8

NVIDIA DGX Spark ($4,699) β€” reference of the GB10 family (128 GB LPDDR5x unified, 273 GB/s, 1 PFLOP FP4 Blackwell on ARM). ~51 tok/s on Qwen 3.5-122B-A10B at Q4 with day-1 vLLM / sglang / TRT-LLM. Power: ~240 W active β€” half a 5090's draw, ~$86/year at 8 h/day, $315/year at 24/7 (a noticeable saving vs a dense build). Extensibility: documented ConnectX-7 cluster path up to x8 ($42k for max-out). The GB10 family compressed in price recently (May 2026: DGX Spark $4,699, MSI EdgeXpert $4,599 Amazon, Dell Pro Max $4,061, Lenovo PGX $4,100, ASUS Ascent $3,499) β€” ASUS Ascent is the cheapest, DGX Spark gets first-party NVIDIA support.

Best for: 120B-class MoE on the CUDA stack

Buy on Amazon Setup guide β†’

The buyer-defining bracket β€” most consumer money lands here, and the architectural fork is real. The dense path: RTX 5090 32 GB for fastest decode in the consumer tier (520 W); AMD W7900 48 GB for 50 % more VRAM at slightly higher price (slower decode but better for 50K+ token agentic loops); RTX Pro 5000 Blackwell 48 GB (~$5.2K card, build lands at ~$7K) is the CUDA answer at the 48 GB dense tier β€” Blackwell NVFP4 + workstation warranty + 300 W draw (about half the 5090's wattage). Card price runs ~15 % above the W7900 48 GB; the full build sits about $2.5K higher once you add the workstation chassis, so it's the right pick when CUDA + NVFP4 matters more than the price gap. The MoE path forks three ways. CUDA-on-ARM: NVIDIA DGX Spark 128 GB β€” reference GB10, 128 GB unified, day-1 vLLM / sglang / TRT-LLM, ~51 tok/s on Qwen 3.5-122B-A10B at half a 5090's draw (240 W); the GB10 family extends down to $3,499 (ASUS Ascent) across MSI EdgeXpert / Dell Pro Max / Lenovo ThinkStation PGX clones. Pooled discrete VRAM: Intel Arc Pro B70 x4 gives you 128 GB of GDDR6 across 4 cards on the SYCL / ipex-llm stack (~50 tok/s on 120B MoE, 700 W) β€” and a 3-card configuration (~$4,300 build, 96 GB pooled) is the bracket-friendly variant for buyers who don't want the ARM platform or the CUDA lock-in. Apple Silicon unified memory: Mac Studio M3 Ultra 96 GB at $3,999 runs the same 120B-MoE workloads on 819 GB/s bandwidth (50 % more than M4 Max) at ~180 W silent β€” 80 GB usable fits 70B Q4 + 32K KV cache AND gpt-oss-120B MoE on a Metal / MLX stack that lags CUDA on day-one model support but covers every established model. Portable counterpart at the top of this bracket: MacBook Pro M5 Max 128 GB at $5,399 (16-inch, 40-core GPU, 614 GB/s) is the only sub-$10K build that fits in a backpack β€” runs 70-106B dense models at Q4 comfortably, and pairs over Thunderbolt 5 with a second unit for the 256 GB MoE step-up in the next chapter. Pick by workload and platform constraints: 5090 / W7900 for dense throughput; DGX Spark for CUDA-on-ARM MoE with the ConnectX-7 cluster upgrade path; Arc Pro B70 x3-x4 for x86 + standard PCIe + 96-128 GB pooled VRAM and a younger software stack; Mac Studio M3 Ultra 96 when silence + low-watt + Metal / MLX is the right tradeoff at 70B-class; MacBook Pro M5 Max 128 when portability matters.

Also worth considering at this budget

If 27/35B isn't enough β€” the 200-700B step-up

Qwen 3.6-27B and 35B-A3B cover most local-AI use cases, but two limits show up in practice. Long autonomous agent sessions β€” 30 minutes or more of tool-calling β€” plateau around 55-59 % on Terminal-Bench 2.0 and start losing context. And for reasoning, vision, or harder math, Qwen 3.6 trails frontier-class models by 10-15 points because it's sharpened for code and agents specifically. The next step up is a 200-700B Mixture-of-Experts (MoE) model. Two memory tiers cover the practical range β€” 256 GB of pooled memory for the 230-310B class, or 512 GB for the 400-754B class.

256 GB pool

256 GB β€” the 230-310B MoE class

Three current (June 2026) picks. All Q4-fit a 256 GB memory pool β€” hardware for that lives in the next chapter, around the $5,600 to $10,000 range.

512 GB pool

512 GB β€” the 400-754B MoE class

Three current (June 2026) picks. All need a 512 GB memory pool β€” hardware for that lives in the next chapter, around the $11,500 to $19,500 range.

More expensive builds β€” $10,000 and up

Past $10,000 the choice shape changes. Multi-card and cluster builds become the norm; dense and MoE both fit on the same machine; power draw, cooling, and a 30-amp circuit start factoring into the buy. The brackets below pair workstation-tier silicon with the workloads that justify the spend.

Under $10,000

Dense

Dual RTX 5090 build $10k +18.9% Β· 20d 64 GB Β· 1792 GB/s Β· 1.7 PF FP8

Dual RTX 5090 at $7,400 β€” 64 GB pooled Blackwell with vLLM tensor parallelism. The compute-tier workhorse: Qwen 3.6-27B dense at Q5 on a single card (fast), plus enough pooled VRAM to fit gpt-oss-120B MoE at Q4 via tensor parallel (~96 tok/s short-prompt; long-context number unverified). Power: ~1,050 W under load (needs a 1,600 W PSU). Extensibility: standard ATX-EVO chassis still has room for a third card later if you build with a 2 kW PSU and enough PCIe lanes from the start.

Best for: 27B dense single-card, or 120B-class MoE via tensor parallel

Buy on Amazon Setup guide β†’

MoE

2Γ— DGX Spark cluster (256 GB unified, CUDA) $10k 256 GB Β· 273 GB/s Β· 500 TF FP8

DGX Spark x2 at $9,500 β€” 256 GB pooled with TP=2. Runs MiniMax M2.7 230B MoE at Q5 (24 tok/s) or qwen3-235b MoE. The bridge between single-Spark and the 4-unit clusters. Power: ~460 W combined β€” less than HALF a dual-5090 build and ~$200/year cheaper to run 24/7 at $0.15/kWh. Extensibility: documented x2β†’x4β†’x8 ConnectX-7 cluster path is the easiest scale-out in the dataset.

Best for: 230B-class MoE

Buy on Amazon (2-pack DGX Spark) Setup guide β†’

Four legitimate paths at $7-10k. Dual RTX 5090 (~1,050 W) is the fastest dense build at this price β€” 64 GB pooled Blackwell, NVFP4-ready. AMD W7900 x2 96 GB trades raw decode speed for 50 % more VRAM at lower power (~720 W combined) β€” interesting if your work hits the 64 GB dense ceiling. Intel Arc Pro B70 x8 sits just over budget but unlocks 256 GB of SYCL-pool VRAM, the cheapest path to that memory tier. DGX Spark x2 (~460 W, less than half a dual-5090) doubles the MoE memory ceiling to 256 GB and unlocks 230B-class MoE. Dual-5090 wins for coding/agents on dense; DGX Spark x2 wins for long-context 230B-class MoE; W7900 x2 wins for max-VRAM dense work. If you can stretch $500-1,000 over budget, the single Pro 6000 Blackwell 96 ($10,500, see the $20k bracket) outclasses all of them for breadth.

Also worth considering at this budget

Under $20,000

Dense

Single RTX Pro 6000 Blackwell 96 GB build $12k +16.2% Β· 20d 96 GB Β· 1792 GB/s Β· 1.0 PF FP8

Single RTX Pro 6000 Blackwell 96 GB at $10,500 β€” the dense-and-MoE-both pick when budget allows the workstation card. 96 GB Blackwell on one card fits Qwen 3.6-27B at Q8 / FP16 with 128K context AND 120B-class MoE at Q4. Power: ~600 W under load β€” same as a 5090 but with 3Γ— the memory and an enterprise driver path. Extensibility: standard workstation chassis, dual-card upgrade lives at the $19,500 'rtx-pro-6000-blackwell-x2' tier when you outgrow this. Leaves ~$9,500 of the $20k budget for a beefy host (dual-EPYC, 256 GB RAM, fast NVMe, 2 kW PSU) which actually matters for long-context throughput.

Best for: 27-120B dense, single-card with workstation-grade host

Buy on Amazon Setup guide β†’

MoE

4Γ— DGX Spark cluster (512 GB unified, CUDA) $20k 512 GB Β· 273 GB/s Β· 1.0 PF FP8

DGX Spark x4 at $19,500 β€” 488 GB usable, TP=4. Runs qwen3-235b MoE comfortably at Q5 and DeepSeek V3 671B at Q4. NVIDIA's official CUDA-on-ARM cluster reference architecture. Power: ~920 W combined across 4 nodes (~$330/year at 8 h/day, ~$1,000/year at 24/7) β€” significantly less than a comparable 4-GPU dense workstation. Extensibility: the cluster is documented up to 8 units (dgx-spark-x8 at $42k); add one more Spark + ConnectX-7 cable when you need it.

Best for: 235-671B MoE

Buy on Amazon (4Γ— DGX Spark) Setup guide β†’

At $20k the NVIDIA workstation tier opens up cleanly. Pro 6000 Blackwell 96 GB (single) is the dense reference for AI labs and serious solo developers β€” half-the-bracket cost means more budget for a strong host build (dual-EPYC, 256 GB RAM, fast NVMe, 2 kW PSU), and the Pro 6000 Blackwell x2 is the natural upgrade when you outgrow it. AMD doesn't have a direct equivalent in the dataset at this tier β€” W7900 x2 is the closest but sits in the $10k bracket, and AMD's CDNA Instinct cards (MI300X / MI325X) are B2B-only via Supermicro / Dell PowerEdge channels. DGX Spark x4 (~920 W) is the MoE cluster reference for 235-671B deployment β€” significantly less power than a quad-Blackwell workstation, with documented x8 expansion. Either is a multi-year platform. Choose Pro 6000 if your work spans dense coding/agent β†’ image/video generation (ComfyUI at FP16 fits comfortably). Choose DGX Spark x4 if your work is research-scale MoE where the alternative is renting H100s.

Also worth considering at this budget

Under $50,000

Dense

Quad RTX Pro 6000 Blackwell build (384 GB) $38k 384 GB Β· 1792 GB/s Β· 4.0 PF FP8

Quad RTX Pro 6000 Blackwell at $38,000 β€” 384 GB pooled at 1,792 GB/s per card, no NVLink so tensor-parallel is PCIe-bandwidth-bound. The fast-MoE workhorse at $50K: DeepSeek V4-Flash (284B, 13B active, 192 GB at Q4) fits with ~180 GB to spare for KV cache and concurrent agent slots, and 13B active params decode quickly over Blackwell's bandwidth β€” the build clocks 145 tok/s on a 235B MoE benchmark, V4-Flash's sparser routing decodes faster still. Benchmarks: SWE-Bench Verified 79, LiveCodeBench 91.6, Terminal-Bench 2.0 56.9 β€” within 1.6 points of V4-Pro on every coding/agent axis at a fraction of the memory footprint. Power: ~2,200 W under load β€” needs a dedicated 30-amp circuit and a Threadripper Pro / Xeon W host for the PCIe lane count. Extensibility: still workstation form factor (4U pedestal), with [Pro 6000 Blackwell x8](rtx-pro-6000-blackwell-x8) ($78k) as the natural next step when the chassis fills up β€” that's where 'workstation' ends and 'server' begins.

Best for: DeepSeek V4-Flash 284B-A13B at Q4 (fast MoE, 192 GB)

Buy on Amazon Setup guide β†’

MoE

8Γ— DGX Spark cluster (1024 GB unified, CUDA) $44k 1024 GB Β· 273 GB/s Β· 2.0 PF FP8

DGX Spark x8 at $43,500 β€” 976 GB usable across 8 GB10 nodes on ConnectX-7 200 GbE, the documented cluster ceiling for the GB10 family. Fits the open-weights frontier comfortably: Kimi K2.6 (1T total, 32B active, 600 GB at Q4 NVFP4) is the recipe primary at ~18 tok/s with Eagle3 speculative decoding β€” SWE-Bench Verified 80.2, SWE-Pro 58.6 (top open-weights mark on the harder coding bench), Terminal-Bench 2.0 66.7. DeepSeek V4-Pro 1.6T at Q4 is the alternate β€” 900 GB weights leave 76 GB for KV cache, viable but tight; V4-Pro wins raw benchmarks (SWE-V 80.6, LiveCodeBench 93.5, TB2 67.9). Decode is bandwidth-bound across the cluster fabric β€” 1T-class MoE sustains ~13-18 tok/s, optimal for deep autonomous loops where total capability matters more than per-token latency. Power: ~1,840 W combined β€” roughly half the draw of a comparable 8-Blackwell workstation. Extensibility: this IS the ceiling β€” beyond 8 nodes you're moving into rack territory and a real 200 GbE switch (NVIDIA SN5400 $25k, MikroTik $3-8k per the build's cons).

Best for: Kimi K2.6 1T-A32B (primary) / DeepSeek V4-Pro 1.6T-A49B (alternate) β€” frontier MoE

Buy on Amazon (8Γ— DGX Spark) Setup guide β†’

At $50K both winning picks are MoE β€” the fork is fast MoE vs frontier 1T-class, not dense vs MoE. Dense workloads (Qwen 3.6-27B, Mistral Medium 128B) top out at quality below $20K; at $50K nothing dense wins decisively against open-weights MoE on coding/agent benchmarks. Pro 6000 Blackwell x4 runs DeepSeek V4-Flash at high decode speed on Blackwell's 1.79 TB/s/card bandwidth β€” best when the agent loop is tight and a human is waiting (Cline, Aider, Claude Code editing sessions). The natural step up from the Pro 6000 Blackwell x2 at the $20k bracket, 4Γ— the memory of the single-card pick, same CUDA stack. DGX Spark x8 runs Kimi K2.6 or V4-Pro at ~13-18 tok/s β€” best when the model is driving deep autonomous work and per-token latency matters less than the +1-3 point benchmark edge frontier MoE delivers (SWE-Pro 58.6 on K2.6, LiveCodeBench 93.5 on V4-Pro). Three sidesteps land here. H200 141 GB workstation is the research-card pick β€” Hopper HBM3e at 4,800 GB/s, required for training experiments and certain inference paths the Blackwells can't touch (FlashAttention 3, NCCL multi-node). Two turnkey appliances: TinyBox v2 bundles 4Γ— RTX 5090 Blackwell into a pre-integrated box, TinyBox Pro bundles 8Γ— RTX 4090 β€” pay the integration tax, skip three weeks of cabling and firmware roulette. AMD's frontier cards (MI325X 256 GB CDNA3 and MI355X 288 GB CDNA4) remain B2B-only via Supermicro / Dell PowerEdge channels (same caveat the $20k bracket flags). Above $50K you're in real datacenter territory β€” H100 x8, H200 x8, B200 x8 reference platforms β€” out of scope for this page.

Also worth considering at this budget

Where AMD, Intel, and Apple can challenge NVIDIA dominance

The brackets above lead with NVIDIA because CUDA's day-1 software support (vLLM, sglang, TensorRT-LLM, ComfyUI nodes, FlashAttention 3) still beats ROCm, SYCL, and Metal/MLX on every new-model launch by two to six weeks. But that lead doesn't translate to wins at every memory tier. AMD's RDNA4 / RDNA3 workstation lineup gives you roughly 50 % more VRAM per dollar above $2,000; Intel's Arc Pro B70 is the cheapest 32 GB card on the market; and Apple's M-series Mac Studio is the quietest large-unified-memory build at every tier β€” 96 GB at $3,999, 256 GB at $7,999, 512 GB at $14,199 (the last two are refurb / used only since Apple's mid-2026 configurator pull). For established models running through llama.cpp, vLLM, or MLX, all three work. The friction is on bleeding-edge releases and on niche stacks (training, multi-modal, certain ComfyUI custom nodes) where ROCm, SYCL, and Metal/MLX lag.

At the 48 GB dense tier, NVIDIA's RTX Pro 5000 Blackwell (~$4,500) is the direct CUDA answer to the AMD W7900 48 GB at the same price β€” full CUDA + NVFP4 + the workstation chassis warranty, with the FP4 tensor cores the W7900 lacks. For a buyer who needs 48 GB of VRAM and is on the CUDA stack, it's the right pick at this tier.

Apple's edge is at the upper-memory tiers and on noise / watts: an M3 Ultra Mac Studio runs gpt-oss-120B silently at ~180 W where a dual-5090 build pulls 1 kW with audible fans. The Metal / MLX stack covers every established open-weights model with first-class quantization support, but lags 2-6 weeks on day-one launches and skips most ComfyUI custom nodes. The 256 GB / 512 GB SKUs going refurb-only (per Apple's mid-2026 configurator pull, see "What can change the picture" below) means the upper Apple tiers are now a used-market play rather than an Apple-direct purchase.

The two costs that don't show up on the sticker

Sticker price isn't the whole spend. Two factors compound over the years you'll own a build, and at the upper end of the dataset they swing the answer between otherwise-tied picks.

Electricity. A dual-RTX-5090 box pulls about 1 kW under load β€” at $0.15/kWh that's roughly $1,400 a year running 24/7. A DGX Spark at 240 W costs $315 in the same scenario. Over a three-year build cycle, $3,000 swing on the same workload. Even at an eight-hours-a-day load it's $683 versus $105. The Spark and Strix Halo are dramatically more efficient than dense-GPU equivalents at every tier, and the gap widens at cluster scale: a quad-Spark's 920 W stays well below a four-Blackwell workstation's 2 kW-plus.

BuildActive W8 h/day24/7
Strix Halo 128~120 W$53/yr$158/yr
Mac M4 Max 128~130 W$57/yr$171/yr
Mac M3 Ultra 96~180 W$79/yr$237/yr
DGX Spark (GB10)~240 W$105/yr$315/yr
RTX 3090~350 W$153/yr$460/yr
RTX 4090~410 W$180/yr$540/yr
DGX Spark x2~460 W$201/yr$604/yr
RTX 5090~520 W$228/yr$683/yr
RTX Pro 6000 Blackwell~600 W$263/yr$788/yr
DGX Spark x4~920 W$403/yr$1,209/yr
RTX 5090 x2~1,050 W$460/yr$1,380/yr
RTX Pro 6000 Blackwell x2~1,100 W$482/yr$1,445/yr
DGX Spark x8~1,840 W$806/yr$2,418/yr
RTX Pro 6000 Blackwell x4~2,200 W$964/yr$2,891/yr

Cost per token over 5 years. Watts Γ— time only matter relative to tokens generated β€” and the tokens-per-second a build sustains depends on which model is running on it. A Pro 6000 doing Qwen 3.6-27B and a Pro 6000 doing Kimi K2.6 spend the same watts on workloads with an order-of-magnitude throughput gap. So we split by model-size tier, list the builds that can run that model at Q4 / NVFP4, divide each build's 5-year 24/7 electricity bill ($0.15/kWh) by its 5-year token output at the listed TPS, and compare against OpenRouter's median output rate. TPS values are normalized to ~32K context single-stream decode (the realistic agent workload, not 4K-prompt cherry-picks); the dataset's 120b_moe column in db.json tracks Qwen3.5-122B-A10B β€” the open 120B-class MoE these boxes actually run β€” and supplies each build's figure, with the DGX Spark's own first-party number at ~51 t/s. Electricity only β€” no host PC, no idle, no hardware amortization.

27-35B class β€” Dense (Qwen 3.6-27B at Q4, β‰ˆ 20 GB)

BuildActive WTPS5y $/Mtok @ 24/7
RTX Pro 6000 Blackwell~600 W~85 t/s$0.29
RTX 5090~520 W~100 t/s$0.22
RTX 4090~410 W~42 t/s$0.41
RTX 3090~350 W~28 t/s$0.52
OpenRouter median output (Qwen 3.6-27B providers)~$0.30/Mtok

27-35B class β€” MoE (Qwen 3.6-35B-A3B at Q4, β‰ˆ 22 GB)

BuildActive WTPS5y $/Mtok @ 24/7
Strix Halo 128~120 W~40 t/s$0.13
RTX Pro 6000 (FP8 + MTP)~600 W~170 t/s$0.15
Mac M3 Ultra 96~180 W~48 t/s$0.16
Mac M4 Max 128~130 W~31 t/s$0.17
DGX Spark (GB10)~240 W~50 t/s$0.20
OpenRouter median output (Qwen 3.6-35B-A3B providers)~$0.30/Mtok

~120B MoE β€” Qwen3.5-122B-A10B at Q4 (β‰ˆ 67 GB)

BuildActive WTPS5y $/Mtok @ 24/7
Strix Halo 128~120 W~47 t/s$0.11
RTX Pro 6000~600 W~190 t/s$0.13
Mac M3 Ultra 96~180 W~55 t/s$0.14
Mac M4 Max 128~130 W~35 t/s$0.15
RTX Pro 6000 x2~1,100 W~280 t/s$0.16
DGX Spark (GB10)~240 W~51 t/s$0.20
DGX Spark x2~460 W~90 t/s$0.21
RTX 5090 x2 (tight 64 GB fit)~1,050 W~96 t/s$0.46
OpenRouter median output (Qwen3.5-122B-A10B providers)~$2.50/Mtok

230-400B MoE β€” Qwen3-235B-A22B at Q4 (β‰ˆ 150 GB)

BuildActive WTPS5y $/Mtok @ 24/7
Mac M3 Ultra 256 (refurb)~180 W~22 t/s$0.34
RTX Pro 6000 (offload)~600 W~50 t/s$0.50
RTX Pro 6000 x2~1,100 W~90 t/s$0.51
RTX Pro 6000 x4~2,200 W~145 t/s$0.63
DGX Spark x2~460 W~24 t/s$0.80
DGX Spark x4~920 W~32 t/s$1.20
DGX Spark x8~1,840 W~42 t/s$1.83
OpenRouter median output (Qwen3-235B / MiniMax M2.7 providers)~$1.20/Mtok

1T+ frontier MoE β€” Kimi K2.6 / DeepSeek V4-Pro NVFP4 (β‰ˆ 600-900 GB)

BuildActive WTPS5y $/Mtok @ 24/7
DGX Spark x8 (Kimi K2.6 NVFP4)~1,840 W~18 t/s$4.26
OpenRouter median output (DeepSeek V4-Pro / Kimi K2.6 providers)~$2.50/Mtok

Takeaway. The break-even isn't the model size β€” it's the model-to-hardware fit. Dense 27B on discrete VRAM roughly ties the OpenRouter rate: a Pro 6000 clears $0.29/Mtok and an RTX 5090 with NVFP4 hits $0.22, both just under the ~$0.30 API; older 3090/4090 lose. The same model size as MoE (Qwen 3.6-35B-A3B with 3 B active params) compresses the spread but Strix Halo's very low wattage wins at $0.13/Mtok, with Pro 6000 (NVFP4 + MTP) at $0.15 and Mac M3 Ultra at $0.16 β€” all roughly half the API rate. 120B MoE (Qwen3.5-122B-A10B) is where local wins most decisively: Strix Halo $0.11, Pro 6000 $0.13, Mac Studios $0.14-$0.15, all well over 10Γ— under the ~$2.50 API rate, which runs high because the model is newly listed and thinly hosted. 230-400B MoE still favors local on the right hardware (Mac M3 Ultra 256 at $0.34, Pro 6000 family $0.50-$0.63 vs ~$1.20 API) but multi-Spark clusters ($0.80-$1.83) drift toward or past the API rate. 1T+ frontier MoE inverts the picture: Spark x8 on Kimi K2.6 costs $4.26/Mtok in electricity alone vs ~$2.50 API. Two caveats: hardware amortization adds to local cost but caps at zero marginal once paid while the API scales linearly with use forever; and OpenRouter rates above are rough community-provider medians as of 2026, fluctuating Β±50 % week-to-week β€” check live pricing before any TCO call.

What happens when you outgrow the build. Standard ATX workstations from a 3090 to a Pro 6000 Blackwell let you drop in a second card and a bigger PSU. The DGX Spark family scales differently but as cleanly β€” NVIDIA documents an x1 β†’ x2 β†’ x4 β†’ x8 ConnectX-7 cluster path; add a box and a $200 cable. Strix Halo chains two units over 10 GbE for 256 GB pooled at the $5,500 tier. Apple Silicon and tinybox don't scale at all: you buy the size you'll need at the end or you replace the build. Combine this with the electricity column and you'll see why DGX Spark x2 at $9,500 routinely outperforms dual-RTX-5090 at $7,400 over a three-year window β€” same daily work, less than half the watts, and a documented next step instead of a wall.

What can change the picture

The "dense narrowly leads" call holds until one of two things changes: a stronger consumer-fitting MoE ships, or memory-rich silicon gets cheap enough to make 256 GB consumer builds routine again. The first is plausible on a 6-12 month horizon; the second isn't.

A Qwen 3.6-class 80B-A12B MoE β€” fitting on Strix Halo or a single DGX Spark, with roughly the same active-parameter compute as the current dense 27B β€” would close the gap and probably edge past it. Watch the Qwen, DeepSeek, and Moonshot release windows; the Qwen 3 β†’ Qwen 3.6 transition that flipped MoE-edge to dense-edge took about six months, and the next flip is likely on a similar cadence.

The hardware side is moving the wrong way. Apple discontinued the Mac Studio M3 Ultra 256 GB and 512 GB configurations earlier this year; MSI EdgeXpert's Amazon street price moved from $2,999 at launch to $4,599 today; NVIDIA raised DGX Spark MSRP from $3,999 to $4,699. HBM3E and DDR5-X supply remains tight from data-center demand. The realistic 2026 question isn't "when does 256 GB drop to $2,500" β€” it's whether memory pressure eases enough for OEM partners to keep shipping the bigger configurations at current pricing. That's a 12-24 month read, which means the model-side flip will almost certainly arrive first.

We refresh this snapshot every two weeks. The picture moves when a new model lands or a market data point flips β€” not on a calendar.

Why is local AI booming

Setup recipes by build

Each hardware page below has the recipe β€” model file to download, quantization, the runtime to install, the exact launch command, and what tok/s to expect at 32K+ context. Pick your hardware, follow the recipe.

Methodology. Model picks come from per-workload benchmark leaderboards (SWE-Bench Verified, Terminal-Bench 2.0, LiveCodeBench, MMLU-Pro, HLE). Hardware picks draw on community-verified prices, bandwidth, software-stack maturity, active power draw, and documented expansion paths. Every claim cites a URL on the underlying build or model page. Snapshot version 2026-06-03.

Prices on this page adjust to the region selected in the site header (top-right region chip). Budget brackets convert from USD using live FX rates plus regional VAT or tax where applicable; per-build prices use vendor-confirmed local prices when available, falling back to FX conversion otherwise.