ionCube Logo
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 


 
Post new topic   Reply to topic    ionCube Forum Index -> Suggestions and Feedback

There's a proper workflow to release a encoded software?

Author Message
musikdoktor



Joined: 06 Jul 2021
Posts: 3

PostPosted: Tue Jul 06, 2021 8:58 pm    Post subject: There's a proper workflow to release a encoded software? Reply with quote

Hi guys, im new with ioncube enconder and i would like to ask for some advice about what is the best workflow to use the encoder.

I mean, i have a product that i want to sell, but i don't really get how to use in a real scenario..

Imagine i have a few customers.. 4... Have to encode every version for each customer?? create one and distribute it?? but there's no keygen so that's seems is not the right way.. but encode all the program for every single customer also sounds weird and complicated.. Then? how to deal with the upgrades??

If you have 1 customer there's no problem but if you have 10?? or more??

Anyone can explain the best workflow to use ioncube encoder with few customers?

Sorry if the question is not clear..will try to be more specific.. Thanks
Back to top
View user's profile Send private message
liaison
ionCube Support


Joined: 16 Dec 2004
Posts: 2827

PostPosted: Wed Jul 28, 2021 1:24 pm    Post subject: Reply with quote

The typical way would be to use Pro or Cerberus and create license files for customers. Encode once for each release, use a unique license passphrase so a license file for one variant cannot be used with another (e.g. so a license for a "lite" version won't work with a "full" version), create a license file for each customer.

When you release an update, everyone can have the same update and their license file will work with the update. License files can have key/value properties, and these can be read via an API call in the Loader, providing a way to make available customer specific data to the generic code.

Some customers accumulate license settings for all customers into a single file, but this is not ideal. We would recommend a unique license file per customer, and keep a record of the license details for each customer in e.g. a database so you can recreate the license files if needed.
_________________
Community Admin
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    ionCube Forum Index -> Suggestions and Feedback All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum