Licences

Licences are the most concrete risk in a motion project: many state-of-the-art models have non-commercial weights. The plugin handles them at three levels:

• At kickoff, the project's policy is written into license_policy: commercial use or not, region, Remotion status (free up to 3 employees, paid company licence above), accepted exceptions.
• While you work, a hook refuses to install (npm, pnpm, yarn, bun, pip, uv, pipx, poetry) a package or model that the policy forbids, and suggests an alternative. The registry has 39 entries:
  • non-commercial weights such as F5-TTS, MusicGen, YuE, FLUX.1 [dev]…, and tools under a non-commercial licence (anything2explainer, CC BY-NC datasets);
  • Tencent Hunyuan models, whose licence does not apply in Europe;
  • AGPL and GPL;
  • Animate UI's Commons Clause;
  • repositories without a licence;
  • paid collections, or collections you may not redistribute.
• At audit, umd licenses cross-checks dependencies, declared models and .motion/assets.lock.json. Every asset is recorded there with its source and licence; required credits are copied into deliverables/credits.txt.

An exception is still possible: it is your decision, written down explicitly in license_policy.allow.

For images, umd commons only offers public domain, CC0 and CC BY (CC BY-SA only if you ask), downloads the file and records it in assets.lock.json with its author and credit line.