Best Open-Source Coding Model in 2026: Ranked by Cost

The best open-source coding model in 2026 depends on whether you optimize for cost or benchmark accuracy: Qwen3-Coder-Next is the cheapest fast option we measured at $0.00007072 per call, DeepSeek-V3.2 trades speed for a broader base model, and Kimi-Dev-72B leads on cited SWE-bench accuracy.

There is no single winner here, and any article that hands you one is skipping the tradeoff that actually decides this. An open-weight coding model is a language model whose weights are publicly released that you can self-host or reach through third-party routers instead of only a single vendor's API. That property is what lets independent hosts serve these models cheaply, and it is why the price you pay depends as much on routing as on the model. Below we rank three open-weight coding contenders on cost, speed, and the one benchmark figure that survives scrutiny, then show the numbers we actually measured.

Best open-source coding model, ranked (verified 2026-07)

The short version: two of these three we could call and time ourselves, and one we could not. That gap matters, so the table separates measured cost from cited accuracy rather than blending them into a single score.

Qwen3-Coder-Next is Alibaba's coding-tuned open-weight model, and it was the cheapest fast option in our set. On a live OpenRouter call on 2026-07-10 it consumed 36 input and 83 output tokens, billed $0.00007072, and returned in 2.78 seconds, at list rates near $0.11 input and $0.80 output per million tokens.

The pattern to notice is that Qwen3-Coder-Next carries a high output rate ($0.80/M) but a low input rate, so it rewards short-answer coding turns and punishes long generations. According to Qwen3-Coder GitHub repository, the Qwen3-Coder family is released as open-weight models, which is exactly what lets third-party routers host it at the low per-call cost we observed. If your agent asks for tight diffs rather than whole rewritten files, that pricing shape works in your favor.

DeepSeek-V3.2 is served on OpenRouter at $0.229 per million input tokens and $0.343 output. Our 2026-07-10 call used 27 input and 72 output tokens, billed $0.00013608, and took 6.05 seconds. It cost roughly twice Qwen3-Coder-Next's per-call price and ran more than twice as slow in this single measurement.

DeepSeek-V3.2's appeal is not that single call. It is a broad general-purpose base with a much flatter input-to-output rate ratio, so long-output work stays affordable where Qwen3-Coder-Next's $0.80/M output would bite. The practical read: pick DeepSeek-V3.2 when you generate a lot of tokens per task, pick Qwen3-Coder-Next when latency and short turns dominate.

What we measured via OpenRouter (first-hand)

Documentation lists prices; it does not tell you what a real request costs or how long it comes back. So we called each callable model once through OpenRouter on 2026-07-10 and recorded billed cost, token counts, and latency straight from the response body. These are routed measurements, not native-endpoint numbers, which is a real caveat: a router can price and shard differently from the model maker's own API.

What stood out when we lined them up was the speed spread. Qwen3-Coder-Next answered in 2.78 seconds against DeepSeek-V3.2's 6.05, more than a 2x difference on comparable short prompts. For an interactive coding loop where a human waits on each turn, that is the number you feel, not the fraction of a cent per call. We flag both figures for native re-verification before you budget against them. According to DeepSeek API Docs, DeepSeek publishes an official per-token rate card, and that native reference, not our routed $0.229/$0.343 reading, is what a production budget should be checked against.

Where Kimi-Dev-72B fits (sourced research, not first-hand)

Kimi-Dev-72B is Moonshot AI's open-weight coding model, and it is not callable on OpenRouter, so we did not measure it first-hand. Per sourced research it scores about 60.4% on SWE-bench Verified, which would place it ahead of both models we timed on that particular coding benchmark, though on cited numbers only, not on any figure we ran ourselves.

We are deliberately keeping Kimi-Dev-72B in a separate lane because we hold first-hand and sourced evidence to different standards. According to Kimi-Dev GitHub repository, Moonshot's coding model reports its SWE-bench Verified result, and that roughly 60.4% figure is the one worth watching if end-to-end issue resolution, rather than raw latency or price, is your primary metric. The honest caveat is that we could not price or time it here, so it stays a benchmark leader on paper until it is routable or self-hosted and measured the same way.

The verdict, by workload

Cost per call is not the decision; workload shape is. Choose Qwen3-Coder-Next if latency and short coding turns dominate, because at 2.78 seconds and $0.00007072 per call it was the fastest and cheapest thing we ran. Choose DeepSeek-V3.2 if you generate long outputs, because its flat $0.343/M output rate ages better than Qwen3-Coder-Next's $0.80/M. Watch Kimi-Dev-72B if SWE-bench-style task completion is what you are buying, and re-check it the moment it becomes callable. All three are open-weight, so none of them locks you to one vendor's endpoint, which is the quiet advantage over closed coding models that no pricing table shows.

FAQ

What is the best open-source coding model in 2026? There is no single winner. Qwen3-Coder-Next was the cheapest and fastest we measured ($0.00007072, 2.78s via OpenRouter), DeepSeek-V3.2 is better for long-output work at a flatter $0.343/M output rate, and Kimi-Dev-72B leads on the cited ~60.4% SWE-bench Verified figure but was not callable for us to time.

Which open-weight coding model is cheapest to run? In our 2026-07-10 measurements, Qwen3-Coder-Next was cheapest per call at $0.00007072 for a 36-in / 83-out request via OpenRouter, roughly half DeepSeek-V3.2's $0.00013608 on a comparable short prompt. Cheapest at scale depends on your output length, since Qwen3-Coder-Next's $0.80/M output rate is much higher than DeepSeek-V3.2's $0.343/M.

Why isn't Kimi-Dev-72B in the measured table? Kimi-Dev-72B is not available on OpenRouter, so we could not call it, price it, or time it first-hand. We cite its ~60.4% SWE-bench Verified score as sourced research only, and we do not present any latency or cost number for it because we did not run it.

Are these OpenRouter prices the same as the native API prices? Not necessarily. Every cost and latency here was measured via OpenRouter routing and is flagged for native re-verification. Router pricing and sharding can differ from a model maker's own endpoint, so treat these as a dated routed snapshot and confirm against the official rate card before budgeting.

This is part of the open-source AI agents hub. For native DeepSeek rates, see the DeepSeek API pricing hub; for the broader field, the best Chinese LLM API overview.

Author: Kevin Fan, Customer Success Manager at China LLM Directory, specializing in the Chinese LLM ecosystem and model benchmarking. Last verified: 2026-07-10.