Frequently asked
questions.

KADE is an intelligence infrastructure layer for capital markets. It connects permitted institutional data, analytical reads and existing workflows, retaining the evidence beneath each result.

The institution retains its systems of record and its decisions.

KADE sits above the existing stack. Market data, portfolio systems, risk models, research and internal records supply permitted inputs through governed interfaces. Those systems remain authoritative.

Where KADE fits ↗

Explore the architecture ↗

An individual Lens addresses a specific question. The eight lenses cover Portfolio, Momentum, Trend, Volatility, Risk, Opportunity, Liquidity and Correlation.

TELESCOPE is optional synthesis across several reads. It preserves the underlying evidence, including agreement, conflict and confidence. An institution can use a single Lens without choosing synthesis.

Explore the eight lenses ↗

Lens configuration defines the context for each read. Relevant settings include classification schemes, measurement windows, horizons, limits and thresholds. The configuration depends on the question being assessed and the institution’s mandate.

Configuration and version remain with the analytical record.

No. Complementarity describes how KADE is intended to fit into an institution’s architecture. Institutions can also consider an internal build, specialist analytical tools and capabilities within broader financial platforms.

The comparison is the institutional question being addressed, the evidence retained with a read and the deployment boundary. Existing providers can span several categories.

Explore where KADE fits ↗

Start with where each system runs, whose data it reads and the role it keeps. Market and reference data, risk and factor models, portfolio and order systems, and research and analytics can supply permitted inputs to the intelligence layer.

These categories describe roles. They are not a ranking of providers’ capabilities. Data access, interfaces, licences and processing locations must be agreed for each deployment.

Compare the roles and boundaries ↗

The analytical record retains the read, its contributing factors, configuration and ruleset version. The Governance example also identifies the retained run timestamp.

The public example is illustrative. Its numeric settings and runtime identifiers are unspecified.

Inspect an example read ↗

Yes. Each Lens resolves a different question, so supportive reads can coexist with constraints. Optional synthesis retains that disagreement.

In the illustrative Governance example, five supportive reads sit alongside constraints from Volatility, Correlation and Liquidity. The combined result is REDUCE. It is an explanation of the analytical process, with no live instrument or recommendation.

The institution. KADE returns intelligence and retained evidence into the selected workflow. The institutional team reviews the result and determines the action.

The website’s illustrative synthesis does not specify a trade or an institutional action.

Policy Lenses are optional overlays that condition reads against an institutional rule set. The specified examples include Shariah, mandate drift, ESG, concentration and exposure, evidenced disbursement, regulatory suitability and bespoke client screens.

Policy Intelligence is planned for Phase 3. The website preview explains the rule boundary; it does not calculate a screening result.

Hosted

Analytical processing runs in a KADE-controlled environment. Permitted inputs, transfers and service dependencies follow the contracted configuration.

Hybrid sovereign

Selected data and processing remain within the institution. The contract defines the remaining stages and permitted cross-boundary flows.

Fully sovereign

Every analytical stage executes locally within the institution’s controlled environment. Approved signed updates are pulled or imported and verified locally.

Sovereign runtime certification is pending. A certified sovereign runtime is not yet in production.

Inspect the deployment boundaries ↗

That depends on the technical profile and contracted configuration. Hosted and hybrid deployments define which inputs, processing stages and results may cross the institutional boundary.

The fully sovereign specification keeps analytical execution local, without a query-time external model round trip. No analytical payload leaves the certified boundary; non-content telemetry is permitted only where institutional policy allows. Certification remains pending.

Enterprise is a direct institutional engagement. White Label delivers the intelligence layer under a partner’s brand.

These are commercial arrangements. Branding and distribution do not determine where analytical processing runs. The technical profile, data residency, processing and access boundaries are set separately in the deployment contract.

Results can return through APIs and SDKs, existing applications and white-label products, or the customer platform and chat. Embedding places intelligence inside an existing application or workflow through governed interfaces.

The delivery surface and technical boundary are selected for the institution’s requirements.

KADE Technologies LLC is incorporated in Qatar and built to operate globally.

About KADE ↗

Board and executive team ↗

Core and lens suite

Running in staging.

Sovereign runtime

Certification pending. A certified sovereign runtime is not yet in production.

Policy Intelligence

Planned for Phase 3.

A pilot is a scoped evaluation with agreed outcomes and success criteria. Its processing and data boundary are specified with the institution.

The evaluation scope can identify the institutional question, permitted sources, selected reads and intended workflow. Those choices provide the basis for agreeing what the pilot should demonstrate.

Institutional deployment, partnership and investor enquiries can be submitted through the institutional enquiry form, or sent directly to info@kadetechnologies.com.

An initial enquiry can outline the intended use, existing workflow and deployment requirements.