DataFabISO 27001:2022SOC 2 Type II
Utilities
Studio
Fabric
DataFab

The Enterprise That
Understands Itself.

DataFab turns the systems, data, knowledge and decisions already inside an organisation — continuously enriched by external intelligence — into a living, governed knowledge layer that discovers what the enterprise knows, lets humans and agents jointly operate against that knowledge, and compounds every validated insight, decision and outcome into a continuously richer understanding of the organisation and the world around it.

No mandatory data migration.No ontology programme before value.No permanent army of specialists.
ISO/IEC 27001:2022
Certified
SOC 2 Type II
Certified
Layer 3
Utilities · out of the box

Governed utilities

Ready-made agentic applications on top of the platform. The Financial Crime Unit is one of several — and you can build your own.

Financial CrimeDue DiligenceRemediationLegal CLMClaim HandlingGov Intelligence
built in the Studio
every execution enriches the Fabric
Layer 2
The builder

Knowledge & Agentic Studio

Where the enterprise composes, tests and publishes governed agents — in language, or with full control.

grounds
enriches · governed
Layer 1
The foundation

Knowledge Fabric

Discovers and resolves the systems you already run into one governed, cumulative knowledge state — read in place.

The architecture

Don’t rebuild the enterprise. Draw it.

DataFab discovers and resolves the systems you already run into a governed knowledge state, then gives your people and agents the tools to operate, refine and compound it.

DataFab · Platform Architecture

The Knowledge
Fabric.

The foundational data-integration and intelligence layer of DataFab. It discovers and resolves the systems you already run into one usable knowledge graph — the ontology is derived from your estate, read in place, and kept current by the fabric itself.

In place
Read, never copied
Derived
Ontology from your sources
Continuous
Kept current by the fabric
01 · Foundation

What the Knowledge Fabric is

A metadata-driven layer that gives unified access to distributed data assets — maintaining mappings and relationships rather than duplicating data.

It is an access enabler, not a repository — one source of truth, unified analytics, nothing moved.

Knowledge Graph

Graph-native storage with entity resolution

Entity Resolution

Cross-source matching and linking

Connectivity

Direct DB / API / MCP connectors

Data Flow

Read from and write back

Discovery

Automated identification and cataloging

Active Metadata

Continuous analysis and enrichment

External Sources

OSINT and external integration

Data Lineage

End-to-end tracking of data flow

MCP Creation

Model Context Protocol generation

Monitoring

Health, performance and security

02 · Architecture

Six governed layers

Each layer carries its own controls. The Semantic Layer is the Fabric’s primary output — the derived model everything above consumes. Requests flow down to the source; data is read in place and resolved on the way back up. Click a layer to open it.

01PresentationSearch UI · API Gateway · Platform Integration APIs
Search UIAPI GatewayPlatform Integration APIs
Controls · Authentication · rate limiting · input validation
02ServiceSearch · Lineage · Quality · Discovery · Governance
SearchLineageQualityDiscoveryGovernance
Controls · Service-to-service AuthN/AuthZ · mTLS
03Semantic LayerDerived Ontology · Entity / Relationship / Attribute Types · Source→Graph Mappings
Derived OntologyEntity TypesRelationship TypesAttributesSource→Graph Mappings
The Fabric’s primary output · schema-bounded · human-approved · versioned — the model every agent and utility reasons over
04Knowledge GraphEntity Store · Relationship Store · Query Engine
Entity StoreRelationship StoreQuery Engine
Controls · Encryption at rest · access-control lists
05ConnectivityDatabase · API · MCP · Event Streams
DatabaseAPIMCPEvent Streams
Controls · Credential vault · secure connections · sampling
06Source SystemsCustomer-managed data — read in place
DatabasesDocument StoresAPIsLegal SystemsExternal
Controls · Customer-managed · customer credentials
04 · Entity Resolution

A name match is never an identity

Records from every source are blocked, scored, clustered, reviewed and merged into one authoritative golden record — with a confidence score and full provenance.

CRM
John A. Smith
London · +44 7700…
0.91
Case management
J. Smith
Smith & Co · matter 4821
0.88
Corporate registry
Jonathan Smith
DOB 1979 · Dir. 3 cos
0.95
Match & cluster
Human review
◆ Golden record
Jonathan A. Smith
Confidence
0.94
Provenance · 3 sources merged
registry p.2 · CRM #7741 · matter 4821

The resolution pipeline

Stage 1
Blocking
Reduce the comparison space to candidate pairs
Stage 2
Matching
Deterministic + probabilistic scoring
Stage 3
Clustering
Group records at configurable thresholds
Stage 4
Human Review
Uncertain matches routed to a person
Stage 5
Golden Record
Merged, authoritative entity
Human-in-the-loopUncertain matches go to human review; every match decision and merge writes to the audit trail. Matching spans exact, fuzzy-name, phonetic (Soundex/Metaphone), address-standardization and ML-based methods.
05 · Data Flow

Resolve in place

Direct access without ETL or replication. The fabric reads from source systems and resolves on the way back — the records never leave, and there is no integration layer to engineer.

