This IAMP release is very nice news. Thank you!
I was searching for info about differences between the version we can build from github sorces and version sold at https://www.installaware.com/iamp/, but I was not able to find any. Looking at project license didn't enlighten me much. Does project license allow commercial use of setups created with it, when IAMP is built without any changes to source files? Is there a fee for that? Limitations? In what cases we have to purchase official IAMP? The same questions for noncommercial use (setups built for open source applications)?
Please clarify or give me a web link that could help with these questions.
Absolutely, thank you very much for those excellent questions.
You may certainly build commercial setups (or non-commercial setups) without having to buy the software (this use is termed "production use" in the license), including cases where you have modified the source code of the software.
What the license does prohibit is building competitors to IAMP itself, until the switchover date to the AGPL on May 19th, 2029 (for the current published version). This date will always be 4 years into the future at any time we update the published IAMP sources, ensuring our competitors cannot use our own hard work to build commercial products that directly compete with IAMP (as was the original intent of the MariaDB license).
So why would you pay for IAMP at all?
Even without any support, you will be getting
pre-packaged builds for 7 platforms, together with many setup themes and sample/template projects (the version you compile includes only one theme [although that is the
best looking Multi Platform theme, designed after the macOS PKG look], and has just the
Quick Start Wizard [no sample or template projects are included, although
Multi Platform PackageAware is included {which is snapshot based setup capture}]).
You could also buy
support, of course.
So in this sense we're rather similar to RedHat, but note that the latter do actually sell licenses which are forbidden from production use (while we don't forbid production use in any of our paid [or your own compiled] packages).