You can license your project however <i>you</i> would like to. You absolutely can have a license with text that is similar to the MIT license, except with a clause saying that company X can't use it. However, as other commentators here point out, you could not, in good faith, call that "open source" under the standard, accepted definitions of that term.<p>So the answer to "is there any way to achieve this?" is twofold. If the question is "can I achieve this and still legitimately use the term 'Open source software'?", the answer is a flat-out "no". If the question is "can I set it up legally in this way, without regards to the terminology", the answer is yes.<p>A license is a pretty free-form thing. You can write whatever text there you want. You may wish to consult with a lawyer, in order to get some legal assurance that what you wrote makes legal sense and will hold up in court. This is especially true if you want to be very sure that you didn't accidentally leave some loophole in your wording that will allow the company you dislike to use your project against your will.<p>You are going to have to write the text of this license yourself (or pay a lawyer to do it for you): you're not going to find much of this kind of "almost-OSS" license out there for you to base yours off of, because in general, those who want to license their software as OSS actually do want a fully OSS license. But there are a few examples, although not <i>quite</i> identical in spirit to your "use case" (excluding a particular company) but instead different variations of not-quite open source. For instance, you can take a look at MongoDB's SSPL (<a href="https://www.mongodb.com/licensing/server-side-public-license" rel="nofollow">https://www.mongodb.com/licensing/server-side-public-license</a>), and Redis Lab's RSAL (<a href="https://live-redislabs.pantheonsite.io/wp-content/uploads/2019/02/Redis-Source-Available-License-PDF.pdf" rel="nofollow">https://live-redislabs.pantheonsite.io/wp-content/uploads/20...</a>).