GenRocket is licensed on a per “named user" or "named server” basis.


Named Users:

                                                                        

We use the term “named user” because GenRocket users are usually software testers and software testers sometimes change jobs and roles so the named user can be reassigned in the GenRocket system to a new named user during the license period.

                                                      

Named users access the GenRocket hosted system - for example the Virtual Private Cloud to create test data Projects where they create test data generation Scenarios that will generate test data for different software testing test cases. To access the Virtual Private Cloud the named user needs to be a valid, registered user in that system.

                                               

When the tester is ready to generate test data the encrypted Scenario is downloaded from the Virtual Private Cloud to a local machine that has the GenRocket Runtime installed on it. When the test data generation Scenario runs there is a license check and as long as the license is valid the Scenario runs and test data is generated.


Some Named users have a desktop and a laptop machine for their work. This structure is fine as long as the test data generation Scenarios are only run on one or the other machine at a time and never two machines associated to the same named user at the same time.
                               
Named Servers:
                                                        

We use the term “named server” because sometimes a testing automation server has the GenRocket Runtime installed on it so that it can run test data generation Scenarios. Any “named server” that is executing GenRocket Scenarios to generate data needs to be registered in the GenRocket system. When the software tests run on the automation server and call the GenRocket test data generation Scenarios to generate data there is a license check that validates the “named server”.


We use the term “named server” because testing automation servers are sometimes changed so the named server can be reassigned in the GenRocket system to a new named server during the license period.