Do Schools and Research Labs Need to Worry About Licenses? Ten Scenarios, One by One ​

We · October 2026

This is the fourth article in our "Open Source and Commercial Use" series, written for instructors running courses, lab supervisors, and students alike. Examples in this article come from our existing license compilation and the license fields in our local application catalog; clause descriptions are based on each repository's LICENSE file at the time. This article does not constitute legal advice: it teaches how to read clauses and how to judge your own actions, not whether any particular use is legal.

I. Correcting the Most Common Claim First ​

Almost every semester someone says this: "We're doing teaching, not commercial use, so we don't need to worry about licenses."

This sentence conflates two things into one.

First: permissive licenses do not ask who you are to begin with. MIT and Apache-2.0 allow anyone to use them, including commercial use — teaching is naturally included. So under these licenses you indeed do not need to worry, but the reason is not "classrooms have an exemption" — it is that there was never a threshold to begin with.

Second: the three license types schools are most likely to encounter do not ask about your identity — they ask about your actions. They are:

• Non-commercial licenses (CC BY-NC, research licenses, and similar): the question is "does this instance count as commercial," not "are you a student."
• Community licenses with scale thresholds: the question is "how large is the entity using it, how much revenue does it generate." Whether a school falls inside this clause depends on how the license defines the using entity.
• Attribution and trademark: the question is "did you state the source, did you use someone else's标识." Logos on course covers, recruitment posters, and competition materials have nothing to do with whether the model can be used commercially.

So the question needs to be reframed: instead of "I'm a school, so what?" — ask "what action am I about to take next." The rest of this article is written entirely according to this reframed question.

On the legal layer, this article clarifies only one thing. The law does provide certain exceptions for classroom teaching and scientific research. But how these exceptions apply depends on current statutes and specific cases: what conditions apply, how much copying counts as "a small amount," whether online courses are included. We do not paraphrase these provisions from memory. When you need precise basis, refer to the official text or consult legal counsel.

What can be said here is one plain sentence: a license is a contract you agreed to; legal exceptions are a separate set of rules — the two do not substitute for each other. A contract that says "no commercial use" does not automatically become void because you are in a classroom.

II. Judgment Depends on Only Two Actions ​

Licenses stay quiet most of the time. Only two actions make them speak up.

Action 1: Handing something over. You give software, model files, installers, images, or USB drives to someone else — whether or not money changes hands, this is distribution. Obligations under GPL and similar licenses begin at this moment: when you give the program to someone else, you must simultaneously provide source code or a way to obtain it, and attach the license text and notices.

Action 2: Exposing capability as a service. Others do not download your thing — they directly use results produced by your machine over the network. Deploying on a campus platform, opening a web API, installing an online grading tool — all of these count. AGPL specifically targets this situation: it states that providing access over a network also requires open-sourcing.

Most remaining situations do not need to cause concern. Installing on your own machine and running it, students running it in a computer lab, students submitting assignments and the instructor reviewing on their own machine — neither of the two actions has occurred, so obligations have not yet begun.

You can therefore compress an entire course's or lab's compliance question into two sentences: Am I going to hand something to someone else? Am I letting someone use my machine over the network? If both answers are "no," you can generally proceed with confidence. If either is "yes," you need to read the original text.

III. Ten Scenarios, One by One ​

Arranged in order of "getting closer to the school gate, then finally crossing it." This table can be printed and posted in the office.

Two reminders.

The first concerns ⑥. There is no buffer between internal and public — only one action. A previous article, Which Local Open-Source Models Can Students Run for Their Capstone Projects?, organized which models run by direction; that list governs "can it run," while this table governs "how far can it go." Students most often get into trouble here: submission day is fully compliant, but the day they upload weights to a public repo, they become a distributor.

The second concerns ⑨ and ⑩. Once someone else is contributing money or resources, the license is no longer the only source of terms. The model the enterprise gave you might say "for internal use in this project only," while the collaboration agreement might require output to be published externally. Both documents govern you simultaneously, and only what both permit is genuinely usable. This article does not guess at the specific obligations in university-industry collaboration and technology transfer — they are written in the agreement you signed.

⑥ and ⑦ also have a publishing side. The table above governs "how far can you go with someone else's thing." Why schools, labs, and individual developers publish what they make, why their licenses tend to be more permissive, and where they might suddenly tighten — Why People Who Don't Run a Business Also Open-Source covers that side. The two articles together form one complete path: first understand why the other party wrote it that way, then judge whether you can use it.

