True ownership of software requires the ability to tinker and repair via open or at least licensed source code. But source code almost never makes sense to release for commercial products that must grow to survive and requiring funding to do that.

In the little software business I have been working towards creating, my desire was to offer a educational product for aspiring programmers as a monthly subscription.

Then, once the subscription product is paying the bills and successful, create a single seat offline version of the software and sell that as a package with a book. The book would be a user's guide for the programming language with fun example programs to type in suitable for families and schools who don't have internet to connect to my site.

I have planned networking and sharing features for the online edition that the offline book edition wouldn't have, so there'd be an incentive to pay the subscription to get all that. Nevertheless, I feel an offline version should be made available with a perpetual license in case my company dies, taking the website and web-based programming environment with it and leaving people with nothing.

> True ownership of software requires the ability to tinker and repair via open or at least licensed source code

I think I'd settle for a well-documented plugin API? This used to be more or less the dominant model before everything moved to the cloud