3 ms·
Ask HN: free-personal/paid-commercial licensing model
I'm considering adopting a licensing model that permits free personal use and requires purchasing a license for commercial use. Quick Google search brought up few examples:
* http://www.jetbrains.com/idea/buy/buy.jsp - Java IDE
* http://free.avg.com/download-avg-anti-virus-free-edition - AVG Antivirus
* https://secure.logmein.com/products/hamachi/licensing.asp - VPN service
Berkeley DB is (sort of) of this variety and so is the Aladdin Ghostscript license. Are there any obviously notable examples out there ?
Does anyone has any experience with this model ? From either side - as a licensor or a licensee.
Thanks
(edit) I though I'd elaborate on this a bit. First of all, the context is a standalone application. Its target audience is not dumb users, but the app is not very specialized either. It is equally useful to both the home users and IT professionals.
Secondly, my take on the above model is this. It is viable because it appeals to the users who are
* capable of paying (from the company budget)
* generally feel obligated to pay (due to internal IT practices)
* and who are easier to part with the money (as it's not their own)
In case of home users neither of these three points holds. The only way to facilitate the payment is to appeal to their conscience (by nagging, by enforcing the restrictions via some sort of DRM mechanism, etc) - very .. err .. uncertain and effort-intensive endeavor compared to focusing on commercial users only.
Also, giving away fully-functional version under some sort of a free license effectively counters the need for hacked "full version" and eliminates the need for the licensing enforcement provisions in the application. Former helps to maintain greater control over the installation base and latter makes for a cleaner and simpler application.
- noodle 18y agoas a licensee, i would suggest that you not bother. too many people are dishonest about it, and too many things blur the lines between personal and commercial usage. looking back at it, i've installed something intended for personal use, but later on used it for commercial use, totally forgetting about the license agreement. one product in particular, i can think of, i would've paid for if i would've remembered. but they went under. probably from the license that few paid for. instead, i would suggest you offer two version, a "lite" version for free and a fully-featured version for $$$.
- huhtenberg 18y ago> but later on used it for commercial use This is remedied by periodic re-verification of the usage purpose when in personal license mode. I am wary of lite/pro model, because it complicates the offering. Looking through the feature comparison matrix may be quite confusing, especially if pro version is packed with not so frequently used features. Also, if too many features are withheld from the lite version, it will drive users to use 'patched' pro versions. On other hand, if the lite version is liberal, the pro version will suffer as its usefulness will decline. Finding a balance depends on knowing your userbase and the userbase won't stabilize until the lite/pro matrix is stable. So it's a catch 22.
- noodle 18y ago> This is remedied by periodic re-verification of the usage purpose when in personal license mode. this "might" be remedied by periodic re-verification. again, you're fully relying on the individuals being honest and reporting their own usage. i'm just pointing out that your revenue stream is going to be inconsistent. with respect to lite/pro model, look at the 37signals products. they've definitely made headway with the pro/lite model. they don't strip away many features, but they also limit the product in other ways.
- huhtenberg 18y ago> you're fully relying on the individuals being honest and reporting their own usage Both models rely on this. Just keep in mind it's not a service, but an application. There's no way to enforce certain usage, so it comes down to whether you want dishonest users running a hacked version or the original app (and thus allow them an option of going straight at some point).
- noodle 18y agothere's a big difference between someone clicking "personal" on your popup to be dishonest on the personal/commercial license model, and someone spending the time to crack and reverse engineer your product to be dishonest with the lite/pro license model. i disagree with your assertion that there's no way to enforce certain usage.
- emmett 18y ago30 or 60 day free trial, and after that an infinite-use key available for $X. That's what convinced me to buy TextMate and many other software products that I use.
- huhtenberg 18y agoAh, good point. I meant to say there is a N days trial period if you are uncertain which license you are going to use. This is effectively needed to enable trialing the app in commercial setups.
- emmett 18y agoI wouldn't make a distinction. Your work is worth something, charge for it!
- huhtenberg 18y agoWell, there's more than one way to charge for it. I can try and charge everyone $10 a pop or focus on a selected few and sell $1000 licenses. There are few elements in play here including who's a target audience, the feature set, the simplicity of the offering, the good will attitude towards the users, the license enforcement issues, etc. The goal is to weight and balance so them so that to maximize the revenue. The model I am looking at looks very promising from many angles, so I wanted to evaluate it from other angles that I am not perhaps considering.