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.

The model is substitutable by design. Lens definitions, composite construction and the retained analytical record do not change when the model does, and the fully sovereign specification executes without a query-time external model round trip.

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. A screen is an adjudication against an adopted methodology, with the ruling, its reasons and the ruleset version retained for audit.

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.

No certified sovereign runtime is in production today.

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. No certified sovereign runtime is in production today.

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 is based in Qatar and built to operate globally.

About KADE ↗︎

Board and executive team ↗︎

Synthesis core

Production-ready and running in staging.

Lens suite

Specified and mapped.

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.

Register through the Customer Platform access route. Requests are reviewed by KADE; registration does not automatically grant access. Approved resources depend on your account permissions.

Explore this topic ↗︎

The website provides the developer-facing journey and access-request routes. Integration with the KADE system is the next step towards completing the playground. Public walkthroughs do not provide production credentials or prove that a live analytical environment is available.

Explore this topic ↗︎

An authorised administrator invites other administrators or third-party guests by email. Invitees confirm before joining. The presenter chooses when to share a screen and can stop sharing. Guests can view the invited room only; the invitation does not provide admin access. KADE’s interface provides no recording or remote-control function.

Explore this topic ↗︎

Yes. You can decline optional KADE visitor analytics using Analytics preferences and still browse, send an enquiry or request access. Hosting, security and Cloudflare Web Analytics are described separately in the privacy notice.

Explore this topic ↗︎

No. Newsletter consent is a separate choice and you must confirm using the emailed link. You can unsubscribe later without affecting enquiry handling or approved portal access.

Explore this topic ↗︎

Use the Press & Media access route to request access. The team reviews requests, and restricted materials remain subject to authentication and the permissions provided.

Explore this topic ↗︎

News & Insights is the public home for articles and perspectives. Press & Media provides approved users with restricted resources for media use. Access to the resource library requires review and authentication; each resource remains subject to its stated permissions.

Explore this topic ↗︎

Use the account recovery link on the Press & Media sign-in page. Follow the emailed link, enter your new password twice and confirm the change using the separate confirmation email. A temporary password requires this setup before resource access. You can also change your password from your signed-in profile. If a link has expired, request another recovery email.

Explore this topic ↗︎

Articles display their author or contributor. A contributor profile may include a photograph, title and professional profile link. For a factual correction, email info@kadetechnologies.com with the article link and the detail to review. Articles provide information and perspectives, not investment advice.

Explore this topic ↗︎