KADE / Customer Platform Portal preview

Your operating
environment
for KADE.

Synthesis core in staging · Customer Platform in portal preview · Sovereign runtime certification pending.

One governed client area to administer your KADE estate, connect your systems and put intelligence to work.

Approved customers manage products and access, configure applications and environments, test integrations in the sandbox, monitor usage and get support, with every team working within the same customer context.

Request customer access ↗︎

Illustrative platform preview. The tool walkthroughs do not connect to a live sandbox. Portal approval does not issue API credentials or grant production access.

Register for the restricted customer portal. Access to published documentation and developer tools follows KADE approval.

Customer context / Portal preview
Select a layer to move inside
Connected view

One connected customer context

Access. Application. Connection.

Start with who can act, follow where the application runs, then inspect how it connects. The customer’s permissions accompany each step.

Choose a layer above, then select a control to explore it.

Illustrative architecture. No live customer data or API connection.

CUSTOMER ESTATE / CONTEXT LAYERS
ORGANISATION01
IdentityRolesEntitlement
APPLICATION02
ProductsEnvironmentConfiguration
INTERFACES03
APIs / SDKsEventsEvidence
ESTATE / OVERVIEW

Inspect a layer to see how customer identity, application configuration and technical access remain connected.

Choose a layer to inspect

Tap a plane or use the controls. Escape returns to the connected view.

ILLUSTRATIVE ARCHITECTURE · NO LIVE CUSTOMER DATA

Architecture / Interactive inspection

Separate the layers.
Keep the connections.

Explore the controls behind the customer estate. Select a layer to move inside the architecture and inspect its role.

SELECT A LAYER · SEPARATE OR REASSEMBLE · ILLUSTRATIVE ARCHITECTURE

Connected customer context

Five layers. One governed estate.

Identity, entitlement, application, environment and interface work together. Separating the diagram reveals their responsibilities without removing the relationships between them.

  • Start with the organisation and its users.
  • Follow access through products and applications.
  • Inspect how environments govern integration.

01 / One client area

The controls around
the intelligence.

The Customer Platform brings administration, integration and operation together. Your existing systems remain authoritative; your organisation controls how KADE is used.

01

Operate

See applications, environments, integrations, service health and usage across your KADE estate.

02

Govern

Manage users, roles, entitlements, intelligence access and the evidence behind important changes.

03

Build

Discover APIs, use SDKs, test requests and connect KADE to the systems your teams already use.

04

Extend

Enable additional products and configure approved customer-branded and embedded delivery.

02 / From access to operation

One workflow.
Context retained.

Follow an illustrative integration through the Customer Platform. Select a stage to see the task, the controls and the evidence that accompanies it.

03 / Workspaces

A shared platform.
A view for every team.

Twelve workspace families organise the customer experience in this portal preview. Access reflects each person’s role, licensed capabilities and operating context.

01Executive & Management

See adoption, intelligence usage, operational health and the commercial position across your KADE applications.

02Operations

Monitor integrations, deployments, jobs and incidents across your customer estate.

03AI Administration

Manage knowledge, evaluation, consumption and the permitted use of intelligence capabilities.

04Organisation, IT & Security

Administer users, roles, identity settings, credentials and access reviews.

05Commercial

Review products, arrangements, usage, allowances and billing in your account context.

06Developer Centre

Discover interfaces, configure environments, test workflows and inspect delivery evidence.

07Solution Architecture

Understand how applications, integrations and data boundaries connect within your solution.

08Product Management

Manage capability availability, configuration and rollout across applications.

09Customer Success

Coordinate onboarding, adoption and the activities that support your organisation’s use of KADE.

10Compliance

Review policy, access and operational evidence within your permission boundaries.

11Support

Raise cases, track service requests and follow issues through to resolution.

12Institutional Control

Review sovereignty context, data boundaries and customer-side institutional controls.

04 / Developer Centre

Build KADE into
your own systems.

The Developer Centre lives inside the Customer Platform. Interfaces, credentials and environments inherit the same customer context as the rest of your estate. Production credentials follow separate approval.

Find a contract, understand its requirements, test a workflow and inspect what happened. Documentation and integration guidance accompany the interface throughout its lifecycle.

