> "We are not turning Zulip into a proprietary product with an “open core” demo version" doesn't ring too true, given that a key component that must also be pre

> "We are not turning Zulip into a proprietary product with an “open core” demo version" doesn't ring too true, given that a key component that must also be pretty inexpensive to run is walled off No, it's pretty clear it doesn't change anything about uts open source status. No definition ever required that authors run the services for you.