A foundation model is retired
Your team swaps an upstream model on the lab's schedule, not yours. What changed for each hospital customer?
For health-tech vendors selling into hospitals
When your AI changes, what do you owe every hospital customer?
Bring one real change from your stack (a model swap, a prompt edit, a new subprocessor). In 15 minutes you’ll know exactly what a hospital customer can ask you to prove about it. And whether you could, today.
Book the free gap check 15 minutes · No prep · No sales deck
Runtime evidenceSOC 2 / HIPAA control mappedHuman-reviewed gap analysis
The trigger is already in your stack
Your AI can change even when your roadmap doesn’t.
A prompt or guardrail changes
Behavior changes without a new product release. Can you reconstruct the deployed policy and decision path?
A subprocessor or patch lands
A dependency or security fix changes the stack. Who needs notice, what evidence goes with it, and by when?
What happens in 15 minutes
Bring one change. Leave knowing what breaks.
Use a recent model swap, a planned release, or the next deprecation you know is coming. If you have contract language, redacted snippets are plenty. If you don’t, that itself is worth knowing.
- 01
Change
Name the model, prompt, policy, guardrail, subprocessor, or patch that moved.
- 02
Obligation
Check the notice window, approval path, evidence language, and delivery channel.
- 03
Evidence
Identify the runtime record and customer-ready proof you can actually produce.
- 04
Gap
Leave with the missing owner, artifact, or workflow—not another governance deck.
The proof layer
Start with what actually happened at runtime.
Gatekeeper is a proxy that sits in front of your AI calls. Every call gets logged with the policy that ran, the model and provider, timestamps, and what was redacted. In our 1,000-call production test, all 1,000 calls came back with a complete audit record: 4,407 entities redacted, about 0.44s of added latency. That record is what becomes customer-ready evidence, instead of a reconstruction after someone asks.
01
Traceable. Policy-version lineage and timestamped decisions.
02
Reviewable. Evidence mapped to relevant SOC 2 and HIPAA controls.
03
Honest. Ungoverned calls are flagged; detection is never described as perfect.
Real product output3 pages · synthetic data
If the check finds a real gap
Step 1 · Free
15-minute gap check
One change, one obligation, one honest answer on what you can prove today.
Step 2 · Fixed fee
Change-evidence audit
We go through your last 12 months of AI changes, match them against what your customer contracts require, and hand you the evidence baseline. Fixed scope, fixed price, quoted on the call.
Step 3 · Product
Runtime evidence, continuously
Where the gap is proof itself, Gatekeeper’s proxy writes the audit record on every AI call, so the next change shows up with its evidence already attached.
This is for you if
You sell an AI-enabled product into hospitals.
- A hospital security review is open or approaching.
- You have changed a model, prompt, guardrail, or AI vendor.
- You need to know what evidence you can defend today.
This is not
A formal compliance attestation or legal opinion.
I won’t claim your contracts already contain these duties, that Gatekeeper catches every instance of PII, or that a control mapping makes you certified. If a claim isn’t provable, it doesn’t go on this page.
Who you’ll talk to
Your 15 minutes goes to the founder, not a rep.
No SDRs, no deck, no follow-up sequence you didn’t ask for. Every check is run by Dilip Adityan — years of engineering at Broadcom, a Chicago Booth MBA, and too many health-tech deals watched stalling in hospital security reviews. That’s the experience your one change gets checked against.
Before you book
Is this a sales call?
No. It's a working session on one real change from your stack. If runtime evidence turns out to be your gap, that's what Gatekeeper makes, and you'll hear that plainly. If it isn't, you still leave knowing where the gap is.
Do I need to share contracts?
No. Your redacted clause text is ideal, but describing the obligation from memory works fine. The full agreement is never needed, and nothing you share is kept without your say-so.
We haven't signed anything about AI changes yet. Still useful?
That's most vendors right now, honestly, and it's the best time to look. Hospital-side playbooks (HSCC, Joint Commission) now tell health systems to ask for change-notification clauses, so we map you against what your next renewal or security review will probably ask.
What happens after the 15 minutes?
You leave with the gap named: the missing owner, artifact, or workflow. If you want it closed, there's a fixed-fee change-evidence audit. And where the gap is runtime proof itself, that's Gatekeeper's product.
One change. One contract. Fifteen minutes.
Find the gap before your hospital customer does.
Bring the last AI change you shipped, or the next one you know is coming.
Book the free gap check Or email dilip@shaachi.com