DiscoverUnderstandTestConnectObserve

Access follows governance.

Customer, application, environment, role and entitlement determine what an integration can use. Commercial access does not override validation, data rights or production eligibility.

API Catalogue

Discover authorised interfaces, versions, schemas, authentication requirements and request examples.

SDK Centre

Access supported packages, version guidance and examples for your integration.

Playground Portal preview

Explore requests and validate workflows in the appropriate non-production environment.

Credentials & environments Portal preview

Manage authorised technical access across development, sandbox, pilot and production contexts.

Events & webhooks

Configure event-driven connections and review delivery history.

Logs & usage Portal preview

Investigate requests and service consumption within your permitted visibility.

Integration guides

Follow task-led guidance for institutional connections and embedded workflows.

Developer support

Use contextual guidance and escalate issues with the relevant integration evidence.

Customer applicationAPI / SDKAccess contextROLE · ENVIRONMENTENTITLEMENTKADE capabilityGOVERNED INTERFACERESULT + REASONING + VERSIONEVENTS / LOGS
Follow the request. Retain the context behind the response.ILLUSTRATIVE INTEGRATION FLOW

05 / White-label & embedded delivery

Your experience.
Connected to KADE.

Portal preview The White-label Studio configures approved branding and delivery settings within the Developer Centre. Products, users and entitlements remain governed through the Customer Platform.

Governed capabilityCUSTOMER CONTEXTKADE experienceUSERS + CAPABILITIESCustomer-brandedWHITE-LABEL STUDIOInstitution-ownedEMBEDDED / SYSTEM-TO-SYSTEM
The delivery surface changes. Governance accompanies every route.DELIVERY ARCHITECTURE

Use KADE’s experience

Administer users and capabilities within a KADE-provided experience.

Deliver under your brand

Configure an authorised customer-branded proposition, with controlled presentation choices and application identity.

Embed in your estate

Bring intelligence into institution-owned applications, existing workflows or system-to-system integrations through APIs, SDKs and events.

Studio controls presentation and delivery configuration. It does not change the underlying intelligence methodology or remove approval and entitlement requirements.

06 / Help, assurance & control

Help in the context
of your estate.

User guides, technical documentation and contextual help are available where your teams work. Roadmap KADE-specific AI assistance draws on controlled knowledge and the customer’s permitted context.

Roadmap When an issue needs human follow-through, approved customers raise a support case and track its progress inside the client area.

Assistance is not authority.

Help explains and guides. Actions that change customer state remain subject to identity, permission, approval and audit controls.

Governed at every step.

01020304IDENTITYPERMISSIONAPPROVALEVIDENCECUSTOMER ACTION / GOVERNED PATH
  • IDENTITYUsers and roles operate within your organisation’s access boundaries.
  • ENVIRONMENTSDevelopment, sandbox, pilot and production remain distinct operating contexts.
  • ENTITLEMENTProducts and capabilities follow licensed access and governed activation.
  • EVIDENCEImportant actions and configuration changes retain an auditable record.
  • INSTITUTIONAL CONTROLData boundaries and sovereignty context remain visible within the customer’s permitted scope.

Customer portal / Registration & approval

Your next step.
Your customer workspace.

Request access to KADE’s restricted customer portal for published API references, integration documentation and developer tools.

01 Register your organisation and use case.

02 KADE reviews your access request.

03 Sign in to your approved customer workspace.

Request access ↗︎

Portal approval does not issue API credentials or grant production access.

Developer enquiries

Your next build.
Starts here.

Every collaboration starts
with a conversation.Select your enquiry. Shape your brief.

ConversationChoose a route
Enquiry topic
A starting point

Ask us about the platform, customer access or the support you need.

Your enquiryDraft

Your brief.

General enquiry
Your enquiry

We use these details to respond to your enquiry. Read our privacy notice. Please do not include passwords, API keys, customer data or other confidential records.

A conversation starts here.

Or contact info@kadetechnologies.com directly.

KADE Technologies · Intelligence InfrastructureBack to top ↑
Customer context / inspect

ILLUSTRATIVE CAPABILITIES · NO CUSTOMER DATA