As ive said in many other comments - YOU DO NOT NEED PRO. The devs are very adamant about this - even aggressively so. 99% of apps will work just fine with the free library. Pro is for some bells and whistles, or just to support people who have invested many thousands of hours into making a genuinely innovative framework, and given it away
OK, then this approach will needlessly discourage adoption AND consume way more resources than it brings in. Under this structure the team needs to deliver the highest level of quality to the smallest paying audience without community support. Further, enterprise is very hesitant to pay for this as a product but are way more receptive to paying for support. Everyone would be much better served without a tiered free/pay product and paid support options.
>> or just to support people who have invested many thousands of hours into making a genuinely innovative framework, and given it away
I've never seen a corporation do this even with projects that don't try and encourage like here.
If an enterprise won't want to pay for the product, what makes you think they're more likely pay for support?
If you're implying they'll only pay when they've seen the value of the product, then the non-pro part of the framework is incredibly feature-rich and can easily do that.
Yeah support model for a lit of projects like this doesn't work. Even companies like the one behind NATS struggle. It's almost contingent on you building a bad product that needs support.
This is irrelevant to my comment. You claimed they're not hiding pricing and I'm simply saying it was a little hard to find ¯\_(ツ)_/¯