The checklist
- Read the acceptable use policy, which is the part beyond plain Apache 2.0.
- Keep the licence text and attribution with the model weights and with any derivative you distribute.
- Do not imply endorsement by TII. This site carries that disclaimer and yours should too.
- Check whether your fine-tune or your product falls under a restriction in the policy.
- Note the model card warning: production use without adequate risk assessment is listed as out of scope.
What the licence does not require
The Apache 2.0 base does not oblige you to publish your fine-tunes, does not require you to open-source an application built on the model, and does not impose a revenue share. That is the substantive difference from Falcon 1, whose licence required a separate agreement above a revenue threshold.
Serving other people
Running Falcon 2 behind an API for paying users is a commercial use like any other, but it moves the acceptable use policy from a document you read once to a requirement you operate: you are now the party deciding what prompts the model sees. Moderation, logging and abuse handling become part of licence compliance rather than product polish.
Not legal advice
This page summarises public licence documents. It is not legal advice and it is not a substitute for reading the licence at the source, which is the version that governs.
Related pages
Sources
falcon2.lol is an independent third-party site. It is not affiliated with, endorsed by, sponsored by or operated by the Technology Innovation Institute, and it does not speak for TII. Every number on this page is attributed to the source listed above.