Pliant is copyrighted by Hubert Tonneau, contains a few external contributions (see source code), and is released under the GNU public license, version 2.
In very few words, it means that if you want to use Pliant for writing an application for your company or organization, then you have no special constrains, but if you want to release or sell the application to other companies or organizations, you have to release it under GNU public license version 2, which in very few words means that it has to be free.
If you want to write an application provided as a service (Saas), then from the GNU plublic license version 2 point of view, it's just like using it internally, as opposed to distributing it, so you have no special constrain.
Now, if you want to distribute an application written in Pliant, then keep in mind that from a technical point of view, Pliant is a dynamic compiler, so the application runs from the source code, and as a result, the GNU public license version 2 constrain stating that you have to publish your application source code should not be an extra contrain for you.
Lastly, there is a Pliant to C translator that enables to turn a Pliant application to an executable, technically suited for distributing an application without the source code, but this software is not publically available on the web. If you intend to use it, please contact Hubert Tonneau.
Pliant development model and license planned evolution
It is not very clear whether the best license for Pliant is GPL or the less restrictive LGPL.
Over it's first 10 years of existence, Pliant has not spread much if at all. Reasons are: too different, not documented, not seriously marketed, etc. Another important reason is that I was more interested in making my computing visions progress, I mean moving forward on the concepts, than spreading already implemented parts. Many external contributors would have meant spending more time coordinating than thinking, and more progress at features than concepts level.
These 10 years have been just enough for me to understand what I'm good and not to work at and so decide a suitable organization for Pliant taking off.
There comes the final organization from: I'm not targeting Pliant for end users or end developers, but rather for people that want to start something new (an application or a product or a company) in a year or so. So external contributors are welcome to fill the gap with end users needs, either through concentrating on proper packaging, or features enhancing of one part, or providing more focused application framework, or providing high quality courses, etc.
Now, if the GPL license is not suited for enabling some Pliant contributors to be fairly rewarded, then I will provide the extra license suited for each particular case, and if at some point the fact that I decide it seems abusive, then it will be time to create a foundation.