We plan to stay in business in the long run, but if things do go wrong and we shut down, we do intend to open source the app.
On a more serious note: I see no issue with software being a service and costing money if it's built on a standard that leaves the data in the owners hands and in the owners own structures. I.e. Markdown files synced using infrastructure like OneDrive/Dropbox/whatever with some nice features on top of it and a nice UI can cost whatever and no one should complain. Because if that software goes away the data is in the owners hands and in a standardized format supported by many other tools.
That should be the preferred way we build software btw. And to take it to the next level we should create more general purpose (and standardized) database tools that are user friendly, treat them in similar fashion as files by syncing with user owned Infrastructure and we might just get to the point where more rigid data structures can be used in a similar manner as what I described above for files. That future would be great.
Come to think of it, IDEs are exactly that: a powerful front-end for your code files. That means us programmers are not locked into any one IDE.
> And to take it to the next level we should create more general purpose (and standardized) database tools that are user friendly
Yep, but I wonder how we can get there. Hope someone figures it out! It's always hard to set standards.