How LimeLM handles upgrades ?

Yes, this is all possible with LimeLM.

-hardware lock-in

Yes, LimeLM is hardware-locked licensing.

-I would like my software not to require internet access (other than activation but not for everyday use)

Sure, you can use TurboActivate like this (TurboActivate is the part of LimeLM you include with your app). The initial activation can be done either online or offline and you can have it so your app never re-verifies with the activation servers.

-I don't mind (and actually prefer) that users download the upgrades themselves (no auto-upgrades)

That's fine.

-I would like to make their old license/serial work for upgraded version -I would like to be able to release 2.0/3.0 version of my software for which their old license no longer work

Ok, so you'd like free "minor updates" and paid major upgrades. You can do that with LimeLM. For the same minor versions of your app, just use the same version in LimeLM. For new "major upgrades" create a new version in LimeLM and those new keys won't work with the old version (and vice versa).

Does that make sense?

Yes it does, thank you.While I still don't understand how the details work I guess it will become apparent once I try to integrate LimeLM wtih my software.It's still several weeks till I am at that stage but I will surely give LimeLM a go and come back here if problems occur 🙂

One more question:My software can benefit from custom compiles (different for i7, different for Haswell, different for Xeon with a lot of cores etc.). Will it be possible for me to create those (and maybe add some specific user specific features) in those and have LimeLM treat them as the same product ? (so again I can provide minor upgrades for free etc.)

Will it be possible for me to create those (and maybe add some specific user specific features) in those and have LimeLM treat them as the same product ? (so again I can provide minor upgrades for free etc.)

Yes, using the same version in LimeLM you'll be able to do that (the free updates).

And using custom license fields you'll be able to specify build-specific or user-specific features.

>>And using custom license fields you'll be able to specify build-specific or user-specific features.

I understand but what I am asking for is if it's possible to me to build executables specifically for given clients. Those will be very different executables (depending on instruction sets of the target CPU but also some personal wishes of my clients). It's not going to be "enabling features" but custom executables with parts of code which don't exists in other ones. I just want to make sure that if I produce 100 custom executables, compile with AVX2 here, without there, include some custom API functions here but not there those won't be treated as separate products (because then only MAX plan would be suitable for me and that is too much as I am just starting).

Yes, you can do that too (making custom builds that use the same product keys).

Thanks.It seems everything I need is there then. Can't wait to start integrating with LimeLM 🙂