Outcomer can be deployed as a container inside your own cloud environment, under your existing security, identity and governance controls — or run for you as a hosted service. Either way it reads the files, prepares the Case Orientation Report (COR), and every determination stays with your reviewer.
You choose where your data lives. In your environment, it never reaches us.
Installed the way any enterprise workload is: into your own cloud subscription, where your data already lives, under the controls you already operate. The model runs in your environment too, against your own model deployment. No case data is sent to Outcomer.
We run Outcomer for you in a US region, with nothing to install, and your data held separately from every other organization’s. Files travel encrypted and are encrypted at rest. Case records are used only to prepare the report, and are never used to train any model. Where they are held, how long they are kept and who can access them are set out in a written data agreement, which your team reviews before any case record is shared.
A versioned, signed feed of the requirements — the same corpus described on the governance page. Updated on a controlled schedule as requirements change. It contains no customer data: it is public regulatory material, prepared and versioned. You can inspect exactly what each version contains and when it applied.
The corpus is the only inbound dependency.
You supply your own policies. We bring the published requirements — already sourced from the issuing authority, versioned and signed off. The statutes, regulations and official guidance that govern the work, maintained as they change. A policy engine leaves that side to you.
Case files, personal data and evidence stay in your systems. The Case Orientation Report is written back into your estate, not sent anywhere. No case data is transmitted to Outcomer for processing, training or support. Your files are never used to train any model — not ours, and not your own deployment’s. Your reviewers’ determinations never leave your perimeter.
Nothing case-related crosses the boundary outbound.
The container runs under your identity and access management. Who can invoke it, and who can read the reports, is governed by your existing roles — not by an Outcomer account system.
It sits inside your own network, subject to your egress rules, your segmentation and your monitoring. The corpus channel is the only external path, and it is one you can inspect and restrict.
Every run happens under your logging and observability stack. What was prepared, when, and against which corpus version is recorded in your systems alongside everything else you audit.
Your region, your residency. Because the workload runs in your subscription, data residency is whatever your environment already enforces. There is no second jurisdiction to reason about — the data never moves.
Policies, access control, change management and incident response are documented and operating. The independent attestation is scoped and quoted, and we commission it as part of a customer deployment. A penetration test is completed before Outcomer is installed in your environment, and the results are shared with your security team. Technical documentation is available on request.
In your environment, support works from what you choose to share. Hosted, it works within the access set out in your data agreement.
The deployment model, the boundary, the corpus channel and, for hosted use, the data agreement are open to your security and procurement review before anything is installed or shared. We expect the questions, and the architecture is built to answer them.
Claims and complaints teams · Financial review teams · Quality assurance teams