4 ms·
You could monetise via an "insiders" lane. Like the way material for mkdocs works. https://squidfunk.github.io/mkdocs-material/insiders/ https://squidfunk.githu
by CraigJPerry 5y ago
You could monetise via an "insiders" lane. Like the way material for mkdocs works. https://squidfunk.github.io/mkdocs-material/insiders/ https://squidfunk.github.io/mkdocs-material/insiders/
- mtlynch 5y agoOh, that's interesting. I'm doing something like that now, except the premium features are just in a Pro version.[0] There are only a handful of purchases per month of the Pro version, and I've wondered whether I should scrap it for some other model. It's possible that even though people don't buy the software standalone, it's part of what makes people purchase hardware kits from me, as the hardware packages all include the Pro license. [0] https://tinypilotkvm.com/product/tinypilot-pro https://tinypilotkvm.com/product/tinypilot-pro
- mbreese 5y agoAnother classic way to monetize open source is via support contracts. Enterprise love support contracts where someone has to answer the phone. This doesn’t help the “no on call” criterion, but is a good way to increase revenue. Or sponsorships… this project is sponsored by X. But that’s probably not a good fit for a hardware/software combination.