An Open Model You Cannot Run Is a Different Product Than One You Can. This Month Proved It.

Two open weight releases landed within about a day of each other this month, and together they tell you more about where local AI is going than any benchmark chart. On August 11, Nvidia shipped Nemotron 3.5 Lightning, a 30 billion parameter mixture of experts model with 3 billion active parameters per token, built explicitly for the high volume execution layer of always on agents. On August 12, DeepSeek took V4 Pro out of preview and put the full weights on Hugging Face under an MIT license: 1.7 trillion parameters, 893 gigabytes on disk. Both releases get filed under the same label, open weights. They are not the same product. They are barely the same category, and if you build AI systems, the difference should change how you spend money.

The word open is doing two different jobs

Start with the honest math. My workstation runs an RTX PRO 6000 Blackwell with 96 GB of VRAM, which puts me well past what most people running local models have on their desk. An 893 gigabyte model is not a stretch goal for that machine. It is not a quantization project or a clever offloading trick away. It is a different class of infrastructure, a multi node cluster problem, and the same is true of Kimi K3 at roughly 2.8 trillion parameters and Qwen3.8 Max at 2.4 trillion. The r/LocalLLaMA crowd has already noticed the irony: the community that exists to run models locally increasingly consumes the biggest open models through cloud token plans and third party inference providers, because there is no other way to touch them.

So what is a frontier scale open release actually for, if almost nobody can run it? Three things, and they are all real. First, price discipline: an MIT licensed 1.7 trillion parameter model means any inference provider on the planet can serve it, which puts a hard ceiling on what closed labs can charge for comparable capability. Second, audit rights: enterprises with genuine cluster budgets can inspect and self host the thing that touches their data. Third, insurance: if the lab pivots, raises prices, or gets acquired, the weights do not disappear. That is a valuable product. It is just not local AI, and calling it open without that asterisk confuses people about what they bought.

The runnable class is where agents actually live

Nemotron 3.5 Lightning is the other product, and its design point is the one I care about as someone who runs agents around the clock. Nvidia built it for what it calls specialized task execution in long running agents, and the shape of the model follows: sparse mixture of experts, only 3 billion parameters active per token, a context window up to a million tokens, small enough to serve from a single GPU. Nvidia claims up to four times the output speed of similar sized models. Treat that number the way you should treat every vendor benchmark, as a claim awaiting third party replication. But the architectural logic does not need the marketing to hold up: a tiny active parameter set means high throughput and low latency, which is exactly what the execution layer of an agent system consumes.

Here is the distinction that took me an embarrassingly long time to internalize while running my own agent stack. Agents do not spend most of their tokens thinking. They spend most of their tokens doing: classifying an email, extracting fields from a page, formatting a tool call, checking whether a step succeeded, summarizing a log. For every genuinely hard reasoning call in my pipelines, there are dozens of these small, boring, high volume calls. The token volume, and therefore the money, lives in the boring layer. That is the layer where an API bill compounds against you every single day, and it is also the layer where a model you own, running on hardware you already paid for, amortizes toward free. The frontier scale model is a peak capability question. The execution model is an economics question, and economics is where local wins.

Stop choosing. Split the stack.

The mistake I see builders make is treating this as a loyalty question: local versus cloud, open versus closed, pick a side. The right architecture is a split. Rent the frontier scale capability for the small fraction of calls that genuinely need it, and rent it from whoever serves open weights cheapest this month, because the MIT license is precisely what keeps that market competitive and your switching cost near zero. Run the execution class locally, on hardware sized to your actual volume, where the marginal token costs electricity. Keep the boundary between the two layers explicit in your routing so you can move it as models improve. Every serious agent system I have built converges on this shape, and the releases this month suggest the model makers now design for it too. Nvidia did not ship a 3 billion active parameter model by accident. It ships hardware for exactly the buyers who run that layer at home.

And note what the 893 gigabyte release still does for you even if you never download a single shard: it disciplines the price of the layer you rent. Every closed lab pricing a frontier API today has to answer to an MIT licensed alternative that any provider can serve at commodity margins. Local builders benefit from frontier open weights the way drivers benefit from a competitor opening a gas station across the street. You do not have to shop there for the price to drop.

The test I would run this week

Pull one week of traces from whatever agent system you run and tag every model call as reasoning or execution. My experience says most builders guess their split badly, assuming the expensive thinking dominates when the cheap doing does. Once you have the real ratio, price the execution slice at API rates against the amortized cost of a GPU you could buy this quarter, and price the reasoning slice across three open weight providers instead of one closed lab. If your execution layer is more than half your token volume and you are paying frontier prices for it, you are not buying intelligence. You are buying convenience at a markup that a 30 billion parameter model running in your office would erase. The labels on these releases all say open. Your job is to know which kind of open you are holding.