Re:Show HN: Keygen – A dead-simple software licensing API bu...
by ezekg on Monday June 12, 2017 @09:57PM
(#14542444)
Since my initial product is an API, it's going to have limited support simply due to the nature of the product. You can set up licenses to require periodic check-ins (e.g. phone check-ins or something similar via an online form may work), but other than that, Keygen needs a periodic internet connection. How would you envision Keygen working offline?
[ Parent
| on HN ]
Re:Show HN: Keygen – A dead-simple software licensing API bu...
by dgudkov on Tuesday June 13, 2017 @01:59AM
(#14543076)
Customer logs into a web portal and pastes some hash generated by his/her instance. Then downloads a generated license key for offline use. Alternatively, a license manager installed on-premises that dispatches licenses locally based on a master license key.
PS. Internet connection is frequently not available for enterprise software.
Re:Show HN: Keygen – A dead-simple software licensing API bu...
by ezekg on Tuesday June 13, 2017 @10:13AM
(#14544808)
What would be the use of Keygen, then? Not sure if people would pay for what would essentially be a hosted web form that generates a key. I just don't see what value Keygen could bring in that situation, especially considering my initial product is an API. Regarding enterprise--I'm actually focusing on small- to medium-sized businesses right now, not enterprise; offering on-prem plans is as far as I've gone into enterprise-land.
Re:Show HN: Keygen – A dead-simple software licensing API bu...
by dgudkov on Wednesday June 14, 2017 @09:05AM
(#14552406)
>What would be the use of Keygen, then?
I don't know. I'm just describing an existing problem that I would like to have a solution for.
>a hosted web form that generates a key
Not just generates a key, but also ensures that the use pattern complies with the licensing terms. It's the same API but on-premises.
Re:Show HN: Keygen – A dead-simple software licensing API bu...
by ezekg on Wednesday June 14, 2017 @11:01AM
(#14553220)
No problem, just trying to dig a little deeper. :) I do offer on-prem installs of Keygen in a dockerized container i.e. an enterprise plan, so it could most definitely be installed in a locked down network. Other than that, you could also set up a policy that requires licenses to 'check-in' at an interval e.g. once a month to remain valid. You could then set up a web form they could visit that let customers 'check-in' all of their nodes somehow and purchase additional licenses if needed. (Just brain storming here.)
Re:Show HN: Keygen – A dead-simple software licensing API bu...
by asmosoinio on Tuesday June 13, 2017 @12:56AM
(#14542925)
Not OP, but something like like:
1. Receive code in an email 2. Enter code in app X to license 3. Use app X
So maybe a scenario you purposely are not supporting
Re:Show HN: Keygen – A dead-simple software licensing API bu...
by ezekg on Tuesday June 13, 2017 @01:05AM
(#14542949)
Definitely a popular choice. There are open source libararies for public/private key license validation (CocoaFob is a popular one for macOS), and I don't really think this aligns with the current product i.e. the API. Maybe in the future I can expand if there's demand for it, but I'm not sure what I could offer that the open source community can't already offer. :)