Platform / Deployment
Choose where the analytical workload runs, which inputs may cross a boundary and how access is governed.
Your data has an address. Some of it should only go as far as you allow. KADE works within the boundary you set. The boundary is yours.
01 / Placement options
One platform. Three ways to place the boundary.
The hosted model places analytical processing in a KADE-controlled environment. Permitted inputs and access are agreed by contract.
Processing is split across agreed environments. Residency, interfaces and access depend on the institution’s deployment contract and validation.
The analytical workload is designed to run inside the institution’s environment, subject to the agreed technical and control requirements.
Build state / October 2026Hosted deployment is a proposed placement model, subject to technical validation and agreement. Hybrid sovereign and fully sovereign deployment are specified and in development. No certified sovereign runtime is in production today.
02 / Data flows
Permitted flows depend on the agreed deployment design.
The institution and KADE agree the inputs, interfaces and access for the selected configuration.
03 / Comparison
The technical profile determines where the work happens. Availability and permitted transfers remain specific to each deployment.
| Profile | 01Hosted | 02Hybrid sovereign | 03Fully sovereign |
|---|---|---|---|
| Workload | KADE-controlled environment | Split across agreed environments | Institutional environment |
| Transfers | Permitted inputs, defined by contract | Only the flows agreed for the deployment | Determined by the validated deployment design |
| Availability | Requirements and validation to be agreed | Specified and in development | Specified and in development |
04 / Your requirements
Where intelligence runs, what data may move and who can access it are defined for each institutional deployment.
KADE works with your technical and governance teams to agree the operating environment, integration requirements and applicable controls. Availability, data residency and service commitments depend on the selected configuration and its validation.
Discuss your deployment requirements →Institutional enquiries
Discuss your institution’s workflows, integration or deployment requirements.
Your brief
