Architecture / Fortress
The enterprise UCL deployment inside the customer boundary.
Fortress takes the UCL data plane into regulated enterprise operation: private connectors, local credential boundaries, governance dashboards, audit export, identity integration, and on-prem or private-cloud deployment.
Core layers
How Fortress is structured
01
Private connector runtime
Enterprise connectors read metadata and permitted source structure without exporting customer records to KynticAI Cloud.
02
Policy and provenance layer
Context facts are shaped with tenant, source, role, confidence, audit, and masking boundaries before consumption.
03
Operational control
Installer assets, lifecycle status, config delivery, dashboards, and support boundaries give enterprise teams a controllable runtime.
Operating flow
The request path through the product
Source
Systems stay where they are
SQL, CRM, ERP, SharePoint, email metadata, logs, and service systems remain under customer control.
Distil
Facts gain provenance
Context facts carry confidence, freshness, source lineage, and governance attributes instead of becoming anonymous prompt text.
Serve
AI gets context, not data sprawl
Approved consumers receive the relevant context package without broad movement of raw operational data.
Governance
Boundaries the architecture must respect
Identity
Access follows enterprise roles
Fortress patterns align context access with customer identity, role boundaries, and local administration.
Audit
Evidence is first-class
Governance dashboards and export paths focus on what was read, why it was used, and which policy boundary applied.
Sovereignty
Cloud is not the raw data plane
KynticAI Cloud can manage licences, support, updates, and aggregate posture while the customer data plane owns operational data.
Integration points
Where it connects to the wider stack
Scout
Open core
Scout proves the data-plane mechanics with source registration, selectors, snapshots, and APIs.
Fortress
Enterprise deployment
Fortress adds private connectors, vaults, identity, compliance export, and customer-controlled deployment.
Elite
Operating model
Elite connects outcomes, support, updates, and the proof loop around the data-plane deployment.
Evidence boundary
What this page proves, and what it does not claim yet
Built
Local code boundary
Scout, Cloud, and Fortress repos contain the current public/core, control-plane, and enterprise runtime surfaces.
Deferred
Heavy runtime proof
Production-scale vector, model, and P99 benchmark claims remain deferred until the larger workstation is ready.