InfrastructurePart of the Finxis CDM toolchain

Turn your CDM applications into a service network.

The CDM ships as a library, and a library only runs when something calls it. CDM Node wraps the model in a service architecture — always on, routing CDM objects between your own systems and out to counterparties. CDM Net connects those nodes into a private network.

Start free trial Request information

Runs internally or externally · Blockchain optional · Java 17

Three nodes

One per job, so each stays in its own zone.

Node is not one process. It is three, split along the lines a bank already segments its network — so the component facing the internet is not the component holding your trade data.

E-Node

External · the gateway

Peer to peer CDM connectivity.

Faces the internet. Finds peers, accepts inbound traffic and passes it inward without ever opening the payload — so compromising the gateway does not expose CDM business data.

I-Node

Internal · the service core

Validate, store and route CDM objects.

Where CDM objects actually live. Validates them against the model, persists them, and routes them between your applications and out through the gateway. Stays on the secure network and is never exposed directly.

D-Node

DLT · the chain gateway

Connect to a private or public blockchain and execute smart contract services.

The gateway to a chain. Commits and confirms event hashes, and executes smart contract services. Sees hashes, never trades — and it is entirely optional. Run the first two nodes and never touch DLT if that is not your world.

Bilateral attestation

Both sides confirm the same trade.

Add a D-Node and each firm independently commits the same CDM event to a shared chain. When both have confirmed it, the record is attested — a tamper-proof bilateral audit trail neither side can quietly revise.

01 — PENDING

One side has committed

The event hash is on chain. The counterparty has not confirmed it yet.

02 — ATTESTED

Both sides agree

Two independent confirmations of the same event. One agreed version of the trade.

03 — DISPUTED

The hashes differ

A disagreement surfaces immediately, at the point it happens, rather than at end of day.

04 — EXPIRED

No confirmation came

The window closed unconfirmed, and that fact is recorded too.

Only hashes go on chain. Trade data never leaves your infrastructure, so an attestation proves two parties held the same event without either publishing what it contained.

Bilateral attestation — two nodes, one shared chain Screenshot to follow

Live attestation flow

Architecture

Built to pass a security review.

The three-tier split is the reason a bank can approve this. Each node sits in the zone it belongs in, and the data each one can see is bounded by design rather than by configuration.

Node	Network zone	Sees	Exposed to
E-Node	DMZ	Opaque payloads only	The internet
I-Node	Secure zone	CDM business data	Internal network only
D-Node	DLT zone	Hashes only	Chain endpoint

Peers do not have to be on your CDM version.

Nodes negotiate on connection. Each side advertises the CDM versions it supports, and the handshake settles on a version both can speak — so a counterparty running an older release is a compatibility check rather than a blocker.

Monitor — live message feed Inbound · outbound · errors

CDM Node monitor showing a live feed of trade executions, allocations, confirmations and settlements with inbound and outbound counts

Deployment

Start where it makes sense.

INTERNAL

A router inside the firm

Move CDM objects between your own applications. No counterparties, no chain — just the model running as a service across your estate.

EXTERNAL

Out to counterparties

Add gateways and exchange CDM events directly with other firms, peer to peer. CDM Net handles the connectivity.

ATTESTED

With bilateral proof

Add a D-Node when you want an agreed, tamper-proof record of what both sides confirmed.

Peers — active connections CDM version · throughput · latency

CDM Node peers view showing three active connections with CDM version, message counts and ping latency for each

Built with CDM Workbench — workflows designed and tested there run here.