What I like most about Arcjet is how easy it makes it to integrate security features into an application. The rate-limiting feature was especially useful because it let me protect my API from excessive requests by automatically rejecting repeated calls within a defined time window. It was simple to configure, and the documentation helped keep the implementation process smooth.
The main downside I ran into was during development. Because I was constantly testing and making frequent API calls, the rate limiting would often end up blocking my own requests. To make development easier, I had to raise the limit or temporarily disable rate limiting in my development environment. That said, it wasn’t a problem in production, where it worked exactly as intended and did a good job protecting my API from abuse. Review collected by and hosted on G2.com.
One thing I disliked was that the bot protection occasionally flagged some of my legitimate requests as bot traffic during development and testing. Since I was making many rapid requests while debugging, I sometimes had to adjust or temporarily disable the protection in my development environment. It would be helpful to have an easier way to distinguish trusted development traffic from actual bot activity. Review collected by and hosted on G2.com.
