My comments are coming from 2 different perspectives, developer & system administrator. The system administrator, in an Intranet environment, will usually be the "host" for most installations. The reason being is if a server is running on the network the system administrator is responsible for all hardware/software/security, etc.
As a system administrator, licensing needs to make my job easier when I need to get approval for a purchase. It cannot be complicated to explain. It needs to be flexible allow for real world situations such as development servers, local installs, etc. I also am not referring to a $25.00 module that comes with free lifetime updates until the planet explodes.
LICENSING - Non-Hosting
Single Server - Permits module use on a single server without limit to number of portals.
Permits use on a development/proof of concept server.
This license is intended for an Intranet site or company site where the number of portals are all related to the same company and used by the same set of users or customers.
LICENSING - Hosting
Single Server - Permits module use on a single server without limit to the number of portals.
The cost of this license would be 10, 20 or xx times the cost of a non-hosting license.
LICENSING - Single Portal
Single Portal - This license will cover the majority of single site users with a small number of users.
These are just some initial thoughts. There needs to be a substantial difference in licensing for a hosting company.
mikez