Product status & availability. Labeled honestly.
This page states where each A8 Core™ product actually stands — what is running with design partners, what is specified, and what depends on providers or production release. It is distinct from infrastructure status and is maintained manually by the A8 Core™ team.
Status definitions
Five labels, used consistently across the site.
Design partner
Operating with design partners; availability is limited and institution-configured.
Foundation
Core capability built and evolving; depth varies by workflow.
Product specification
Fully specified and in design-partner recruitment; not yet generally built.
In progress
Under active development; not generally available.
Provider dependent
A8 Core™ produces the data and workflow; final capability depends on the institution’s providers and certifications.
Current status
Maintained manually; ask for the latest detail in a working session.
| Product | Status | Availability | Dependencies |
|---|---|---|---|
| Account core | Design partner | Limited | Institution configuration |
| Omnibus custodial cash | Product specification | Design-partner recruitment | Bank and network integrations |
| Trust accounting | Foundation | Limited | Jurisdictional rules |
| Note servicing | Foundation | Limited | Payment and legal integrations |
| Tax reporting | Foundation | Provider dependent | Filing certification |
| React portals (Experience SDK) | In progress | Not generally available | Production release |
| Custody command fabric | Product specification | Design-partner recruitment | Custodian integrations and authorized relationships |
| Financial data hub & reconciliation | Product specification | Design-partner recruitment | Provider integrations |
| SDIRA compliance center | Foundation | Educational content live; controls institution-configured | Institution policy |
| Operations Studio | In progress | Not generally available | Production release |
| Migration Factory | Product specification | Engagement-scoped | Source-system access |
| Integration Exchange | Product specification | Design-partner recruitment | Partner authorizations |
API surface
Two figures are published for the API surface and they are not the same kind of statement. One counts what exists in the codebase today. The other is a target for a release that has not happened.
| Figure | What it counts | Status |
|---|---|---|
| 600+ endpoints | Path and method combinations across the five service families | Verified — current codebase |
| 800+ endpoints | Path and method combinations targeted for the Q4 2026 release | Roadmap — targeted, not built |
An endpoint here is one path and method pair. Counting paths alone gives a smaller number and counting operations gives a different one again, so the basis is stated with the figure rather than left to the reader.
How to read this page
A8 Core™ does not present any module as further along than it is. Historical ISCP operating experience is lineage, not current A8 Core™ production status. Where a capability depends on an institution’s charter, contracts, or providers, that dependency is stated rather than assumed away.
Want the detail behind a status?
A working session covers current build state, design-partner scope, and the roadmap under NDA.