Securing 2M+ accounts & $15B+ in assets, protected & secure·B5 Secure™ — per data-element authorization for .NET platforms·Now building on .NET 10

What B5 Secure Protects in Production

← Trust Center
Trust Center

What B5 Secure protects in production.

Most security products are evaluated on a description. This one has run in front of real money for years. Below is the deployment the numbers come from, what those numbers do and do not say, and the reason none of it obliges you to buy anything except B5 Secure.

Reference deploymentScope of the figuresIndependently deployable

The deployment

One platform, named plainly, with its lineage stated rather than implied.

B5 Secure is the authorization and evidence layer of ISCP→A8 Core™ — the Investor Services Cloud Platform and the account operating system reimagined and rebuilt from it. Every protected call in that platform resolves through the same fail-closed pipeline this site documents: the request is screened, the caller is authenticated, the environment is checked, the action is authorised at the record, and the decision is written to an evidence chain.

That is the whole claim. B5 Secure was not designed in the abstract and then looked for a customer; it was extracted from a platform that had to survive audits, and generalised for every modern .NET application afterwards.

Assets

$15B+

Under custody on the platform this framework protects.

Accounts

2M+

Individual accounts, each with its own authority boundary.

Security losses

$0

Security-related losses to date on that platform.

What those numbers say, and what they do not. They describe the security and processing integrity of the ISCP→A8 Core™ lineage. They are not investment performance, not a guarantee, and not a statement about assets held anywhere else. A figure whose scope is not stated is not evidence, so the scope is stated here and on every page that repeats it.

Why this is not a reason to buy a platform

B5 Secure is the bottom layer, and it is the only layer you can buy on its own. A8 Core™ depends on B5 Secure. B5 Secure does not depend on A8 Core™, and nothing in it assumes a custody platform, a ledger, or a financial account of any kind. It is a .NET 10 library and pipeline that enforces authority inside your own process, in your own cloud.

So the honest way to read the figures above is this: that is what this looks like at $15B scale, and you do not have to buy the platform to get it. The reference deployment is evidence that the design survives real conditions — not a bundle you are being routed into.

What travels

The enforcement and the evidence

The pipeline, data-element authorization, delegation with expiry, reason codes on every outcome, and the signed decision chain. All of it is framework, not platform.

What does not

Anything account-specific

No ledger, no custody model, no financial schema. The account examples in these docs are examples. Your records are whatever your application already calls a record.

What you can check without asking us

A production claim you cannot inspect is still just a claim.

The decision evidence B5 produces has a published format and an offline verifier that has no dependency on B5 software, no network access and no configuration. You can take an export, run the tool, and satisfy yourself that the chain is intact — then alter one character and watch it refuse.

Evaluate the layer, not the lineage

The deployment above is why we can describe this with specifics. Whether it fits your application is a different question, and a shorter one.

Scroll to Top