So true. I have no problem with using and paying for a hosted, "cloud" version of the product if a self-hosting option is available. It reassures me that I can rely on this product, while not being vendor-locked.
I've certainly seen many different licenses used in COSS projects, including different mixes of them. E.g.: for my latest project I've decided to use mainly AGPL-3.0 (a pretty strong copyleft license) with specific parts licensed under MIT.
That said, my goal wasn't to limit the usage, but to be open-source, and provide self-hosting option (the 2 fundamental advantages you can provide to your users by being open-source, IMHO), while making sure nobody just runs the product on their servers, rebrands it, and sells it to others as a service (which, while possible with other licenses, is simply unethical in my book).
I've certainly seen many different licenses used in COSS projects, including different mixes of them. E.g.: for my latest project I've decided to use mainly AGPL-3.0 (a pretty strong copyleft license) with specific parts licensed under MIT.
That said, my goal wasn't to limit the usage, but to be open-source, and provide self-hosting option (the 2 fundamental advantages you can provide to your users by being open-source, IMHO), while making sure nobody just runs the product on their servers, rebrands it, and sells it to others as a service (which, while possible with other licenses, is simply unethical in my book).