Five questions. No email gate. Get a tailored recommendation before you talk to sales: which plan, which architecture, and whether you need a BAA on day one.
1. What kind of data will your model see at run time?
We are asking about the data the artifact processes during inference, not the seed data you used to train it.
2. Where will the artifact run?
.kolm artifacts are deterministic binaries. They run wherever you put them.
3. What about the seed data you will use to compile?
Compile is the one-time training step that bakes your task into the .kolm artifact.
4. Volume expected in year one?
A claim, a chart, a member message — whatever your unit of work is.
5. Who signs the BAA on your side?
Privacy officer, security officer, general counsel — whoever holds the pen.
recommended path
Your recommended starting path
This recommendation is a starting point, not legal advice. The executable BAA, privacy review, and SRA are still required before processing live PHI. Talk to your privacy officer.