Licensing PS extensions

Question

I need help on how to license an extension for a PS that I've created or how to limit the use of the extension to the appropriate users and for an appropriate period of time?

Kukurykus · Accepted Answer

From your first post and the first sentence of the second post, it would be concluded that my entire work is based on barowing code, which is not true and which honestly offended me.

For the second part of your answer, i never said anything bad, evenmore I am grateful to you for the specific answer as well as for all the correct answers with which you solved many of my questions.

I transferred the code to jsxbin if it's safe enough, but I still don't know how to control unlimited use and sharing of my content?!

I work in company where I dispose Bridge / Photoshop codes to different users who mostly are engaged into different part of overall work. That may be different on your side, but just for example when you know their usual place they work at you may exclude part of script to be working only on certain computer (due to its user computer name etc) also less necessarily at some hours or else with option to log in every Monday with a password automatically beeing sent to that user E-Mail etc).

The licensing is more adequate for people who sell the product, here I understand you are in some control of company machines and in some contact with employess. It's more convininet to make main conditional script you keep on company server the other computers are linked to, but their users can't access its content beside given singly allowed functionality.

When you want to make some change, edit the script on server and the updates will be done on each computer at same time, including swaping used script functions when for any reason people are going to change their seats. You don't have to use .jsxbin, or operate individually other computers until someone removes PS from own workstation with important stuff.

btw the first post was answered by you in other manner, so after my another reply I didn't think you may get back to initial response, to note in your feeling the accusatory than humourous tone at the second approach.

erinferinferinf · Answer

Hi!

So, if you distribute on the Exchange Marketplace, the current backend runs through a company called FastSpring. Here's some advice from other plugin developers:

Fastspring requires you to generate your own licenses, but they’re pretty flexible. We use both JS code to generate (entirely on their machinery) in one case, and also a REST call to our own license server code running on AWS.

Some developers use Gumroad to distribute, and work with Gumroad's API to do licenses:

Plugin in the user's PC sends the license key in REST API into Gumroad server and server replies whether the key is still valid. Gumroad API Reference Licenses So unlocking itself happens in Gumroad server along with purchase.

There's also a service called SoftwareKey:

SoftwareKey is a vendor that handles the license generation, node locking, and “phone home” calls. That all happens on the client but is done in a library. Cross platform Mac/Windows. It pairs with FastSpring and is reasonably priced.

Some developers tie into Paypal:

Paypal also has an easy API... But then you have to generate your own licenses.

Ideally, Adobe would offer something like this that ties to a user's AdobeID (without the developer getting user's personal information). That's often requested, and it might happen in the future, but isn't in place now (so we're talking minimally one to two years before you could expect that).

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded