Ask HN: More open than open source products

We are planning to start a business in the near future around a product (a data warehouse system) that we have been building over the years. Our product builds on an Apache-licensed open source project by replacing its core component with a proprietary engine.

I would like to ask HN about the licensing model that we are considering. Tentatively we call it as 'more open than open source products' because our product is not entirely open source, but practically it is more open than typical open source products.

A typical (commencial) open source product has by definition an open source repository, but its enterprise features are usually closed source. This implies that even if a user has purchased a license for the enterprise features, he/she still cannot rebuild the product after modifying/extending/fixing the code in the open source repository. In fact, there is no guarantee that the same open source repository is used in building the product.

In our case, we provide the binary distribution of the engine and everything else so that the user can rebuild the product, including all the enterprise features. For example, a user can modify/extend/fix the code in the open source repository and immediately rebuild his/her own version. If the user needs an extension to the proprietary engine (which we believe will rarely occur), we implement the extension at no charge. So, the user should trust a small core of the product (less than 5%) without access to the source code.

So, do you agree that this strategy deserves to be called 'more open than open source products'? Thanks!