* The Business of Software

A former community discussing the business of software, from the smallest shareware operation to Microsoft. A part of Joel on Software.

We're closed, folks!


» Business of Software FAQ
» The Business of Software Conference (held every fall, usually in Boston)
» Forum guidelines (Please read before posting!)


Andy Brice
Successful Software

Doug Nebeker ("Doug")

Jonathan Matthews
Creator of DeepTrawl, CloudTrawl, and LeapDoc

Nicholas Hebb
BreezeTree Software

Bob Walsh
host, Startup Success Podcast author of The Web Startup Success Guide and Micro-ISV: From Vision To Reality

Patrick McKenzie
Bingo Card Creator

web server licensing

Do any of you offer a web server license to customers that want to install and run your software from their web server? If so, how do you detect if your app is being run on a web server. What do you base the license fees on?

Some of my customers are installing my softare, a c# console application, on their web server and using it as part of a data massaging process for which they charge their customers. Their customer logs in to their website, uploads data files, clicks a button to have them processed and gets the results. My software is just one small part of the data massaging . right now my customer buys one license for this and I would like to offer a web server license and charge more if used in this scenario.
Bill Anonomist Send private email
Monday, March 09, 2015
If you have a significant number of such customers, you can make that scenario the default, raising your price accordingly, and have the "non-server" customers explicitly agree to a license prohibiting such usage in order to get a lower price.
Dmitry Leskov Send private email
Tuesday, March 10, 2015
We have an ASP.NET Control, and also an underlying engine that the control uses.

When customers use our Control, it's easy because the control runs in a context where it has access to the HttpRequest, so we implicitly know it's running on a server but also use the HTTP variables to check the servername and address against our license.

When customers use the underlying engine, we don't bother checking the server details (or even if it is on a server) and just accept any valid license key.  This is less usual use case.

So, if you can, expose your process as an API (DLL/JAR) and require a request object.
Bob Frances Send private email
Tuesday, March 10, 2015
<also use the HTTP variables to check the servername and address against our license.>

Sounds like you are encrypting their servername into the license which is not something I wish to do. My strategy is to have .NET code that detects if the Windows OS is a server OS and if IIS is running then require upgrade to web server license.
Bill Anonomist Send private email
Tuesday, March 10, 2015

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz