TurboActivate compatible with Amazon EC2

You can use TurboActivate with Amazon EC2, however you must take into account that every time you stop and start an EC2 instance, the instance will be on a completely different physical machine. And because TurboActivate is hardware-locked licensing, this means every time the customer shuts down the EC2 instance with your app on it, the next time they start the machine (and your app) TurboActivate will say they're not activated (because the machines are different).

See: Licensing from inside a virtual machine or hypervisor

So you have 2 choices for customers running on EC2:

1. Tell them to never shut down their EC2 instance (my guess is that won't fly).

or...

2. Let them use a version of your app that has TurboFloat integrated. Then they can install the TurboFloat Server on a real computer somewhere (it doesn't need to be installed on "server hardware" just any old computer will do)

And your app (using TurboFloat) will connect the TurboFloat Server hosted on their computer. So they can start and stop the EC2 instance all they want and the TurboFloat Server will just work.

Does that make sense?

Finally, my customer will wait to buy my software - we are still in beta.

However, right now i am on solo plan - we are still a 1 month old startup so we are really getting customers one by one - so going on the Plus plan is out of our budget to maybe get 1 or 2 customers in the next year. However we neither afford to lose any EC2 customers that would show up.

Maybe you should look to either include 5% of activations as TurboFloat - in the Solo and Basic plan. That way it will be easier for startup to grow with their plan - at the same time maybe we'll need to upgrade plan faster if we were getting more of those EC2 customers.

Or maybe have a TurboFloat offer for solo/basic like 1$ a month per activation ?

Is it a lot of job to add TurboFloat support ? We are on Adobe Air.

Every plan comes with 10 free floating licenses. We have no immediate plans to do micro plans or to make the pricing more complicated.

Ok thanks.

I didn't know there was ten licenses included with the solo/basic plans - this should be enough for the few clients that could need this in the next year or two.

I will spend some time looking to implement that soon.

Hi Guys,

I was thinking of something that could probably work for EC2:- When you close your application or when a "shutdown" is detected, simply call Deactivate().- Every time you start your application again, call Activate() again.

In so doing, the key is released every time the software is not used or when it is used yet a shutdown is asked, and the key will be registered properly every time the software has to run. But you should do that only on EC2 hardware.

The same technique could be used with TurboFloat when it will be possible to "deactivate".

Maybe Wyatt would have a better suggestion along this way. For example, is it possible to call Deactivate() when IsActivated() returns false? If yes, then just "try" to call Deactivate() in such a case, a Activate() right after. This would be much better, if it is possible.

Best regards,Alexandre Leclerc

For example, is it possible to call Deactivate() when IsActivated() returns false?

No.

I was thinking of something that could probably work for EC2:- When you close your application or when a "shutdown" is detected, simply call Deactivate().- Every time you start your application again, call Activate() again.

That works only if the customer configured their EC2 to allow outside connections to our activation servers. And if they keep their EC2 instance up until Deactivate() is successfully called. We've found must end-users won't do either of those things.

That's why TurboFloat / TurboFloat Server is the best option for EC2 and similar "cloud" providers.