Hi, Alan, we will be posting some more polished explanations of our various editions shortly. In the meantime, I want to make a brief observation about some of the other open source vendors you mention. Each of the companies above takes a different approach to licensing. SugarCRM, for example, has a community edition newly re-licensed under the GPL. However, their Professional and Enterprise editions are licensed purely under a proprietary license. OpenBravo uses a "badgeware" style license based on the MPL that requires a "powered by OpenBravo" logo and is thus not OSI-certified. Zimbra, recently purchased by Yahoo, now licenses its open source edition under the Yahoo Public License which is also not OSI-certified. And Zimbra also maintains functional differences between its open source edition and its commercial editions. (More information here: http://www.zimbra.com/products/product_editions.html). MySQL's enterprise edition includes administration and installation tools not provided to open source users. Even Alfresco--which might be the purest open source play amongst the companies you mention--reserves, as I understand it, some "secret sauce" that they only provide to commercial customers.
My point is that all of the commercial open source vendors--including us--continue experimenting with various business models, including licensing schemes to strike the correct balance of, openness, community support and participation, and a viable economic engine.
Thanks,
Michael Harvey
EVP, Concursive
Hi Michael.
CentricCRM/Concursive has not been very forthcoming, i would actually say bordering on deceitful, with the separation between community and enterprise version features. The entire community was led into believing the features listed in the roadmap were going to be available in the community 5.0 version.
I thought the strategy was similar to Redhat where they release the source code and the business would rely on support revenue ,which was truly different than SugarCRMs offering and much more attractive. It would allow a small company to figure out how to use the system, and when it became valuable enough it could look for more of a "supported" system.
If this is an "open source" company, i suggest you work harder on your "openness" and clearly define the product editions. I would also suggest looking to SugarCRM for guidance on this. (http://www.sugarcrm.com/crm/products/editions.html).
Geoff