With AI, control matters more than capability

Ask most enterprise technology teams where they spend their AI strategy energy and you will get the same answer: figuring out which model to use. It feels like the right question. As organizations move from pilots into production and the real compliance, cost and continuity risks appear, it turns out to be the wrong one.

Writing on CIO.com this year, Floyd DCosta argued the divide is between enterprises that own their AI and those that rent it, and later that closed-model dependency is outsourced intelligence with a vendor kill switch in your operations. He is right. But the ownership question raises a harder one: own it how? I believe the answer is open-weight and open-source models, not because they are cheaper, but because they are structurally better suited to how serious organizations need to govern and protect AI at scale.

Why closed models create governance problems

Building an enterprise AI program on closed, proprietary models from a single external provider is not a technology decision. It is a governance liability. The data confirms the exposure is already real.

A June 2026 IBM Institute for Business Value study of 1,000 senior executives found that 91% do not fully understand their AI vendor dependencies, 71% said switching providers would be difficult, and 81% said a seven-day vendor outage would cause severe disruption. These figures describe the baseline condition of enterprise AI in 2026.

Think about what you give up. You cannot audit the training data. You have no visibility into how the model changes between versions. Your cost structure is set by someone else’s pricing team. And if that provider faces a government directive, a supply disruption or a commercial decision to reprice, you have no leverage and often no warning. For a generic SaaS tool, that is an inconvenience. For organizations in defense, healthcare or financial services, where data handling is regulated by law and audit trails are mandatory, a vendor changing model access terms overnight is a compliance event.

The most vivid demonstration came in June 2026, when the U.S. Commerce Department ordered Anthropic to suspend access to Fable 5 and Mythos 5 for all foreign nationals, including its own non-citizen employees. The result was a hard global shutoff for every customer, with no advance notice. Enterprises with production workflows on those models were left with nothing. The precedent is now set.

This is what AI governance exposure looks like in practice. When your intelligence layer sits entirely outside your control, a single government directive, pricing change or vendor decision can bring your AI operations to a halt. Having seen organizations scramble through exactly this scenario, I can say the ones with no continuity plan are the most exposed. The IBM numbers confirm it: most enterprises have not built the visibility, let alone the architecture, to absorb this kind of disruption. The question is not whether it will happen again. It is whether your architecture is ready when it does.

Open-weight models have changed the equation

Until recently, the argument for closed frontier models was simple: they were dramatically better. That gap has narrowed faster than most enterprise technology leaders anticipated, and the conversation has shifted from capability to control.

Open-weight models, including Meta’s Llama family, Alibaba’s Qwen series, Zhipu AI’s GLM and DeepSeek, have moved well past the research stage. They are running in production at serious organizations, and not because those organizations could not afford anything better. They chose them because open-weight models give them something closed models cannot: control.

Airbnb’s adoption of Alibaba’s Qwen makes the case plainly. CEO Brian Chesky stated that the company relies heavily on Qwen to power its customer service agent, describing it as “very good” and “fast and cheap,” while noting that OpenAI’s SDK was not ready for the depth of integration Airbnb needed. The agent runs across 13 different models. That is not a cost-cutting move. It is a deliberate multi-model architecture built around control, not just capability.

Microsoft’s evaluation of DeepSeek V4 for Copilot Cowork, reported by Axios in June 2026, tells the same story. The company is exploring a self-hosted DeepSeek to replace the Anthropic and OpenAI models powering its enterprise agentic product, driven by unsustainable costs at scale. Charles Lamanna, Microsoft’s executive vice president for Copilot, agents and platform, told Axios: “We have users who do hundreds of tasks a week… the consequence is the costs can go very high.” The IBM study’s full findings add context: organizations pay 2.8 times more in token processing when AI runs far from the data it depends on.

When Airbnb and Microsoft are making these choices in production, the market signal is unambiguous. Open weight is not a fallback. It is the architecture direction serious enterprises are moving toward.

Some of these models are Chinese in origin, and yes, that has drawn attention from U.S. lawmakers. Those are real conversations worth having. But here is the practical point: a model running inside your own infrastructure, under your own security controls, gives you more governance than a closed model running on a server you do not own, regardless of where either was built.

Three forces accelerating the shift

Three things are pushing enterprises in this direction, and none of them are going away.

• Cost at scale. Every API call compounds. Open-weight models on your own infrastructure convert that variable cost into one your organization controls. The IBM study found misaligned AI infrastructure costs enterprises 2.8 times more in token processing. Microsoft’s DeepSeek evaluation is that logic at the largest scale in the industry.
• Data protection. Consider what this means for a hospital routing patient records through a third-party AI API, a defense contractor using a closed model to analyze procurement data, or bank feeding client financials into an external inference endpoint. In each case, compliance is contingent on a vendor relationship the organization does not fully control. HIPAA does not care whether your AI vendor had a good SLA. FedRAMP authorization does not transfer because a model performed well on a benchmark. Regulators expect organizations to demonstrate control over where sensitive data goes, and a closed frontier API is not a defensible answer. The IBM study found 68% of executives say meeting data residency and sovereignty requirements across geographies is already challenging. Open-weight models deployed within your own environment remove that exposure entirely. The data does not leave your perimeter, full stop.
• Sovereignty. The Fable 5 episode made clear that your AI capability is only as sovereign as the provider you depend on. For defense primes, intelligence contractors and any organization operating under jurisdiction-specific regulations, this is an existential design question, not a preference. Open-weight models, deployable under your own governance in any environment, are the only architecture that resolves it.

What this means for enterprise AI architecture

In conversations with technology leaders, the same pattern keeps surfacing: organizations that started with a single frontier provider for speed are now the most constrained when they try to scale, govern or adapt. This is especially acute in regulated sectors. A healthcare organization that built clinical documentation on a closed frontier model faces a hard question every time that vendor changes its data processing terms. A defense contractor with a closed model embedded in its logistics pipeline must revisit its authorization to operate every time the model updates silently. The implication is not to abandon frontier models entirely. It is to stop building AI programs that depend on them as the sole or default layer.

The practical answer is a multi-model architecture: frontier models where the capability genuinely justifies the cost and the data exposure, open-weight models running on your own infrastructure for everything else. Not every task needs the most powerful model available. And not every task should leave your perimeter.

DCosta framed the coming divide as between AI owners and AI renters. I would take that one step further. The organizations that will genuinely own their AI are the ones building the infrastructure, governance and internal capability to run open-weight models on their own terms, right now. The ones that continue to depend entirely on closed frontier providers are not owners, whatever they call themselves. They are renters, and their leases can be terminated, repriced or restricted at any time. The IBM study makes the stakes clear: 57% of executives say replacing a core AI model would require significant decoupling or a full rebuild. The longer you wait to build portability in, the harder it gets.

The best AI model is not the one with the highest benchmark score. It is the one that fits into an architecture your organization governs.

This article is published as part of the Foundry Expert Contributor Network.
Want to join?