NVIDIA, Hugging Face, and the Growing Importance of Open-Weight AI

We saw big news last week about NVIDIA’s intent to acquire Hugging Face, the “GitHub” for AI models.

Here are three takeaways and some other considerations around this significant development for AI model access.

  1. This proposed acquisition heavily underscores that open weight models are critical to AI systems development 

  2. The acquisition has implications for access to open weight models

  3. This doesn’t mean the end for closed frontier models 

Some background

NVIDIA has built a huge open model and tool ecosystem (Nemotron, GR00T, Cosmos) for a wide range of researchers, data scientists, AI developers, and more. This is nothing new for NVIDIA, and it is complementary to and a logical extension of their approach to open weight models. NVIDIA is also an investor in Hugging Face. And all sorts of models - closed and open - run on  NVIDIA systems.

Takeaway 1: Open Weight Models Matter

The frontier model companies have made access to LLMs widely available across the planet via free and low cost vehicles. This is essentially the SaaS model for AI. The last few years have been transformative - this is an understatement.

However, token cost concerns around closed frontier models have been putting more attention on open weight models and have motivated more and more companies and individuals to look at running local models to shift the token cost. 

Takeaway 2: Concentration of Access to Models is a Concern 

Any time you see this level of concentration of control over a mission critical asset, you should be concerned just on the face of it.

There is a strong case to be made that NVIDIA has a clear vested interest in keeping access to open weight models and keeping the ecosystem healthy. And they have funding and expertise to do this.

There are already other communities for model hosting and discovery, and others will likely emerge. This is one practical application of “software eats the world” that will keep access to models open.

Takeaway 3: Closed Frontier Models will still matter for a long time 

The frontier models are called this for a reason: they are on one critical leading edge of model development and capability.

Many (most) shops are not ready for or interested in running models locally due to the CAPEX cost, potentially large OPEX costs depending on scale, and expertise required. This will shift as ease of use increases and models get more optimized for smaller footprints and efficiency. 

Access to the best available frontier models will be a need for many organizations for the foreseeable future.

Other Considerations

Hugging Face lists over 3 million models as of this writing, and this number will certainly grow. Picking the best or the right model for a task is already daunting, and this underscores the need for smart model routers and other more sophisticated mechanisms for selecting models dynamically based on multiple factors, including cost.

The sheer number of models available also shines a bright light on security concerns. We’re in the “irrational exuberance” phase of picking  models today. We need to mature quickly to develop security frameworks and enforcement mechanisms around model selection and use.

If you’ve been developing code and systems strictly around the frontier models via API access, it’s time to get familiar with downloading models locally and running them in your own environment.

What’s Next 

NVIDIA’s intent to acquire Hugging Face signals much more weight placed in that camp (pun completely intended). There are implications on influence and control over the ecosystem. 

This is a rapidly-developing set of tools and technologies. This is also the next significant milestone, certainly not the last one, and time will show us how the mix of open weight and closed models will trend.

Scott Robohn

Scott is co-founder and CEO of Solutional, where he leads initiatives in next-gen networking, automation, AI, and emerging technologies. With 35+ years of experience building, guiding, and scaling technical teams and solutions, Scott helps IT and NetOps organizations evolve into software-centric, resilient, and intelligent operations teams. His career has provided the depth and breadth of experience needed to lead technical sales organizations, including roles and partnerships with CTOs, Solutions Architects, Sales Engineers, Systems Engineers, Account Executives, Product and Engineering leaders, and other job functions. Scott is a frequent event speaker, host of the Total Network Operations podcast, and a co-founder of the Network Automation Forum (NAF).

Next
Next

The AI Network Is Part of the Product