CareProxy detects sensitive content, enforces your policy and writes a signed proof of every AI call. The engine sits on top of what you already run, and enforces where AI use happens: in the browser, on the gateway or in the API.
CareProxy is in operation as the control and evidence layer on top of the AI tools you already use. And the engine is built to grow: consent-aware steering and output monitoring are shaped together with the first customers.
Ready now · Validated with partners
CareProxy
For clinics, municipalities and organizations using cloud AI
One engine with three jobs: detect sensitive content, enforce your policy, and prove what happened. Sensitive parts are masked before they leave the building, so staff still get their answer, and what must never leave is blocked. Every call is written to the signed audit log.
Real-time detection of patient IDs, clinical and confidential data
Mask and pass on, instead of only blocking
Enforcement where AI use happens: browser, gateway or API
Signed, hash-chained audit log, verifiable by a third party
No local AI infrastructure required, runs on top of what you have
Roadmap · Direction
Next on the engine
For organizations with their own local models and strict consent requirements
The engine is built for more than masking. The direction is consent-aware steering, where requests under special legal bases can be kept on your own local models instead of the cloud, and output monitoring that catches errors on the way back to the user. It is shaped together with the first customers.
Consent-aware steering between cloud and local models
Output monitoring for quality and safety
Governance of AI agents' actions
Developed in collaboration with the first customers
Ready to take control of your AI infrastructure?
CareProxy is under active development. Join the waitlist to be notified as soon as pilot installations open.