Corporate messenger Time

About six months ago, I already told About our corporate messenger Time, which we quickly moved to when Slack refused to work with Russian companies. Over the past couple of years, the solution has passed the test of fire, water and copper pipes and showed that this messenger can be used to communicate with tens of thousands of employees. You can also build business processes and automation on top of it. (ala chat-ops). Some time ago, we started selling this solution to different customers first in the on-prem version, and over the past six months we have added SaaS option, as well as mvp for video conferencing. With so many changes, our colleagues decided to webinar product-wise (Atom and Jurent.)To talk about the pros and cons of the product, as well as share the experience of moving to Time and how they chose from the solutions available on the market.

In general, if the choice is relevant for you, then register for this webinar and do not hesitate to ask questions.

P.S. By the way, website It has been greatly updated and contains more useful information such as a basic description of the solution stack and integrations. Time is a cloud-native solution that we have deployed in our targeted runtime environments. (kubernetes clusters) TIme can be deployed in geo-distributed mode (We have, for example, it deployed to 2 geodistributed) Standard stacks are used under the hood: Postgres, Kafka, Redis, Open search / Elastic search

• There are different types of authorizations (SAML, AD/LDAP, openID) It is possible to migrate from other messengers (Slack, MM, RocketChat)

And there are also numbers for techies about one of our Time instances.

• 45 Thousands of users per day
• 2 million messages per day
• 80 thousand
• 5,4 Millions of conversations created by users
• 186 Thousands of channels created by these users more 1200 bots created by users thanks to convenient documentation
• 99,9% - SLA on availability

#Software