In our company, I manage the security team, which consists of eight people. Since we have a flat organization where everyone is involved in various tasks, all eight team members are using Reblaze. So currently, nine people are using Reblaze in our company.

I witnessed the level of protection they provide, especially during a digital attack that spanned across entire continents and was directed at us. It became evident just how intelligently the product is engineered. It effectively scaled to shield our platform while still allowing legitimate traffic to reach our servers. From that perspective, the scalability of the product is truly exceptional.

In the first year, the scalability was very low. We were one of the first customers that they created front-end load balancers for. The initial solution was a static DNS solution. Only after a year did they provide front-end load balancer servers to spread the load in a much smarter way. Now, it's fully scalable.

The end-users were all the school-age students in Israel, about 2 million students. We had 1.2 million distinct users a month. There was no problem with scalability in that aspect.

We haven't had any problem with the scalability and the performance is okay.

Currently, all of our websites are under the protection of the system and, as we roll out new systems, every new site or application will be automatically installed under the protection of the system.

We have never run into a scalability issue at all with them. We are in the horse racing business, so we have five really busy times of the year which you can think of as similar to Black Friday levels of traffic. They have supported us through record growth.

We do have plans for increasing usage. We are rolling out a new application stack, and we are going to insert Reblaze in front of that. We have it in front of five of our six existing platforms.

I haven't had a need for massive scalability but whenever I needed to scale up a notch, it was not an issue.

It seems the implementation of Reblaze is company-wide. It's not users who use it protecting our activities. It's protecting our cloud solutions. I'm the user of the system but we are protecting our implementations with it. We have a lot of clients connecting through our implementation where Reblaze is in the front.

It's scalable.

We plan to increase use of Reblaze. we need Reblaze to take part in defending the new environments that we are uploading .

There is also no problem with the scalability.

We have three people using the solution and they handle deployment and maintenance of it. We use it every day but we don't currently have plans to increase usage.

Scalability is good. 

The security team uses this product. Only they have access to this solution because it's a security product. 

There are no issues with scalability. The solution is on public cloud so it does auto-scaling.