Web Connection is licensed per developer and/or per physical or virtual Windows Server instance.
Licenses can be interchangeably used for:
- Developer Licenses
- Physical/Virtual Server Runtime Licenses
The Full Web Connection Developer License ships with a one Developer and one Server License, so a single developer can build and deploy one or more applications on a single physical or virtual Windows server.
For additional Server Runtime licenses or additional Developers licenses, runtime license packs can be purchased. Runtime licenses can be applied either to a physical/virtual server OR an additional developer. A single Full Developer license is required in all licensing scenarios as it provides the actual application and source files needed to build your application.
Server Licenses are applicable to a Windows Instance which means either a bare metal server running Windows directly, or a Virtual Machine running a virtual instance of Windows.
The full developer license comes with a single developer license and one live server license, so you can develop your application on your local machine and deploy it on a single live server or Virtual Machine instance. The full developer license provides full source code to the FoxPro framework code, and is required for any further runtime or developer licenses to be applied.
Any additional developers require another developer license or runtime license seat.
Runtime licensing is available by purchasing a runtime license pack which comes in sizes from 5 up to unlimited distributions. A run-time license can only be purchased in addition to at least one full developer license as the run-time licenses do not come with any distributables or code - it's just a license pack.
Runtime license counts can be used for either:
- Per Windows Instance physical or virtual Server Licenses
- Developer Licenses
You can check out pricing for runtime licenses here:
Runtime licenses can be used for licensing Web Connection on a Production Server.
Each runtime license is good for a single physical server or virtual machine instance. Essentially, Web Connection is licensed per Windows instance.
You are allowed to run multiple Web Connection applications on a single Windows instance. So for example, you can run multiple domains that run separate Web Connection applications on a single Windows Server instance. Any additional physical or virtual Windows instances, including load balanced servers in a cluster or additional multiple machines used for backup or fallback recovery, require an additional Web Connection license.
A run-time license allows distribution of a compiled Web Connection application and distribution of any of the binary files included with Web Connection. No portions of the Web Connection framework may be re-distributed as source code without a full developer license. If your application distribution for clients requires source code that includes the Web Connection source code or any part of it, your client will need a source code license.
Runtime applications can make use of any of the framework classes supplied by the Web Connection framework including the HTML rendering classes and support tools as long as distributed in compiled form (APP/EXE).
If you distribute your Web Connection application with source code that includes the Web Connection libraries, each distribution point or end user then requires a full development license. To avoid this requirement, you can ship your application as compiled EXE/APP files.
Run-time licenses can also be applied against additional developers.
Any developer working with Web Connection to build or maintain a Web Connection application is required to have a license whether it is a standalone developer license or one of the runtime licenses.
To make it easier to understand licensing here are a few different scenarios for runtime licensing.
As a broad rule, if you need more than 2 developers or two deployed sites, runtime licenses offer a large discount over individual Web Connection developer licenses. Just keep in mind that a single Web Connection developer license is always required for any organization in order to purchase additional Runtime Licenses.
A single developer can purchase a Web Connection developer license and use that license to develop the application on the local machine, and deploy Web applications to a single live Windows server instance. This means if you are a consultant and you need to build an application for a single customer, the single developer license is all you need.
If you're a single developer with multiple deployed physical servers you need to have a single Web Connection developer license, plus additional runtime server licenses for each additional site deployed beyond the first one.
If you have 2 sites deployed your best bet is to use two full developer licenses:
For more than 2 sites it's cheaper to use the 2 or 5 license pack on top of the full developer runtime:
If you have multiple developers and multiple sites you'll almost certainly will want to take advantage of the runtime license discounts. A single developer license can be purchased and each developer can use a runtime license count as a developer license.
Note: A single Developer License is always required
Multiple Developers and Server:
The following rules apply:
Every Web Connection installation requires at least one full developer license. Runtime licenses can then purchased for additional distribution or developer licenses on top of the developer license.
Every Developer using Web Connection to build or debug Web Connection applications has to have a license.
Every Windows Instance (Server or Client, physical or Virtual Machine) that Web Connection is deployed to requires a license.
The base single developer Web Connection license includes a developer license and allows deploying to a single Windows instance for a deployed application. The developer license is essentially all a single developer needs to build and get an application online.
You may modify the source code and visual appearance of the Visual FoxPro Web Connection framework. Regardless of any changes made to the framework itself, it remains copyright of West Wind Technologies. Modification of any non Visual FoxPro binary files is not allowed.
IN NO EVENT SHALL THE AUTHOR, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THIS PROGRAM AND DOCUMENTATION, BE LIABLE FOR ANY COMMERCIAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM INCLUDING, BUT NOT LIMITED TO, LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS, EVEN IF YOU OR OTHER PARTIES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Comment or report problem with topic