Protection against unauthorized redeployment of PHP applications


I was wondering what options do we have? PHP is open, I know. But what if I want to bind my work to one server, so that a client could not resell / steal my work. I run my own server, so I can provide a remote authorization mechanism, but I'm not yet aware of any.

What options do we have? Zend is paid and useless because of DeZender; ditto ionCube. So, what are our protection options?




No app is safe if it is on customer's premises, whatever the technology is. So the only way to keep is safe is just to self-host it... The harder you try, the more bugs and performance losses you introduce, and the result is always uncertain.

Ioncube and zend are options which help you to discourage reverse engineering and access to code, but they won't stop a determined user.

But remember that the tecnical mean is always just a part of the game. The other part is a properly written and signed EULA or agreement with your customer.

People are also looking for solutions to the problem: php - Day count - calculation and remove the minus


Didn't find the answer?

Our community is visited by hundreds of web development professionals every day. Ask your question and get a quick answer for free.

Ask a Question

Write quick answer

Do you know the answer to this question? Write a quick response to it. With your help, we will make our community stronger.

Similar questions

Find the answer in similar questions on our website.