Hey Jan,
we love your product.
I'm glad to hear that. 🙂
So: is there a way we can enable floating licenses for (five) EC2 instances that end 1 year after the activation? I figure the only way would be requiring the FloatingLicense Sever to connect once for the activation at least with the activation server (plus at times after)
Floating licenses would be the best option. You could use TurboActivate as well, but EC2 and AWS servers aren't real servers -- so the fingerprints change if the "machine" is shut down and then booted back up again (because they're glorified VMs running on different hardware).
Short answer: TurboFloat is the best solution to that problem.
- Offline trial extensions & TurboFloat: End the trial after 100 days; No internet connection required; No control over # computers
I don't know where your read that, but with the TurboFloat Server (even if it's activated offline) you can limit precisely how many computers will be able to request and get license leases. So you can limit it to 5. And set a custom license field for the product key with a set "expiration date". Read the license field in your app using TF_GetFeature(), and if the date has passed, then the customer can no longer use your app.
You can do this with online activations too.
Do you have any recommendations of the time period we should use to check whether the license is still active? I would probably set it to 13 months or so "to be safe" - but I carefully want to check whether there may be some hidden downside I do not recognize with those very long periods (e.g. swifty way to actually use it 24+ months).
We recommend 90 days (and that's the maximum number of days it can be set to).
Tell me if that helps.