KADE / In the existing stack
Where each system runs.
Whose data it reads.
Built to complement
the existing stack.
Market data, risk models, portfolio systems and research keep their roles. KADE connects their permitted inputs to analytical reads, retained evidence and the institution’s existing workflows.
One layer. Across the stack.
Conceptual architecture01 / Existing role
Market &
reference data
Market observations and reference information supply the data universe for analysis.
A configured analytical read in the context of the institution’s position and mandate, with its contributing evidence retained.
The source remains authoritative. Access follows the institution’s licences and permitted interfaces.
Every analytical stage executes locally, with no query-time external model round trip. The question, its context and the analytical payload remain inside the certified boundary. No certified sovereign runtime is in production today.
Roles, not rankings
Read across the stack.
Keep each system’s role.
Providers can span several categories. These are architectural roles, not a statement that a provider lacks adjacent capabilities.
| Existing category | Role it retains | Relationship to KADE |
|---|---|---|
| Market & reference data | Market observations and reference information. | Permitted inputs to a configured analytical read. |
| Risk & factor models | Specialist risk measures and factor outputs. | Inputs that can be read alongside the other lenses. |
| Portfolio & order systems | The institution’s book and operational workflow. | Portfolio context in; intelligence returned to the selected workflow. |
| Research & analytics | External research and proprietary analysis. | Permitted evidence considered in the analytical context. |
| Platforms with native intelligence | The institution's book of record, with analytical capability over the records it holds. | Permitted inputs to reads that span sources beyond a single platform's book. |
| KADE / Intelligence layer | Configured reads and optional synthesis across permitted inputs. | Read, factors, configuration and version retained beneath the result. |
Data access, licences, interfaces and processing locations are defined for each engagement. Hosted and hybrid profiles specify permitted transfers; the fully sovereign specification keeps analytical execution local. No certified sovereign runtime is in production today.
The investor question
Complementary architecture.
A clear basis for comparison.
Complementing the stack does not remove competitive alternatives. Institutions may compare KADE with an internal build, specialist analytical tools or capabilities within a broader financial platform.
The useful comparison is the question being resolved, the evidence retained, the deployment boundary and the fit with the institution’s workflow.
A platform's intelligence is bounded by the book it keeps. Reading across sources that sit outside that book is not an extension of the same product, which is why breadth of source is an architectural position rather than a feature.