IV. Four Places Most Easily Overlooked ​

The school name is not a field in the license. Clauses judge purpose and scale — they do not switch to a different answer just because the scenario says "teaching." More practically: the same lab, the same machine, the same weights — "undergraduates practicing" and "the lab providing services to external organizations" lead to two different conclusions.

"Research" in a research license does not necessarily include teaching. Many research licenses are written around only the two words "research" and "non-commercial." Whether teaching falls inside depends on the specific wording of permitted uses, not on common sense. When reading, focus on three things: what is allowed, whether commercial use is prohibited, and whether you need to mark source and changes.

Attribution and assets are a separate thread, and the most commonly missed one. Weights under CC BY-4.0 (PocketTTS, Parakeet, and Citrinet in our catalog) allow commercial use, but you must actually provide attribution — paper footnotes, video descriptions, course page footers, anywhere counts, but unwritten means undone. And the BGM, voice packs, and fonts used in courses do not belong to the "open-source software" category at all — they operate under a separate set of terms. The habit from Where Model Files Come From of "looking at the license name written next to the file" applies equally to assets.

"Who can reuse it once more" in collaborations is usually left unwritten. When an enterprise provides compute or models to a school, the most common question is: the enterprise received it for "internal research use," does the school using it for teaching count as internal use, and does a student passing it to a classmate count? The agreement does not say, and the person who ends up acting is the one who has the hardest time explaining. This does not require legal knowledge — just one extra question before starting the collaboration.

V. Which Tier Is Least Trouble, and a One-Page Pre-Action Checklist ​

The table below is not ranked and not a recommendation order — it is arranged only by "how many conditions the clause places on use," from fewest to most. Categories and examples follow our Open-Source Software Licenses Explained and audio.cpp Model Licenses and Commercial Use; always verify against the original text of the specific version you are using.

A five-row sheet for instructors and lab supervisors. Installation and equipment procurement are covered in Vocational College AI Lab Construction Guide and Why Universities Need to Build Local AI Lab Environments; here we only add the license side of that one page:

The first two rows determine the risk level; the third and fifth rows determine when obligations take effect. Fill in all five rows, and most of a semester's or cycle's questions are resolved in advance.

Three sentences for students. First: record the name before touching anything — on the day you download, write the version number and license name into your assignment documentation; it costs ten seconds. Second: submitting an assignment is not distributing it — the day you upload to a public repo is, and that day you need to reread the clauses. Third: do not assume "non-commercial" speaks for you — paid courses, freelance work, competition entries — many clauses wrote these three things into their restrictions long ago.

VI. Our Take ​

First, in teaching and research scenarios, there are really only two actions to manage, not one identity. Handing over, exposing as a service — grasp these two, and the ten scenarios split cleanly in half: the first two cells are basically safe, every cell after that requires reading the original text. Fail to grasp these two, and you can reread the clauses three times and still miss things, because what you miss is never in the clauses — it is in your actions.

Second, schools and labs are low-risk settings, not zero-risk settings. Low-risk means: choose models from the permissive tier, do not distribute images, do not expose services, and you can proceed smoothly. It does not mean "no need to read clauses" — quite the opposite. The non-commercial and research licenses most commonly encountered on campus are precisely the two types most worth a second look. Treating low-risk as zero-risk is the single most easily mis-taught lesson in this course, and it should not be left for students to figure out on their own.

Third, the more others are contributing money or resources, the more important it is to confirm first who is doing the distributing. Inter-institutional sharing, university-industry collaboration, and technology transfer — the question in all three tiers is not "can I use it" but "can I pass it on to someone else." That one question takes thirty seconds, yet it determines the attribution of all downstream obligations. When compiling license information for our platform's and. We also treat "can it be redistributed" as a standalone field — and that is precisely the field teaching scenarios actually need.

Disclaimer: This article is our synthesis of license texts and our existing license compilation, discussing usage forms in school and research scenarios. It does not constitute legal advice, nor does it determine whether any specific use is legal. Clause descriptions are based on each repository's LICENSE file at the time; classifications follow the conventions of audio.cpp Model Licenses and Commercial Use and Open-Source Software Licenses Explained, and may change with upstream updates. Regarding the applicability conditions for statutory teaching and research exceptions, we have not verified the provisions here — refer to current official text and consult professional legal counsel.