We want our internal software builds to be license-protected as well in case of a leak. Furthermore, we want these internal builds to be incompatible with the licenses we issue our customers. I see 2 ways to achieve this:

• Use different seeds for internal and external licenses
• Use a special prefix for all features in internal builds

Option 1 "feels" more resilient but are there possible issues I am not aware of?

I believe it would not be possible to host the internal and external daemon on the same internal license server since they share the same name.

Is there another way of achieving the separation that I am not aware of?