Ask HN: What licensing software are you choosing for your projects?
Just looking for productive discussion as to what should drive design decisions / choices. I have some projects I would eventually like to make available for sale..and I really would like to host my own licensing software so that I keep everything in house except the payment portion. (I deal with PCI compliance enough with my day job)
So, lets say you want to sell your programming project / application or whatever. What licensing stack are you going with? For example, lets say you want to limit installs of your application to X number of machines. Do you use something like keygen.sh community edition? ChargePanda? I'm just curious what experience people have in this regard and what licensing model they went with.
I'm asking it here because I think its tech related since your code has to support the licensing stack. (I use a mix of C#, Electron / react, etc) so discussion on developer experience plus application stack is also welcome. That includes discussion around how you lock down your application to only working when licensed / or if you support trial license etc.
Thanks!
Also curious what works well for others here.
Are limiting the # of machines a user is signed-in on and trial licenses the only use-cases you have for this?
That's a good question. It was more an example. I am definitely interested in what model people have chosen. A concrete example is I have a cross platform personal finance app. (win, lin, mac). Its not cloud based or anything. So, I am at the point where I want to think about how to license I guess which is what inspired my question.