It doesnt work like that. Imagine the following scenario. Im Software Company and I have Product1, Product2, Product3. The right approach is to have different Hasp family for every product. That means different Developer ID for each family. Unfortunatelly thats a little bit risky for developers because they need to have stock for every ID, example 20 hasps for Product1, 20 hasps for Product2 and 10 hashs for Product3. What will happen if they ran out of hasps for Product2? They need to order new hasps because the other 2 families are incompatible. And the ordering takes about 2 weeks - to 1 month. Maybe more. Thats why some developers they get one developer ID/family hasp and they alter the memory data to allow differents products to be executed. If you open the HaspEdit software (the one from alladin) you can see it has a "FAS" button. That button allows you to control what module/applications can run with that hasp. So what developer is doing, he's puting number "1" for Product1, number "2" product2 and number "3" for product3. So his application is checking for that number that is inside the hasp. Of course if you own the passwords you can use the Hasp memory easily and change that option and run all programs from the same company. If you want HaspEdit utility, i can upload here.