It took one main engineer from ShieldX. And we used the UK reseller, a company called Cloud Digital.

Cloud Digital was really good. We put any issues or any questions to Cloud Digital and they resolved them with ShieldX for us. It was fairly easy. The original proof of concept and testing that we did were very impressive. We staged up little virtual machines within our environment which attempted to hack or flood the servers. We could actually watch as ShieldX picked up the attack and within less than a second blocked the attack. We simulated a DDoS attack and ShieldX blocked it almost instantly. There were very various things they did to prove how well the product works.

The most recent issue that we had had to contact Could Digital for had to do with an upgrade in the environment. That one came in the other way. It was ShieldX that contacted us because they needed to update ShieldX. Other than that — and I'm looking at the dashboard now — it's been fine. I'm looking at the throughput and various events that have been touching the website and I can't fault it.

We did the implementation with the ShieldX team. I was the only staff required for the deployment.

For the implementation strategy, we needed to figure first what talks to what. We started with the most important servers, then continue on to the rest, one or two servers at a time.

We partnered directly with ShieldX. Our experience with them was very positive. They have a fantastic engineering team. Again, we were customer number-one, so we were directly interfacing with the people who are writing the code and developing the product. That might not be normal.

We worked with ShieldX, who is very engaged with their customers. We had good responses and spent quite a lot of time with them.