Customers
Guardrail is early, and we would rather show you our own numbers than a wall of logos we have not earned. Everything below is labelled with where it came from.
While building the agent-framework support we ran an agent with a deliberately broken tool loop against a $2 session cap. Guardrail blocked the next call the moment the cap was reached: the request was never sent upstream, so it cost nothing, and the agent received an ordinary rate-limit error it already knew how to handle.
Running our own Claude Code sessions through Guardrail made the cache-write tax visible: the opening turn of a long session writes the cache and can cost several times a subsequent turn that only reads it. The hidden-cost view breaks that out per request, which is what turned it from a surprise into a number we plan around.
If Guardrail has stopped a runaway session, changed how your team budgets for agents, or shown you a cost you did not know you were paying, tell us and we will publish it here with your words and your numbers, or anonymously if you prefer.
admin@neatproxy.comThe Free plan enforces budgets locally, with no account.