I used Arcjet in a personal AI banking project for PII detection and setting token/usage limits. It was really easy to integrate, and I liked that I could add security controls directly into the application instead of building them from scratch. For an AI application handling sensitive financial data, it made it much easier to control what could reach the model and prevent excessive usage.

It’s very easy to use, with a generous free tier and an excellent dashboard that makes everything straightforward to manage.

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.