In particular, proprietary is not a sine qua non. Some enterprise companies open source a figleaf to assuage proprietary concerns, while others simply stay proprietary. If you're a product manager and want to use Aha, you just have to use Aha and go with their pricing tiers (including 30 day free trial) and claims of security. There's no open source Aha. That hasn't stopped them from being popular.
Funding and courting early adopters can go a long way towards neutralise 1 ($ and momentum imply a longer lifetime) and 3 ($ implies can hire other devs). Nothing ever removes the risk of a company cancelling a product, but that's the nature of products even from BigCos like Google and Microsoft. Even open source can be abandoned.
And if written in a script (or non-compiled language) probably something to keep your source safe and avoid abuse. Some random examples are sourceguardian (PHP) or proguard (JAVA) or enclosejs (Javascript)
I have to say, first glance, I like the idea of this tool a lot. I normally use light weight spreadsheets like gnumeric when I feel the need to use them at all, and I'd love a more expressive kind of spreadsheet/database/pivot table like this.
At the outset however, I'd be concerned about integrating a tool into my workflow that, most dangerously, is a service that could disappear and take my work with it. Second most dangerously, is proprietary. Third most dangerously, lacks a community beyond the initial dev. Fourth, if it is a service, is not a 'zero knowledge' service.
So while I like this look of this tool very much, and I'm going through the tutorials and playing around with it, personally I see this as a difficult sell. At least for me. But... I dunno, I don't think I'm the kind of demographic that moves markets.
You might see some kinds of success with this by emulating the gitlab model. open source the central components of it for personal use, and try to get some companies looking at it with enterprise-y features?