Subtitle: Open releases now arrive with geographic restrictions, user caps, and acceptable use clauses, so this article answers the question to ask before you build on one: what does the license actually let me do?
Suggested SEO meta title: Open Weights AI Models: Are They Really Free to Use in Business?
The Word "Open" Is Doing a Lot of Work Right Now
MiniMax released H3, a state of the art open video model, free to download on Hugging Face.
Free, that is, unless you live in the United States, the United Kingdom, the European Union, or South Korea. Then you apply for a license. The Batch, DeepLearning.AI's newsletter, called that territorial restriction out in Issue 366 as a violation of what "open" is supposed to mean.
Most of the paying world, asking permission to use a free thing.
Here is the direct answer. No, "open weights" does not automatically mean free for your business. It means you can download the numbers that make the model work. Whether you can legally use those numbers to serve clients, fine tune on your own data, or ship a product depends on a license almost nobody reads, and those licenses increasingly contain caps on your user count, restrictions on your country, bans on competing use, and terms the model maker can change at the next version.
Hear both halves, because both are true at once.
Self hostable models finally got good enough that your client records, contracts, and intake forms can stay inside your own building. That is a genuinely useful shift for anyone in a confidentiality-heavy business.
And "open" has quietly become a marketing word with an asterisk attached.
Candidly, this is where small business owners get hurt. Not by the technology. By the paperwork underneath it.
So read the license before you build the business. That is the thesis, and the rest of this post is how to do it without a law degree.
The Short Version
Key Takeaways
- "Open weights" means you can download the parameters, not that you have unrestricted commercial rights.
- The Open Source AI Definition requires training data information, training code, and an approved license, and most "open" models meet only one.
- Custom licenses like Meta's Llama and Alibaba's Tongyi Qianwen carry user caps and bans on competing use.
- Open models now perform close enough to closed ones that keeping client data in house is realistic.
- Run a four gate license check before you build, and again at every upgrade.
The Problem: Nobody Reads the License, Including the People Selling You the Idea
Here is the thing about fine print. It never hurts you on day one.
It hurts you on day four hundred, after you have built the workflow, trained your team, migrated the client data, and told forty people this is how your firm handles intake now.
I have signed documents I did not fully read. That cost me years of my life and a bankruptcy, and I am not going to dress it up. What I took from it looks obsessive to people who never paid that tuition: I read the agreement before I build on top of the thing.
Most small business owners have the opposite instinct, and I understand why. You are not a lawyer. The license is nine pages of defined terms. Somebody on YouTube said the model was open source and free. Ollama installed it in four minutes and it worked. The friction to check is high and the friction to proceed is zero.
So people proceed.
Then the model maker ships version two with different terms. Or a clause you skipped prohibits exactly the thing your business does. Or the "open" model under your client-facing product turns out to restrict using its outputs to improve any competing system, and your product sits in a gray zone you cannot afford to litigate.
The law firm Cooley published an alert on August 12, 2026, aimed at general counsel evaluating these models. Their framing was blunt: licensing is the threshold issue. Not copyright. Not regulation. The license itself, because unlike traditional open source licenses, which are standardized and well understood, open weight licenses are increasingly custom written by each model maker.
Custom means you cannot pattern match. Apache 2.0 is Apache 2.0 everywhere. The Llama Community License is its own animal, Tongyi Qianwen a different animal, and MiniMax H3 a third animal that asks Americans and Europeans to fill out a form.
I am not telling you to fear open weight models. I run them. They are one of the best things to happen to small business AI in three years.
I am telling you the leverage sits in the fine print, and the people who read it end up in a materially better position than the people who did not.
The Evidence: What the Research Actually Says
Here are the sourced facts, because this is a topic where hand waving is common.
1. "Open source AI" has a real definition, and open weights does not meet it.
The Open Source Initiative's Open Source AI Definition 1.0 requires three things: enough information about the training data that a skilled person could build a substantially equivalent system, the full training and inference code, and the parameters under an OSI approved license. Open weight releases satisfy only the third. The OSI's own phrasing is the clearest summary: open weight models give you the product, but not the factory.
2. Researchers documented this pattern and named it.
Andreas Liesenfeld and Mark Dingemanse presented "Rethinking open source generative AI: open washing and the EU AI Act" at the 2024 ACM Conference on Fairness, Accountability, and Transparency. They evaluated 45 generative AI systems across 14 dimensions of openness and found many marketed as open source were, at best, open weight. The term is openwashing, and it now has peer reviewed evidence behind it.
3. The license caps are specific and numeric.
Meta's Llama Community License requires any licensee exceeding 700 million monthly active users in the preceding calendar month to request a separate license from Meta, granted at Meta's sole discretion. Alibaba's Tongyi Qianwen License sets that threshold at 100 million. Both incorporate acceptable use policies by reference and restrict training competing systems.
Will your consulting practice hit 700 million monthly users? No. That is not the point. These are conditional commercial licenses, not grants of freedom, and the condition that catches you is more likely the one about competing use, redistribution, or attribution.
4. The performance excuse is gone.
Stanford HAI's AI Index found the gap between the best closed model and the best open model on the Chatbot Arena leaderboard fell from 8.0 percent in January 2024 to roughly 4.2 percent by mid 2024, and to 1.7 percent by February 2025. When open models were clearly worse, the license did not matter, because you were not going to use them. That excuse is gone.
5. Adoption is real but messier than the headlines.
The Linux Foundation's research on the economic and workforce impacts of open source AI found 89 percent of organizations using some form of open source in their AI stack and 63 percent using an open model. Yet Menlo Ventures' 2025 State of Generative AI in the Enterprise report, a survey of nearly 500 US enterprise decision makers published December 9, 2025, found enterprise open source model share fell from 19 percent to 11 percent year over year.
Both are true. Lots of companies touch open models. Fewer run production on them. The gap between "we tried it" and "we run our business on it" is where the license question lives.
And the releases keep coming. Alibaba confirmed this week that Qwen3.8-Max weights, all 2.4 trillion of them, are open, in the same quarterly report showing net income down 75 percent on AI capital expenditure.
The Solution: The Four Gate License Check
Here is what changed for me.
I stopped evaluating models on benchmarks first. I evaluate the license first, and only models that clear the license get to the benchmark conversation. It sounds backward. It has saved me from two builds I would have regretted.
Four gates. About twenty minutes per model, once per version.
Gate 1: Who is allowed to use this?
Is there a geographic restriction, and is there a user count threshold? MiniMax H3 fails gate one for most of my readers, because you are in the US, UK, EU, or South Korea and you have to apply. Llama sets its bar at 700 million monthly active users, Tongyi Qianwen at 100 million. Write down the actual number and the actual countries.
Gate 2: What am I allowed to use it for?
Find the acceptable use policy. It is usually a separate document incorporated by reference, which is a fancy way of saying it binds you even though it is not in the license you just read. Look for restrictions on commercial use, on customer facing products versus internal use, and on using the model or its outputs to train or improve a competing AI model. Cooley flags that last one as common, and it catches software businesses by surprise.
Gate 3: What happens to the thing I build?
If you fine tune on your client data, who owns the resulting weights and what license attaches to them? If you redistribute, what attribution is required? Are there copyleft style provisions forcing your derivatives out on the same terms? For a coaching business, usually harmless. For anyone building a product, this gate is the whole ballgame.
Gate 4: What happens at the next version?
This is the gate nobody thinks about. Weights released under Apache 2.0 or MIT cannot have that version's terms retroactively changed. Custom vendor licenses can read differently at the next release. So the question is not just "what does this license say," it is "what is my plan if version four says something worse." Pin the version. Keep a dated copy of the license file.
The practical shortcut: prefer models released under plain Apache 2.0 or MIT. Most of the Qwen line ships under Apache 2.0, with typically only the largest size in each generation keeping the bespoke Tongyi Qianwen terms. That one preference eliminates most of your fine print risk.
The tooling is not exotic. Ollama or LM Studio on a decent machine gets a local model running the same afternoon. The hard part was never the software. It is the twenty minutes with the license.
Practical Steps: Run This Before You Build Anything
-
Write down the one job you want the local model to do. Not "AI for my business." Something like "summarize client intake forms without the content leaving my office." A single named job makes every later decision easy, and tells you whether you even need self hosting.
-
Find the real license file, not the blog post. Go to the model's Hugging Face page and open the LICENSE file directly. Marketing pages say "open." The LICENSE file says what you can do. Save a dated copy.
-
Run the four gates and write one sentence per gate. Who can use it. What for. What happens to derivatives. What happens next version. If you cannot write a clear sentence for a gate, that is your answer for that gate.
-
Use AI to read the license with you, not for you. Paste the license into your assistant with this prompt:
[The Job]
Analyze the attached AI model license and tell me what it restricts.
This is for: [YOUR BUSINESS TYPE, e.g. a six person bookkeeping firm].
It matters because: I am deciding whether to build [YOUR INTENDED USE, e.g. an internal client document summarizer] on this model and I cannot afford to find a restriction after we have deployed it.[The Background]
Here is what you need to know: I plan to [INTERNAL USE ONLY or CUSTOMER FACING PRODUCT]. I will [FINE TUNE / NOT FINE TUNE] the model on my own data. My business operates in [COUNTRY] and serves roughly [NUMBER] customers.
Do not use: general commentary about open source philosophy, or anything not stated in the license text I provided.[The Deliverable]
Return: a plain English table with four rows labeled Who Can Use It, What It Can Be Used For, What Happens To Derivatives, and Version Stability. Under the table, list every clause that could restrict my specific stated use, quoting the clause and giving the section number.
Must include: any geographic restriction, any user count threshold, and any restriction on training competing models.
Optimize for: accuracy. Written from the perspective of a technology transactions attorney speaking to a non-technical business owner.[The Questions]
Ask me any questions you have. -
Pilot on a machine that touches no client data. Run the model locally for two weeks on synthetic or already-public documents. You are testing whether output quality holds up on your real work, not whether the demo was impressive.
-
Have a human read the flagged clauses. AI is excellent at finding clauses. It is not your lawyer. If gate two or gate three turned up anything ambiguous and you are building something customer facing, buy an hour of legal review.
-
Calendar a license review at every version bump. Make it a recurring blocker on upgrades. New version, new license read, before deployment. Cooley recommends exactly this, and it costs twenty minutes against a risk that compounds silently.
Frequently Asked Questions
Is an open weights AI model actually free to use in my business?
Usually yes for internal use, but "free" and "unrestricted" are different things. Open weights means you can download the model without paying. The license still governs how you may use it commercially, and may restrict your country, your user count, customer facing deployment, or building competing products. Read the LICENSE file before deploying.
What is the difference between open source AI and open weights?
Open weights means the trained model parameters are downloadable. Open source AI, per the Open Source Initiative's Open Source AI Definition 1.0, additionally requires the training code and enough information about the training data to rebuild an equivalent system. Most models marketed as open source are open weight only, which researchers call openwashing.
Do I need my own server to use an open weights model?
No. You can run smaller open weight models on a modern laptop using Ollama or LM Studio, or rent a hosted endpoint from an inference provider. You only need your own hardware if your goal is keeping regulated or confidential data entirely inside your own network, which is the main reason small firms self host.
Will self hosting save me money compared to paying for an API?
Usually not at small business volume. Self hosting beats frontier model API pricing only at high sustained usage with good hardware utilization, and against cheap open model APIs it rarely wins on cost alone. The real reason to self host is data control and compliance, not the monthly bill.
Is it risky to use a Chinese developed open weight model in my business?
It requires diligence rather than avoidance. Cooley's August 2026 alert recommends assessing the developer's jurisdiction, ownership, and supply chain, checking for export control or trade restrictions, and applying extra review where sensitive or regulated data is involved. Treat it as standard vendor diligence, alongside your license and IP review.
The Close: Read It Before You Build On It
Go back to where we started. MiniMax released a state of the art video model, called it open, put it on Hugging Face for free, and then asked everyone in the United States, the United Kingdom, the European Union, and South Korea to apply for permission.
That is not a scandal. It is a signal.
"Open" is now a marketing word, and marketing words do not survive contact with a contract. The people who understand that build on solid ground. The people who trust the announcement build on somebody else's terms and find out what those terms were at the worst possible moment.
I am not asking you to become suspicious of everything. I am asking you to spend twenty minutes.
Twenty minutes with a LICENSE file, before you migrate the client records, before you tell your team this is how we do intake now, before you put your name on a product built on somebody else's weights. I have paid far more than twenty minutes for documents I did not read, and I would not wish that math on anybody.
Understand what sits on the other side of those twenty minutes, because it is genuinely good. A model on a machine in your own office. Client contracts that never leave the building. Capability that was frontier grade eighteen months ago, under your own roof.
That is worth having. It is worth having correctly.
The weights are free. The freedom is not. Read the license.
About the Author
Jonathan Mast founded White Beard Strategies to teach entrepreneurs, coaches, and small business owners how to use AI without a technical background. He runs a Facebook community of more than 500,000 members, leads the AI Insiders membership at $247 per month, and speaks regularly on practical AI adoption. He has been open about a past that includes prison and bankruptcy, and the habit he carries from it is simple: read the agreement before you build on it. He keeps a local model running in his own office so client documents never leave the building.
Want to go deeper? AI Insiders is $247 per month and includes the live sessions, the templates, and the community where we work through decisions like this one. New to this? Express AI Training is $10 live or $20 for the replay.
Sources:
- The Open Source AI Definition 1.0, Open Source Initiative
- Open Weights: not quite what you've been told, Open Source Initiative
- Rethinking open source generative AI: open-washing and the EU AI Act, Liesenfeld and Dingemanse, FAccT 2024
- Llama 3.1 Community License Agreement
- Tongyi Qianwen License Agreement
- Unlocking the Weights: What Enterprises Should Know Before Deploying Open-Weight AI Models, Cooley, August 12, 2026
- The 2025 AI Index Report, Stanford HAI
- The Economic and Workforce Impacts of Open Source AI, Linux Foundation
- 2025: The State of Generative AI in the Enterprise, Menlo Ventures
- The Batch, Issue 366, DeepLearning.AI