In the rocket.chat community call on October 13th 202 1 CEO Gabriel assured, that they do not plan to move any other feature to EE. Sorry, but we can't guarantee to remain always that friendly as we did until now in the rocket.chat forum or issue tracker, especially if any other feature would leave the open core. We are still hesitating to sign as it includes clauses like that no negative remarks may be published during and five years after ending the sales partner agreement. We've been asked to join the rocket.chat partner program to resell pro and enterprise packages. The investors'ultimate goal usually is to sell the company in 4-7 years (that's when investors and founders become very rich). Their strategy seem to be to convert any deployment beyond a few hundred mobile users into a seat count package (see table above). Investors now want to see additional income streams. They decided to take the fast lane with venture capital and raised 13 Million USD in February 2021. We've met the founder Gabriel Engel in person in Munich and are in contact with several team members. They created a great messenger, and we commeneted issues and contributed code. We really honour the effort of the rocket.chat team. We will definetely follow and support Pierre's activities! Being part of the rocket.chat community That would allow to pre-populate rocket.chat with users who have not yet signed in without running an LDAP server. Another path suggested by our french friend Pierre is to extend Keycloak to talk directly with the rocket.chat API to sync groups. As some users in the forum fear, that more features might be locked out from the community version in future, a community maintained version would ensure that the current, already quite rich feature set will stay. The focus of the work would be security fixes, but also cherry picking bug fixes. We have been suggesting in the forum, that the community may be joining forces and continues to maintain that version for those who need it and can not afford to switch to the EE version. Many rocket.chat deployments won't care about loosing LDAP/OAuth/ SAML group sync support after March 2022, when LTS support ends for rocket.chat 3.18. BTW, at fairkom, our statutes force us to invest any surplus into open source or commons related activities, we don't serve any shareholders or investors. Often we offer our push gateway in combination with hosting, customization and support as our strength is consulting and integration. Prices are indicative, please contact sales for NGO or education discounts. Our pricing scheme is only counting push messages. Now we start offering those components to any rocket.chat hoster. This step was necessary to us to be able to afford running our own large community server. That way we can configure any rocket.chat instance to make use of our own HA push gateway with our own set of app keys. Using rocket.chat with fairchat push gateway and appĪt fairkom we have forked the rocket.chat app end of 2019 and publish a rebased version regularly as fairchat Android and fairchat iOS apps. recommendedÄisclaimer: Prices may vary or are subject to discounting schemes, see the published rocket.chat price list, price for EE has been estimated to $ 5 per seat (volume discounting may apply). Even if all versions support unlimited users, we assume here that every user receives 5-10 messages per day via the rocket.chat push gateway at their rocket.chat app, which in fact limits the number of recommended users that can be hosted per instance. Let's have a look at suitable packages for typical self hosted deployments. Using the rocket.chat push gateway and app After that date all administrators need to upgrade to a 4.x version and are faced with the announced restrictions. The rocket.chat community server edition version 3.18 will be supported until March 2022. After refactoring, it goes closed source. We had contributed code to exactly that feature as we needed it for a few customers. Most importantly, role and group mapping with identity management systems will no longer be available in the community version (see c omparison table). Rocket.chat's announcement to move some features into their enterprise edition in version 4.0 triggered a controversial discussion on their forum. We had developed a Qt based app, contributed code, gave a lot of feedback and helped to specify and test the team feature, which finally got available in the rocket.chat March 2021 release. At fairkom we deploy rocket.chat servers since 2016 for NGOs, public administration and enterprises and we run a large community server at.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |