DataBridge by Walnut Home

Technical overview

Architecture, model options, data handling, access control, connectors, exports and what a security review receives, for IT, data and security reviewers.

For IT, data and security reviewers: how DataBridge is installed, what it reads, how it is checked and how you leave.

An enterprise platform that turns your organisation's fragmented data into trusted, usable knowledge that every team can find, check and act on.

The other pages of this site keep to plain business language and point here for the detail.

Architecture and deployment

Two layers on one foundation

A Company Brain that connects your data, and the intelligence layer that puts it to work for every team.

What stays where

Every part of DataBridge in detail

What it is

The five steps

Inside the Company Brain

The intelligence layer

Security and control

Model options

Work that needs no model

Matching records, reconciling, building reports and exporting are ordinary software. The same inputs and rule version give the same result.

Reconciliation by rules a person can read

Reconciliation is ordinary software comparing two records of the same money by rules a person can read.

The model you choose, or none

You decide which model DataBridge uses, you can host it locally, and DataBridge also runs with no model at all.

Nothing a model suggests is added or sent until a person approves

A fact a model suggests waits outside the record until a person confirms it, and a drafted email goes out only after approval. Each confirmation is a dated record.

Numbers checked by ordinary code

A number in a model-written sentence is checked by ordinary code against a cited fact, or the sentence is refused.

Instructions hidden in files are quoted as content

An email or a file can carry text written to steer a model. DataBridge treats it as content, which can be quoted; in a test on synthetic data in August 2026, 26 of 26 planted attacks were contained, and none of the planted instructions was followed.

What is logged for each call

Each use of AI is recorded, with a digest of what went in and what came out.

Data handling and history

Every version is kept

A correction adds a new version and keeps the old one, and an attempt to edit a recorded fact is refused. You can read what the record said on any past date.

Each figure read from a file points to its source

Each figure read from a file points to the cell, line or page it came from, with its validation status. The original files are kept unaltered.

Access control

Access follows each person's role, and confidential material sits in a store of its own with its own key.

Who sees what

Your administrators set the roles once, and access follows each person's role from then on.

Confidential material in a separate store

Confidential material is kept in a separate store with a key of its own, and the everyday view is the same whether or not that store holds anything.

Connectors and formats

Databases, documents, spreadsheets, email and the systems your teams already use. Each source connects once, and your systems carry on as they are.

Your operator decides how each source reaches the record and how often, and every route runs inside your environment.

Twelve kinds of record, and where each is kept today

Exports

The whole record can be exported in open formats, and the export is tested in front of you.

Leaving with everything

One command exports the whole record in open formats, with every value, every version and every source reference. We restore it into a fresh system in front of you, the result is checked against its digest, and you keep the digest.

The export self-test

A self-test of the export and restore ships with the product, and your team can run it without writing a line of code.

The shape each job needs

Serves that record in the shape each job needs: answers, reports, analytics tables, AI context and training datasets.

The same value in every shape

An answer, a table row, an export entry and a workbook's value cells carry the same value and the same source as the fact they came from.

What a pilot hands over

You keep the record built from your data and the transcript of everything asked and answered during the pilot. One command exports both, with a digest you keep.

What a security review receives

Your IT, privacy and vendor-risk reviewers get the full architecture sheet before anything is installed. The disclosure policy and the model use statement are on this site.

Security questions and reports go to outreach@walnut.sg.

How this website itself is run

The model use statement, for your records

Why DataBridge wins

Six capabilities, compared across the kinds of tool teams use today.

Only DataBridge spans the Company Brain, the meaning of your data and every output your teams use.

It starts with a demo on a sample of your own documents and data.