Knowledge Fabric
reads · resolves · never copies
Matter Mgmt
matters · clients
CRM
relationships
ERP / Billing
financials
Document Mgmt
files · metadata

Stored in the fabric

Mappings & derived insight
Entity-resolution mappingsA = A across systems
Cross-system relationshipsdiscovered edges
Investigation annotationstags · notes
Derived insightsagent conclusions
Temporal snapshotspoint-in-time

Remains in source

Authoritative records
Actual recordsnames · addresses
Document filescase files · evidence
Financial datasource systems
Communication logsnative systems
Operational dataall business data
Derive · the semantic layer

The ontology builds itself.

You don’t hand-build the model. It emerges from what the fabric has already extracted — source structures, data profiles and resolved entities become a governed domain model — the Semantic Layer, the Fabric’s primary output. A hand-built ontology is a specialist programme measured in months; a derived one forms in place and stays current.

The ontology, visualised — a schema of types, not instances
CONTROLSHOLDSPARTY_TOEVIDENCESRESIDES_ATINVOLVESATTRIBUTES · A-TYPESlegal_name · DOB · jurisdiction · risk_ratingPartyOrganisationAccountTransactionDocumentAddressMatterEntity typeRelationship type· · · Attributes (A-types)

An ontology is a graph of knowledge: entity types linked by relationship types, each carrying attributes. This is the derived model — the Persistent Knowledge Graph then fills it with your resolved records.

Step 1
Extract
Read source structures — tables, columns, keys and foreign-key relationships. Read-only; metadata and sampling only.
Step 2
Profile & classify
Data types, cardinality and distributions inferred; PII and sensitivity flagged in place.
Step 3
Resolve
Records matched and merged into golden records across every source.
Step 4
Derive
The domain model is inferred — entity, relationship and attribute types — a schema-bounded ontology, mapped source → graph.
Step 5
Govern & refine
Seed schemas bound it, a person reviews and approves, and active metadata keeps it current as sources change.
The old way · hand-built
A declared ontology
  • Authored up front by a specialist team
  • Months before the first unit of value
  • Every new source is a fresh modelling project
  • Goes stale the moment a system changes
DataFab · derived
A derived ontology
  • Emerges from the estate you already run
  • Value in weeks — no modelling programme
  • Schema-bounded — it never invents entities
  • Human-refined, then self-maintaining
Schema-bounded by designThe derivation is constrained by seed schemas — entity, relationship and attribute types — so the fabric can enrich and extend the model but never invent entities outside it. This Semantic Layer is exactly what the Studio’s agents and every utility reason over: one governed domain model — the Fabric’s primary output — drawn from your estate, not authored by hand.
Interconnection: this is the “Derive” step from the approach, shown in full — and the model the Persistent Knowledge Graph then makes durable.
Architecture & Deployment · the reference

The whole architecture, end to end.

Interactive — switch views along the top: the reference deployment, the reusable utility pattern, where it physically runs, recovery for loss and corruption, the chain of custody, who may act, and discovery to go-live. Click any component for its enforcement, trust and failure mode; click a red badge for the evidence that proves it.

DataFab · The Knowledge Fabric · Interactive architecture reference · Illustrative
DataFab · Agentic Studio

The Knowledge & Agentic Studio.

The build surface of DataFab — where the enterprise composes its own governed agents from its documents, in its own language, and on its own schemas. Every agent schema-bound, sandboxed, human-gated and audited.

You build
The agents, not a vendor
In words
Natural language, no code
Governed
By construction
01 · The builder

Where governed agents are built

Build, test and publish Data-Driven Agents, design workflows, define widgets and orchestrate multi-agent solutions — the complete builder experience.

You build the agents — on your schemas, in your language. The Studio does the wiring, the testing and the governance.

Domain Discovery

Extract schemas from your documents

Data-Driven Agents

Schema-bound processing units

Visual Pipeline Builder

Drag-and-drop, no code

AI Planning

Build a DDA from a description

Chain of Agents

Orchestrate with human gates

Graph of Agents

Non-linear graph orchestration

Widget Types

Visual interface components

Datasets

Structured, schema-bound data

Utilities

Reusable API + DDA components

MCP Integrations

Connect — and author — connectors

Unified Tool Catalog

Every tool, one searchable place

Template Library

Pre-built workflows

06 · Orchestration

Agencies, not agents

Compose multiple agents into a workflow — with human review gates wherever judgement belongs. Governed teams of agents, each with one job.

DDA · Intake
DDA · Resolve
Human reviewapproval gate
DDA · Assess
DDA · Issue
Execution pauses at the gate until a person approves — then continues. Every step signed, isolated and logged.

Sequential + gate

AB[review]CD

Branching

A splits → B · C · [review] → merge → E

Hierarchical

A → ( BD ) · ( CE )

Graph of AgentsPlanned

The next step extends the linear chain into a full directed graph — conditional branching, parallel fan-out / fan-in, cycles with exit conditions and dynamic routing, with a human gate available at any node.

Governed multi-agentDownstream agents can never exceed upstream permissions; inter-agent messages are signed with a TTL; and every human gate blocks until approved.
How much it runs itself

