When you have a problem that you want to verify, what's important is the time that it takes you to actually find it. If it takes you more than few minutes, or it takes you an hour, or if you need to call their support to get answer, that can be problematic. If you can do it yourself, it means that it's easy. It saved us a couple of hours a week.

Before Reblaze, we worked with and used a number of products. We had one product for reverse proxy, one product for load-balancing, and another product as a web application firewall. We combined them all into one product, into the Reblaze platform. That helped reduce costs a lot. For example, we stopped using the F5 as a load balancer. We only had one F5, so by stopping use of it we ruled out the single-point-of-failure issue. And, of course, it saved us not only the direct cost of paying the vendor, but the cost of maintaining another environment as well, including eliminating backups, upgrades, etc. It saved us a lot of time and money. I worked for an educational institute so the pricing was different, but it saved us thousands of dollars a year.

The presentation of all the traffic, not just the blocked requests, helped our monitoring operations. Because we had very old platforms, the code was not written "by the book" and it was not, for example, HTTP-compliant. We wanted to roll out the solution very fast without false positives. Reblaze was a single, unified platform that helped us a lot in doing that.

We supported consumers and users at home and in schools, and when you work with end-users, the variety of their computers is amazing. Each one had a different browser, a different operating system. The combinations are infinite. Reblaze helped us to see the different combinations and it helped us to better understand which combinations we had a problem with. It helped us a lot to identify end-users' problems, whether it was a specific operating system or a specific combination of the operating system and browser version.

We didn't experience any major performance issues. The caching mechanism helped us a lot. It sent fewer requests to the front-end server and it cached all the static objects. It saved a lot of traffic into our network. It helped saved money by optimizing our server usage. We were able to use fewer resources on our side. It saved us about $15,000 to $20,000 a year in computing resources that we didn't need because we had the reverse proxy, the caching mechanism.

We used the platform as a CDN as well. We installed them outside our network so we could bring in only clean traffic, and only traffic for known static objects. It saved us a lot of traffic and we got only clean traffic. That meant we could use lower models of firewalls because the Reblaze WAF service blocked a lot of unnecessary traffic from coming into our network.

Reblaze has definitely saved us money. We have estimated that it saves up to €500,000 a year.

The response time to web-based attacks on things like credential stuffing is usually two minutes or less. So the response time is very good. For DDoS, they are able to scale and absorb fairly quickly. Usually, within three to five minutes, they have absorbed it and deflected it fully. I have tested this with unannounced tests.

The solution's presentation of all the traffic, not just the blocked requests, gives us a little deeper understanding of what the clients look like. It gives us fairly good fingerprinting on systems, what browsers they are using and the load geography. We have a pretty good indication of where everybody is coming from.

When we are troubleshooting an issue, sometimes they will have insight from the error messages that they receive from our infrastructure, in particular for the casino product. That message might say, "Hey, we are seeing that your systems are not handling the load. You may need to do this, this, or this." We have used them quite a bit to help troubleshoot the product.

I do not know how much, but it has definitely saved us on some infrastructure costs because, obviously, in any cloud environment you get charged for egress. Since they block out the malicious actors and unauthorized locations, that helps save us money. We do not have extended costs coming out of China, Russia, and other places.

When we had some unexplained behavior about our services, we approach the Reblaze team and they introduced us to the WAF. During installation we identified a malicious code or malicious IPs that affected our services. The moment they deployed WAF, it automatically differed from our main traffic and allow us to come back on track.

It gives me a worry-free environment; free of internet risk and cyber risk, so I'm free to do everything else.

It helps us find malicious actors using and abusing our application. We are on a blockchain. There are users and spammers and scammers, people who are trying to steal a lot of money. The app helps us to understand if that is happening and to block them.

The solution's presentation of all the traffic, not just the blocked requests, helps us in our monitoring operations. It's not only for security purposes. We can understand if we have something that is bad, a behavioral anomaly on our app. It helps us understand abusers. Not everything is related directly to security. There are things that you cannot do if you don't have this on your web app. For example, we can see if someone is copying our data. There are endless opportunities.

Reblaze has saved us money by optimizing server usage and blocking malicious bots.