Licensing question

[cs_lf]

Hello,

we have a quick licensing question about UaGateway: the product we are evaluating UaGateway for contains a PC preinstalled with a legacy OPC server software, and an OPC UA gateway. As far as I understood your licensing terms for the machine-based license, the person installing the software on any given machine must be the licensee of UaGateway. Which is fine from our perspective, as that would be us. However, do you allow the resale of the entire machine to our customer, who would then integrate that into an even larger solution, and then sell that to their customers? We are not trying to "hide" the fact that UaGateway is used on the machine itself, if someone were to log onto that box directly, they'd see the installed software, but both our direct customer, and then especially their customers in turn, are really not the people who'd have the technical expertise to configure something like UaGateway. Hence we'd need to be able to sell the machine with UaGateway preinstalled, directly licensed from you, otherwise this wouldn't work for us. Does your standard machine-based licensing allow for this? (An OEM license is not interesting for us price-wise.)

Thanks!

[Support Team]

Hello,

the UaGateway is licensed on a "per installation" base, this license type is called "Runtime License (single installation)" regarding our SLA. The license is not transferable to an other PC. If you sell the complete machine (including the PC where UaGateway was installed) the license stays on that PC (it can not be transfered anyway). Your "preconfiguration" should make life easier for the downstream receiving customer. Even though we think that even unexperieced users can configure the UaGateway (you could provide a very short step-by-step instruction, just in case). You should switch off "none" Endpoint for example, that is what most users just forget.

However from an OPC UA perspective (and licensing technique) there are several settings that customer can not change later. One of which is the x509 certificate content required by OPC UA. Now that said the downstream receiver can not change the "hostname" of the machine later, because all the certificate (and trust relation) needs to be redone (which is doable, but not so easy for the "un-experienced"). Same applies for the license, it will brake if your customer changes the "hostname".

So the basic question here is, how "preconfigured" is this UaGateway installation in real life?

Alternatively you could let your customer install and license the UaGateway himself (he needs to buy license from us directly) and you just provide some "configuration file" to be replaced finally after that.