Design partners. Build the account core with us.
A8 Core™ is pre-general-availability. A design partner shapes the account model, the delegation rules and the evidence format against a real institutional workload, before the interfaces are frozen.
Book the first conversation
Design-partner engagements start on the calendar, not in an inbox.
What a design partner gets
Access is scoped and contractual. Nothing on this page is generally available.
A named engineering counterpart
Direct access during the build, not a ticket queue.
Influence over the contract
Account types, delegation scopes, reason codes and export schema are still open. Design-partner input is how they get decided.
A sandbox before production
Request API access under the API Terms; production access is separately contracted.
Examination material
The authorization evidence your examiner will ask for, in a format you can review before you depend on it. See Examination support.
Who this fits
Institution-dependent. A design-partner engagement assumes an institution with its own regulatory posture.
| Institution | What they typically bring | What they typically need first |
|---|---|---|
| Trust companies and prospective charters | A charter path and an examination calendar | Account titling, custody records, examiner export |
| Retirement and benefit administrators | Plan and participant volume | Account types, contribution and distribution flows, tax reporting |
| Private-markets platforms | Alternative asset workflows | Asset servicing, valuation records, subscription handling |
| Banks and deposit partners | An FBO deposit relationship | Omnibus cash, reconciliation, money movement |
Five surfaces, as they are specified today
These are specified interfaces rendered from the documented contract — not screenshots of a running system, and not a claim of availability. Each carries its own status label. Payload values are illustrative.
How an engagement starts
1 · A scoping conversation
Your workload, your regulator, your timeline. No NDA needed for this step.
2 · Mutual NDA
Execute the mutual NDA before anything confidential is exchanged.
3 · A written scope
Which surfaces, which account types, which evidence. Signed under the Platform Licence.
4 · Sandbox access
Granted under the API Terms. Production access is a separate decision.
A8 Core is not accepting production workloads, is not offering accounts, and does not custody assets. Custody is Investor Services’ role; authorization is B5 Secure™’s.
Bring us a workload.
The interfaces above are still open. A design partner with a real constraint is worth more than a feature request.