The questions your compliance officer will ask, answered before they ask.
Consolidating ten vendors into one platform concentrates risk as well as capability. That deserves a direct answer rather than a badge wall. Here is where your data lives, what the platform does with it, and what we can prove.
Where your data lives
Alberto runs against your warehouse inside your own cloud boundary. Your claims, clinical, pharmacy and member data are not copied to us and are not pooled with any other organization’s. Access is role-based, sessions are authenticated, and administrative actions are logged. Sensitive fields can be masked for demonstration and training use without changing the analysis.
The AI, precisely
Alberto runs on Claude, by Anthropic — chosen for truthfulness and the highest quality of reasoning available — under a commercial enterprise agreement with a business associate agreement in place. Your data is not used to train models.
The model reads the question and writes the explanation. It does not produce the numbers: figures come from queries executed against your database and returned deterministically, on definitions fixed by the taxonomy. The same question on the same data returns the same answer. On the voice line, the model handles the conversation and never states a fact.
Where a figure is an estimate or rests on an assumption, the platform labels it — and an assumption is never allowed to produce a compliance verdict.
Auditability
Every regulated output cites the published specification it implements and the edition of that specification. Every compliance artifact ships with member-level or claim-level evidence and a tier of integrity checks that print their own results. Definitions are versioned, and drift is reported when a new edition lands.
The practical test: hand the artifact to an auditor with no access to us, and they can tell what rule produced the number and reproduce it from your own data.
The boundary we keep
Alberto recommends; it does not approve, adjudicate or attest. It does not determine medical necessity. It does not submit encounter data on your behalf — your submitter does, on your instruction. It does not replace your certifying auditor or actuary. Those boundaries are written into the product, not just the contract.
Continuity
Your data, its history and every output the platform has produced live inside your boundary and are yours already. Definitions are versioned and every artifact self-tests, so the platform’s state is legible to someone who isn’t us. If the relationship ends, nothing has to be extracted, converted or returned.
Availability & operations
Production runs behind a managed edge with a web application firewall, end-to-end encryption in transit, and secrets held in a managed vault. Data refresh runs on a controlled cycle with integrity checks at every stage and a documented restore path.
Certifications, honestly
Alberto carries no certification of its own, because it holds no copy of your data to certify. A single-tenant deployment inside your cloud boundary inherits your security perimeter, your controls and your audit scope — the same ones your existing attestations already cover. We answer your security questionnaire in full, support your auditor with whatever they ask, and put the architecture in writing under NDA. A badge on a website is not what protects a member record. The boundary is.
The architecture in writing, under NDA. Your questionnaire answered in full.