How to organize a system of licenses (keys) for a PHP project?

Question

PHP

Actually the question is: there is a CRM written in PHP, partly in Java and Perl. It is necessary to organize a system of licenses (keys), as, for example, is done for most commercial CMS in PHP, well, or antivirus.
The system is strictly commercial, so the question arose not just to organize, but to create such a system with high quality and safety.
I would be glad for any information: links, articles, anything, because I found little useful on the Internet.
If there is a live example - generally just super!
Help, good IT people!

Answer 1

SaaS + API Key

Answer 2

Taking into account the fact that it is written in Java and Pearl, you can still safely sell it without keys.

Answer 3

Transfer part of the functionality to the cloud and access it via the API with a key.
Or use a SaaS approach.
Or coding through ioncube for example.
Commercial CMS by the way "zero") Such as DLE, Bitrix is ​​an example of this. Therefore, I personally really like the approach to the question from JetBrains. Those who are ready to pay will pay, and those who are not ready to pay will either not use it at all, or will use a hacked product.

Answer 4

You need to understand that in a PHP product you still give away the source code, which means it will not be difficult to find a place where the license is checked and remove the check altogether. It's just by definition. Whoever needs it will still be hacked, believe me.
You would greatly facilitate the task for yourself and users by giving the version as is.
After payment, a person receives a download link.

Answer 5

1. php zend
2. check by public IP