I had a similar idea years ago and the name I came up with was "Eventually Open". It wasn't a case of abandoning code more gracefully per se, but simply that a

I had a similar idea years ago and the name I came up with was "Eventually Open". It wasn't a case of abandoning code more gracefully per se, but simply that after a set period of time, code would be relicensed as open, regardless of the state of the business. So you might have a timeline like: * Today: release version 1.0. * 6 months into the future: release version 2.0. * 12 months into the future: version 1.0 becomes GPL. * 18 months into the future: version 2.0 becomes GPL. * 24 months into the future: version 1.0 becomes MIT. * 30 months into the future: version 2.0 becomes MIT. And so on. The latest version would be proprietary but source-included, and previous versions get relicensed as soon as they age out. The other alternative is to have the same mechanism, but with a donations system to speed up the relicensing. If your codebase is worth 30k to you, then if people chip in 30k, it gets relicensed immediately. If people chip in 15k it gets relicensed earlier than it would normally. It's not a good alternative to open-source, but it's preferable to completely proprietary as it makes it possible for abandonware to be picked up and maintained by third parties, and it offers an alternative mechanism for funding development of code that will eventually be open.