Valerian Saliou

In our initial model, users get load balanced to the server with the least active connections, such that the distribution of connections stays even over all of our WebSocket workers. But now, it's a whole new world.

We got to a point where we had the lightest chatbox on the market, with a compressed size of 232KB (full load), where other chatbox providers would often load up to a megabyte. Discover How!

On July 22th, Crisp experienced infrastructure issues caused hardware failures with our provider DigitalOcean. We wanted to be transparent about the technical cause of this incident.

As the chatbot trend continues, we receive a lot of questions from customers willing to connect very specific automated response systems to Crisp [https://crisp.chat/en/]. For instance, certain users want to connect Recast.AI [https://recast.ai] to Crisp, or even load custom responses from an internal knowledge base that's not hosted on Crisp. Crisp provides a chatbot software [https://crisp.chat/en/chatbot/] as part of the Crisp Unlimited plan. The Crisp Bot builder does the job for most autom

Since the last March 2018 update, the Crisp team has been hard at work shipping brand new features and improving existing features. We're proud to announce our Crisp Summer 2018 update. This article sums up what's new and what's improved. Also, we're telling you a bit more about what the Crisp team members did recently. New Features 1. Status Page As technical guys, we know that server uptime is key to delivering a great service to your customers. We know how hard it is to keep up with the in

The Crisp technical architecture runs around 40+ different micro-services, all replicated across different physical machines. Adding to that, we have around 20 daemons operating different tasks, eg. data storage with MongoDB, or email delivery with Postfix. Those microservices handle 1 billion+ requests each month (this is growing). We need to know when something crashes, quickly. After a thorough analysis of the status page / monitoring solutions available on the market, either as SaaS or Open

This article is a word-for-word repost of Announcing Bloom: A REST API Caching Middleware [https://journal.valeriansaliou.name/announcing-bloom-a-rest-api-caching-middleware/] from the blog of Valerian Saliou [https://valeriansaliou.name], Crisp CTO. -------------------------------------------------------------------------------- Premature optimization is the root of all evil. Especially when you launch a new SaaS business you're not sure will succeed and get the traction you would expect of

The Crisp team has been busy at work over the months of September and October to bring you new improvements to the Crisp Platform. Our focus has been mostly on the chatbox. Since we released our new chatbox in August 2016, we have had a lot of feedback from all our users on how to make each feature of it better. This article sums up all we've been at work on to improve the Crisp chatbox, in 10 points. What's New 1. We're online tooltip A huge number of Crisp users told us they didn't receive

Here at Crisp, we love technology. Especially when it is bleeding edge and may help improve the quality and speed of the service. Want to know more about Crisp Chat widget [https://crisp.chat/en/livechat/]? Make sure to go to https://crisp.chat/en/livechat/ Recently, we made a small optimization to the chatbox code using a recent CSS feature [http://www.w3.org/TR/css-fonts-3/#unicode-range-desc], which had a tremendous impact at scale: it reduced the total size of the chatbox on the network by

looking for tips on how to scale your startup at its early stages? This article is made for you.