Contact sales
Industries/Banking

One view of the customer, built on the systems you already trust.

Banks run on core banking, cards, lending and CRM systems that rarely agree. WhoDB connects them in place and models customers, accounts and exposures once, with access scoped to every person who looks.

In placecore systems stay where they are
Per personaccess on every record and query
Every changedrafted and reviewed before it goes live
Privatedeployment inside your own cloud
IN THE PRODUCT

A customer record everyone can agree on.

Pick a point on the left to see where it lives on the screen. Every screen shown here comes from the Clidey ERP demo project.

APP.WHODB.COM / APPS / CUSTOMER-360DARK
1One view of the customer
HOW IT WORKS

From scattered systems to one trusted customer view.

01
Connect the coreConnect core banking, card, lending and CRM databases without copying them.
02
Model the customerDefine customer, account and exposure entities with the fields risk and operations both use.
03
Trace every figureLineage shows which system and which transform produced each balance or score.
04
Build the toolsGive relationship managers and risk teams apps that read the same records.
CUSTOMER MODEL

Customers, accounts and exposures, related once.

Relationships between customers, accounts and facilities are declared in the model, so a question about total exposure has one answer.

✓Customer, account and facility entities✓Declared relationships between them✓Sample rows for every entity
Customer8 PROPERTIES
customer_idStringRequiredProminent
legal_nameStringRequiredProminent
segmentStringRequiredNormal
relationship_managerStringNormal
total_exposureNumberNormal
kyc_statusStringRequiredNormal
ACCESS

Every grant visible, by person or by resource.

Organization access shows who can reach which files, apps and functions, which is the first thing an auditor asks for.

✓Grants listed by person or by resource✓Project level scopes✓The agent bound by the same rules
Access by resourceRISK PROJECT
RESOURCETYPESCOPEPEOPLE
CustomerentityProject12 people
Exposure viewappTeam4 people
limits_checkfunctionProject3 people
facilities.csvfileProject2 people

What it changes for each team

RELATIONSHIP MANAGERSThe whole customer on one screen.Accounts, products and recent activity in one app, without logging into four systems.
RISKExposure you can trace.Every figure links back to the source and the transform that produced it.
TECHNOLOGYNo new copy to secure.Core systems stay in place. WhoDB reads them with the credentials you approve.
THE DETAILS

For the people who will ask.

The specifics your architects and security reviewers will want before a rollout.

SOURCESRelational, warehouse and document stores used by core and channel systems
DATA MOVEMENTNone required to explore
ACCESSProject members, roles and per resource grants
CHANGESDraft, review and promote
AI AGENTBound by the asking person's permissions
DEPLOYMENTManaged Private inside your own cloud, or WhoDB Cloud
EXAMPLE WORKFLOWOne
Customer definition shared by risk, operations and sales.Instead of each team reconciling its own extract, every app and report reads the same customer, account and exposure entities.

Common questions

With Managed Private, WhoDB runs inside your own cloud environment next to your data, backed by our team for security and maintenance support.

Keep exploring Industries

Industries overview →

Bring one banking workflow to a walkthrough.

Show us your architecture and the workflow that matters most. We'll walk through it with you, on your data.