Monthly subscriptions

Hello,

I'm looking to implement a monthly subscription service in my application.I want to give to registered users (no time trial here) an activation key.A month later, I'll get the list of users that paid the montly subscription and make a bulk activation of those licenses.

1) Is this scenario possible with LimeLM?2) LimeLM detects clock changes, so my clients do not reuse the "suscription" by reversing the clock?3) What function do I need to call every month to update the license? I don't want to bother the client, so this must be done silently.

Actually I'm using a LimeLM free account (for testing purposes). I can manage only one user, so my question is:There is a way to limiting what products/custom fields can activate a user?

Last one, my business accepts delivering software through distributors (I want to give n activation keys to them), so I'd like to know a little about the level of protection that you're offering. I know that it's impossible to avoid being cracked, but as far I've tested with LimeLM, if one of my distributors knows how to NOP a JMP is enough to get registered forever.

Thank you,Ernesto

Hey Ernesto,

1) Is this scenario possible with LimeLM?

Yes.

2) LimeLM detects clock changes, so my clients do not reuse the "suscription" by reversing the clock?

Yes, we have some time fraud protections. We're adding more with each new version.

3) What function do I need to call every month to update the license? I don't want to bother the client, so this must be done silently.

IsGenuineEx() will automatically re-activate if it needs to. So set that to every 30 days and it will get the latest fields.

Actually I'm using a LimeLM free account (for testing purposes). I can manage only one user, so my question is:There is a way to limiting what products/custom fields can activate a user?

I'm not sure I understand this question. Are you asking about LimeLM users that you want to manage your account? If that's what you're talking about then yes, you can broadly set what a user can do.

If you want more fine-grained control then you can make your own API for your resellers/distributors to user. That is, have a script on your server that these distributors can call that will generate keys, renew license fields, etc. Then the script will call the appropriate LimeLM web API function.

Does that make sense?

I know that it's impossible to avoid being cracked, but as far I've tested with LimeLM, if one of my distributors knows how to NOP a JMP is enough to get registered forever.

There are lots of licensing companies that lie to customers to win business. They come up with elaborate "anti-crack" schemes (all of which are easily breakable). We choose not to lie to our customers. Every software protection in existence can be cracked easily.

But as we say in the "What is hardware-locked licensing and why choose LimeLM?" article:

The point of licensing isn't to stop crackers from cracking your software. The point of licensing is to increase your revenue by preventing casual piracy (using serials over and over again). There is real money to be made by stopping casual piracy.

In fact, in the "What is hardware-locked licensing and why choose LimeLM?" article we go in depth into what LimeLM does, how hardware locked licensing works.