Company
NeatProxy builds Guardrail.
NeatProxy is the company; Guardrail is its first product. We build controls for the money AI agents spend on your behalf — starting with the coding agents developers already run every day.
Why the company exists
Coding agents changed what a single developer can spend in an afternoon. An agent runs unattended, retries when it fails, and reads far more context than a person would — and the bill for all of it shows up weeks later, aggregated into one line on a provider invoice with no idea which project or session caused it.
Every tool we found either watched that number go up or shipped the traffic to a cloud to analyse afterwards. Nothing stopped it. The uncomfortable part is that stopping it is not hard — it just has to happen in the request path, on the machine, before the call goes out. That is the whole idea behind Guardrail.
Principles
What we will not trade away.
Local first, not local marketing
The proxy runs on your machine and the database is a file you own. Cloud sync is opt-in, and turning it off is one command. This is an architecture, not a setting we can quietly change later.
Metadata only, enforced in tests
Guardrail records model, token counts, cost, timings and status. Prompts, responses, code and credentials are never written to its logs or database, and disk-scan tests fail the build if they ever are.
Block, do not merely alert
An alert that fires after the spend is a receipt. Policies are evaluated before each request, so an over-budget call is never sent and never billed.
Say estimate when it is an estimate
Costs are computed from a price table and labelled with a confidence level. They are a close guide, not your invoice, and the product says so wherever it shows a number.
Never break the tool in front of the developer
An expired plan drops you to Free rather than bricking the daemon. A blocked call returns a clean provider-shaped error your tool already understands, not a crash.
Privacy
Your prompts are not our business model.
We sell a hosted dashboard and team controls. We do not sell, train on, or otherwise want your prompts and code, which is why the product is built so that they never leave your machine in the first place — even when cloud sync is switched on, what syncs is metadata.
The full model, field by field, is written up in the privacy documentation, and the security posture is in the security overview.
Contact
Talk to us.
Product questions, security reports, billing, or a story about what Guardrail caught — all of it reaches us at the same address, and a person reads it.
admin@neatproxy.com