It is fair criticism. We don't claim to be "open source" rather we are open and free as in you can see the code and host it yourself if you want. The primary restriction is that license does not allow building a managed service out of it.
BTW, we don't have any license key, so that part of the Elastic License wouldn't apply. It is there, because we wanted to use a known license that fits the bill instead of creating our own obscure license.
Pretty terrible look, given you're lying already with this "We don't claim to be "open source" rather we are open and free as in you can see the code and host it yourself if you want. "
I replied this in another thread and didn't want to repeat myself here but that was probably oversight on my part.
> Truly sorry that we missed these instances of "open-source" references. We scrubbed the use of open-source in most places, but forgot about our home page, which might sound weird as the home page is... well... home page. The truth is that our web site is not our primary focus at the moment. Rather we are putting almost all our effort for building the product (You can watch all of it in GitHub)
It is fair criticism. We don't claim to be "open source" rather we are open and free as in you can see the code and host it yourself if you want. The primary restriction is that license does not allow building a managed service out of it.
BTW, we don't have any license key, so that part of the Elastic License wouldn't apply. It is there, because we wanted to use a known license that fits the bill instead of creating our own obscure license.