Skip to content
Barklem&ChiBarklem&Chi

Ecosystem

Two vehicles, one infrastructure framework.

Barklem&Chi operates as the parent infrastructure company. Each vehicle is a distinct technology company with its own market, operating model and governance surface — built on layers the group defines once.

Commodities & trade infrastructure

nelum.techIn operation

An institutional marketplace facilitation service for the global precious metals and physical commodities trade. Nelum digitises the trade lifecycle through business verification (KYB), stage-gated transaction workflows and verified funding mechanisms, so high-value physical supply chains stay transparent, accountable and internationally acceptable.

Verification
Entity-level KYB
Workflow
Stage-gated transactions
Funding
Verified on-chain

Emerging market fintech · Nigeria

veridity.techIn development

A digital wealth and capital infrastructure platform for the West African landscape, in development for the Nigerian market. Veridity uses automated framework logic to organise domestic capital, lower the operational cost of serving a participant, and hold institutional operating standards from the first release rather than as a later retrofit.

Logic
Automated frameworks
Capital
Local efficiencies
Standards
Institutional from day one

Parent and vehicle

What the group holds, and what each vehicle owns.

Technical framework and standards
Barklem&Chi
Compliance policy and controls
Barklem&Chi
Market strategy and product
Vehicle
Counterparty relationships
Vehicle
Operating model
Vehicle, centrally governed

Shared framework

Built once, inherited by every vehicle.

Two products in different markets run on the same four layers. Only the market logic above them differs.
01

Identity and verification

Entity verification, ownership and authority held at group standard. Nelum applies it to counterparties in physical trade; Veridity applies it to market participants.

02

Workflow and state

Stage-gated processes where the platform holds state rather than the parties — trade lifecycle in one market, account and allocation lifecycle in the other.

03

Rules and controls

Policy encoded as executable rules: limits, permissions and conditions enforced at the point of action instead of reviewed afterwards.

04

Record and reporting

An immutable, audit-formatted record of what happened and on what evidence, produced as a by-product of operation rather than assembled on request.

Admission

What a third vehicle would have to satisfy.

The same four tests are applied before anything is incubated, including our own ideas. Most do not pass.
01

Structural friction, not preference

The problem must persist because the market has no shared infrastructure for it, not because incumbents are inattentive.

02

Verifiable state

The facts the market disputes must be capable of being evidenced and recorded, so software can hold them rather than describe them.

03

Framework fit

It must be able to inherit the group's verification, control and reporting layers without a parallel standard being written for it.

04

Portable records

Its records must be legible to counterparties, auditors and regulators outside the market it starts in.

Founding office

Integrating with a vehicle, or building one with us?

Talk to the founding office