TurboFloat server access through internet

Is the TurboFloat server limited to intranet/network or is there capability to access a TurboFloat server through internet?

You can access a TurboFloat Server instance from either the just inside LAN or from all over the Internet. It's all in how the customer allows access to the TFS. That is, whether they allow connections from the Internet as a whole to the computer that is running the TFS instance.

Does that make sense?

PS. Sorry, related question, pricing for TurboFloat? I couldn't find it on the site after a quick search.

It's available for everyone. The "Plus" plan and above get unrestricted number of floating licenses. The Basic/Solo/Free plans get 10 free "floating licenses" so they can test TurboFloat to see if it fits their needs. We cover this on the signup page and on your account page.

Hi Wyatt,

Yes it does make sense and I also saw this morning about the inclusion of TFS in certain plans. Since we have the top plan then it is included of course. That's great, we have requests from customers for floating license scheme.

I'd like to understand better what would happen if more than one products need floating licenses on the same infrastructure? From what I know so far a floating license product key has to be created for that product and then used to activate the server. Then the server has to be installed. For further products, do we just "activate" other instances of the server? Or do we have to do the full installation process again (i.e. activate and install)? Can you corroborate or elaborate?

Thanks!

I'd like to understand better what would happen if more than one products need floating licenses on the same infrastructure?

Each product version needs its own TurboFloat Server instance. So if you have YourApp 1.0, YourApp 2.0, and AppX, then they will need their own TurboFloat Server instance.

This means each will need to be activated with their own serial numbers. Also, you either need to run each TurboFloat Server from commandline or install each TurboFloat Server. In production you're more likely to just install the TurboFloat Servers.

Your customers can install and run each TurboFloat Server instance on the same computer, but they'll need to use a separate port for every instance. Or the customer can just install each TFS instance on a separate computer (and thus a separate IP address).

Important clarification on the port number. Thank you!

Actually, speaking of ports, I will need to provide requirements and firewall information to customers.

- What exactly are those port numbers used for client-server comm? Are they tcp/ip ports? If not I will need to know what protocol is used.- I'm assuming that the server activates and validates licenses using a process similar to TurboActivate? So the same requirements (port 80, LimeLM site access, etc) would apply for TurboFloat. Please confirm.- Is there anything else, network-wise, that would need to be communicated to the customers?

Thank you!

- What exactly are those port numbers used for client-server comm? Are they tcp/ip ports? If not I will need to know what protocol is used.

The port is used for client/server communication using TCP. The actual data is binary blobs. That is, the data isn't a "known format" like HTTP.

- I'm assuming that the server activates and validates licenses using a process similar to TurboActivate? So the same requirements (port 80, LimeLM site access, etc) would apply for TurboFloat. Please confirm.

Yep. We made that clearer in the documentation.

- Is there anything else, network-wise, that would need to be communicated to the customers?

Nope, that's about it.

Thank you!

- Is there anything else, network-wise, that would need to be communicated to the customers?

I've got one ... customers may need to open up your port(s) on their firewall, a lot of big corps block everything that is useful. You should investigate that because network engineers are notoriously unresponsive (they are human firewalls)