The level of automation is a dial.

The Studio does not force one mode. Each use case — and each step within it — runs at the level of autonomy its risk allows, from fully deterministic to fully agentic.

Determined · controlledAutonomous · agentic
Deterministic
Fixed steps, reproducible — no model discretion in the flow.
Autonomy 1 / 5
Fits — Fee checks · calculations · fixed procedures
BPM-Governed
A defined business process routes the work; rules drive the flow.
Autonomy 2 / 5
Fits — Regulated workflows · SLAs · sign-offs
Human-in-the-Middle
Agents do the work; a person approves at each gate.
Autonomy 3 / 5
Fits — Coverage · conflicts · anything contestable
Self-Organising
Agents route and adapt within policy and schema bounds.
Autonomy 4 / 5
Fits — Triage · enrichment · discovery
Pure Agentic
Autonomous reasoning within the sandbox and schema.
Autonomy 5 / 5
Fits — Extraction · summarization · low-stakes
The dial is per stepA single workflow can mix levels — extraction runs agentic, the coverage decision is human-gated, the fee calculation is deterministic. You put the automation where the work is routine, and keep the control where the risk is.
08 · Governance

Governed by construction

Every agent runs inside an isolated sandbox, calls only the tools it is authorised for, receives credentials only at execution, and writes a tamper-evident trail. Governance is not configured on — it is the default.

Execution sandbox
gVisor isolation · read-only FS · allowlisted network · time & memory limits
No exfiltration
Tool authorization
Read-only automatic · writes logged · admin actions multi-party
Per use case
Credential injection
AES-256 · HSM-backed · injected at run, destroyed after
Never in definitions
Testing & isolation
Unit · integration · security · performance, in a separate sandbox
Before publish
Audit trail
Hash-chained · encrypted · Auditor-only · no delete
1–2 yr retention
DataFab · The Agentic Studio · Interactive architecture reference · Illustrative
Layer 3 · Agentic utilities

A utility is the platform, pointed at a problem.

Ready-made agentic applications on the same Fabric and the same Studio — governed, auditable, and run against the systems you already have. Financial crime is one. The platform produces the rest, and any you build yourself.

Shown here

Financial Crime & Compliance

AML alert triage, sanctions & adverse-media screening, and generative compliance — investigation-console ready.
Inside this utility
Investigation consoleentities, timeline, network
Screening & alert triagesanctions · PEP · adverse media
Case → filingnarrative drafted, linked to source
Governed AI teamstraceable to a regulator
Click to expand ▾
Available

Due Diligence

Counterparty, transaction and onboarding due diligence over the resolved graph.
Inside this utility
Counterparty profileownership · control · UBO
Transaction reviewpatterns & anomalies
OnboardingKYC / KYB packaged
Reportsourced & defensible
Click to expand ▾
Available

Car-Finance Remediation

Motor-finance remediation at scale — cohorting, calculation and packaging.
Inside this utility
Cohortingaffected populations
Calculationredress, deterministic
OutreachAutoFab virtual agent
Packagingaudit-ready output
Click to expand ▾
Available

Legal CLM

Client-lifecycle & contract management — extraction, obligations and review.
Inside this utility
Extractionparties · terms · dates
Obligationstracked & alerted
Reviewclause-level, governed
Lifecycleintake → renewal
Click to expand ▾
Available

Insurance Claim Handling

Written claims worked end to end — coverage, prospects, fees and the drafted response, over the systems you already run.
Inside this utility
Intake & extractionper-field confidence
Coverage checkingclauses & endorsements
Prospects & feesmerits · statutory schedule
Draft & routegrounded · a person decides
Click to expand ▾
Available

Gov Intelligence & Investigation

Investigation and intelligence for public bodies — grounded and auditable.
Inside this utility
Entity & networkresolved across sources
OSINTgoverned enrichment
Case managementchain of custody
Assurancefully auditable
Click to expand ▾
In the Studio

Build your own

Any governed workflow the enterprise needs — composed in the Studio, on the Fabric.
Inside this utility
Composeagencies + widgets
Groundon the Fabric graph
Governsandbox · gates · audit
Publishreusable utility
Click to expand ▾
Trust & governance

Governed & certified by construction.

Security is woven through every layer — and independently certified.

ISO/IEC 27001:2022
Information security · certified
SOC 2 Type II
Trust services · certified
Resolve in place

Records never leave source systems.

Human-gated

Judgement stays with people.

Schema-bounded

No entities invented outside your schema.

Tamper-evident audit

Hash-chained, no delete, Auditor-only.

The living enterprise

One governed knowledge fabric.
Any critical workflow.

Connect the enterprise. Understand it. Build how it works. Let governed agents do the work — and let every validated result compound. The Financial Crime Unit is one utility; the same platform produces the rest, and any you build.

Connect the enterprise
Understand it
Build how it works
Compound every result
ISO/IEC 27001:2022
Certified
SOC 2 Type II
Certified
DataFab · The Enterprise That Understands Itself · Knowledge Fabric · Agentic Studio · Governed Utilities · Illustrative