When AI API gateways and proxies fits
- You are building AI-powered applications via API and need centralised rate limiting, cost allocation, and model routing.
- You need a full audit log of every API call with latency, token counts, and routing decisions for developer tooling.
- Your security team requires all model API traffic to flow through a single controlled egress point.
When Locke fits
- Your team uses browser-based AI chat tools that bypass any API gateway entirely.
- You want detection to happen before the data leaves the device. A gateway only intercepts calls after they leave the endpoint.
- You need an on-device control that works regardless of which model interface is open.
Side-by-side
| Dimension | Locke | AI gateways |
|---|---|---|
| Coverage of browser AI tools | Yes. Intercepts chat inputs on-device before submission. | None. Gateways only cover API calls explicitly routed through them. |
| Where inspection runs | On the device, before any network call. | On the gateway server, after data has left the endpoint. |
| Sensitive data visible to operator? | No. Masked content is never transmitted. | Yes. The gateway operator can read full prompt content. |
| Primary use case | Prevent specific sensitive data from reaching any model. | Centralise API access, costs, logging, and model routing. |
| Deployment model | Per-user, on-device Locke Early Access install. No traffic rerouting required. | Server-side proxy. All AI traffic must be explicitly routed through it. |
Bottom line
AI gateways are right for API-based AI in your product code. They don't cover the browser-based chat tools your team actually uses. Locke works on the device, just before any network call, with or without a gateway.
Related comparisons
- Locke vs Cloud-Based Data Loss Prevention
- Locke vs Enterprise Privacy Platforms
- Locke vs VPN and Zero Trust Network Access
