We often get this question about the licenses that Open-DocumentLibrary is sold under. In this article, we will try to answer it.
An important premise to what follows, is that you can install your module on as many pages (tabs) as you like on the portal that the module is licensed for. In other words, within a portal, there is no limit to the instances of the module you can have.
Single Domain License
The Single Domain License agreement that O-DL is sold under, usually corresponds to 1 license 1 DNN installation paradigm but it is not always so.
The intent of the license is to allow the installation of the module so that it can only be accessed by a unique domain name. So, here are various scenarious:
Allowed by Single Domain License:
You have a DNN portal, reacheable through the http://www.domain.com url.
You then create various child portals (off of the same DNN install), reacheable through a sub-domain name or through a modified url such as:
http://mySubPortal.domain.com
http://www.domain.com/mySubPortal
Allowed by Single Domain License:
In a scenario where a Web Farm exists (multiple DNN installs on multiple servers), would allow you to install the module, without the need to purchase additional licenses.
NOT Allowed by Single Domain License:
On the other hand, if you have a single DNN install that can be reached through various domain names such as:
www.domain1.com
www.myDomain2.com
www.anotherDomain.com
Then you would need to purchase as many licenses as domains, even if all the domain point to the same DNN portal and the same server
Enterprise 1 Server License
To remove some of the shortcomings of the Single Domain License, the Enterprise 1 Server License was created.
This license removes the Single Domain restrictions as described, and basically allows you to install all the modules you want on all the portals you need, as long as they are physically located in the same server.
The license is specifically thought for companies that do their own hosting, and have many clients.
Source Code License
It is subject to all the restrictions of the Single Domain license, but adds the possibility of modifying the code to suit your needs.
Should you want to apply the changes that you made on the source to another domain, you would then be required to purchase an additional Single Domain License (not the source again).
We hope that this will clear some doubts and questions you may have. If not all is clear, please feel free to ask.
The Xepient Solutions Team