The main missing component is security updates. Usually in this model there is no guarantee that the open-source "tip" is actually supported. Even if it wasn't

The main missing component is security updates. Usually in this model there is no guarantee that the open-source "tip" is actually supported. Even if it wasn't supported releasing security patches under an open-source license would allow community back porting. Of course security patches are a big driver for businesses so this makes sense from the profit sense. However as an open source project I would be very hesitant to add this as a dependency because now I am forcing my user to enter a contract if they want security. I think this is the problem with non-free licenses in general. It makes it a much harder decision for other projects to build upon. Because now any user is required to become a customer of another business with pricing and licenses that I have no control over and can change at any time.