UI is straightforward with decent rule options such as allow, redirect, or show blank page (after loading complete.) The last option is a nice soft block option as you can hide your store from folks and make it look more like a bug rather than making it obvious they're blocked. However, this has one fatal flaw which has been tested over the last month. Even with lightish traffic, say 1k sessions per day, you cannot use the main search log function to look for specific occurrences. It always consistently times out. If you want to see if someone who is blocked (say someone posting fraudulent orders frequently) and you have a rule in place to block them, you could see log entries that triggered the rule from the rule but only for the current day. Thus you have no way of looking back over a longer period of time for specific rule traffic or doing any general searches, even with current traffic. Having an unsearchable log makes this a not so good solution. Things worked great at first when we didn't have a large log stretching back months so probably this is just a database optimization/indexing and query issue. If this was fixed, by allowing rules to display hits going back further than 1 day, and by allowing paginated log searching over a date range that doesn't time out, then it would be a 5 star app. We'll probably look to evaluate alternatives since not being able to search logs is a critical failure.