Skip to main content
Adaptive Banking · Product Foundation

Faster change,
with stronger control.

BX-CBP-based offerings reuse banking capabilities through components and APIs. Product composition is defined for each offering. Where microservices and containers are required, BX-CoCore can be evaluated as a separate alternative Main Product.

Architecture

Bankware Global Adaptive Banking Architecture

The reusable banking engine of BX-CBP-based offerings, built around BX-CBB.

BX-PF
Product Lifecycle Management
Defines financial products and their conditions, and manages them through their lifecycle.
BX-RDF
Rules and Parameters
Externalises business rules, organisation, business calendar and operating parameters.
BX-CBBEngine · reusable banking logic
Actor / Customer
Product
Engagement / Contract
Calculation
Ledger
Pre-built banking servicesDepositLoanFX and other Exposed through APIs
Core architecture options
BX-CBP
Component-based core banking
Default Main Product for core banking suites and core-banking-based domain-specific software within Banking Software. Built on the engine above, composed with BX-PF and BX-M or BX-CM, and optionally BX-I. Runs on-premise or in cloud.
Default Main Product
BX-CoCore
MSA and container-based core banking
A separate Software Product, with core banking re-architected as microservices in containers. Where an offering requires MSA and containers, it can be evaluated as the alternative Main Product, subject to technical assessment.
Alternative Main Product
About BX-CoCore

BX-CBP and BX-CoCore are different product architectures, not deployment options of one product. The BX-CBP composition does not transfer to BX-CoCore automatically.

Comparison

Conventional approach vs Adaptive Banking

Four areas where the approach changes what a project looks like.

AreaConventional approachAdaptive Banking
Products and rulesOnly selected product attributes are configurableExternalises the product lifecycle and business rules
Business logicSimilar logic is duplicated in each programReuses standard banking logic through components and APIs
Change impactMany programs and tests change togetherReusable components reduce duplicated logic and help contain the impact of change.
Core architectureFixed to one legacy monolithBX-CBP by default; where MSA and containers are required, BX-CoCore can be evaluated as a separate alternative Main Product
Core architecture

Core architecture options

BX-CBP and BX-CoCore are different product architectures, not deployment options of one product. The BX-CBP composition does not transfer to BX-CoCore automatically.

BX-CBBEngine · reusable banking logic
Actor / Customer
Product
Engagement / Contract
Calculation
Ledger
BX-CBP
Component-based core banking
Default Main Product for core banking suites and core-banking-based domain-specific software within Banking Software. Built on the engine above, composed with BX-PF and BX-M or BX-CM, and optionally BX-I. Runs on-premise or in cloud.
Default Main Product
BX-CoCore
MSA and container-based core banking
A separate Software Product, with core banking re-architected as microservices in containers. Where an offering requires MSA and containers, it can be evaluated as the alternative Main Product, subject to technical assessment.
Alternative Main Product
About BX-CoCore

Separately defined compositions

The composition above applies to BX-CBP-based offerings. These offerings have their own Main Product and product composition; the BX-PF and BX-M or BX-CM rules are not applied to them automatically.

Contact Sales

Discuss the Product Foundation.

Tell us about your institution and what you are evaluating.