What I like about the solution is that it is designed strictly as a consistent file system, which means in every situation, it guarantees that the data that is stored is not corrupt or is not invalidated. It seems to have a lot of performance, but when you're doing backup, you can't allow some gaps in your architecture design. This is one of the most critical things that it works strictly as a consistent file system. If data is written, it is written, and you will get it back, and it is guaranteed that you will get back the data in the same way you stored it in the system, so if the system says I have it, I have got it, then it is stored, and it is not corrupted. This is one thing in the backend which most customers think every vendor is offering. It is really safe, and its immutability is another thing. What comes on top is its multitenancy, the ability to set up Chrome accounts so that it is not possible for one administrator to delete the data, so you need at least two or three people to agree that a particular data should be removed. It should be set free, so it can be overwritten, something like this.

It has snapshot capabilities. We take advantage of those.