If you&#x27;re referring to the sentence [1]:<p>&quot;If you want to use Intro.js for a commercial application, theme or plugin the commercial license is the appropriate license.&quot;<p>...It&#x27;s not saying you <i>have</i> to purchase a licence if you want to use the software commercially, but that the author <i>recommends</i> purchasing the commercial licence, which they are perfectly within their rights to do.<p>There is absolutely nothing stopping you from using the software under the terms of the MIT License, but in that case you will have to abide by the terms of the licence and include the copyright and permission notices when re-distributing (the commercial licence may or may not have these requirements -- I haven&#x27;t seen it).<p>According to the Intro.js website, the top two tiers of the commercial plan includes support and code review [2], which aren&#x27;t included with the MIT License.<p>Depending on the situation, one licence may be favourable than the other. It&#x27;s not too dissimilar to MySQL being available under a free licence as well as a proprietary licence -- it provides a choice. At least, that&#x27;s how things are as far as I can tell.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;usablica&#x2F;intro.js&#x2F;blob&#x2F;master&#x2F;license.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;usablica&#x2F;intro.js&#x2F;blob&#x2F;master&#x2F;license.md</a><p>[2] <a href="http:&#x2F;&#x2F;introjs.com&#x2F;#commercial" rel="nofollow">http:&#x2F;&#x2F;introjs.com&#x2F;#commercial</a>