If your customers/users own their copies of your software, then your rights to control what they do with that are enumerated in 17USC§106, and limited by eg. 17USC§117 or §109. Section 109 for example says that your customers can sell off their copy, but can't rent it out (unless they're a library). If you want to prevent your users from re-selling their copy when they're done with it, you have to assert that you have retained ownership of their copy of the software. (And, in cases like Confluence, they have to assert ownership of all copies that their users are authorized to make and redistribute.)
> If your customers/users own their copies of your software, then your rights to control what they do with that are enumerated in 17USC§106, and limited by eg. 17USC§117 or §109. Section 109 for example says that your customers can sell off their copy, but can't rent it out (unless they're a library).
That's an interesting analogy...
Is creating KSQL-as-a-service the equivalent of renting copies of the software? What would the "library exception" look like (which AIUI includes both private and public libraries)?
> If you want to prevent your users from re-selling their copy when they're done with it, you have to assert that you have retained ownership of their copy of the software.
Attempts to do that contradict the "first-sale" doctrine, but that doesn't stop folks from trying.
