Question 1

What is the AFI Platform?

Accepted Answer

The AFI Platform is the banking orchestrator: the event-native infrastructure that delivers banking orchestration, unifying systems, people, and processes on a single substrate. AFI names the category; the AFI Platform is the substrate a financial institution deploys.

Question 2

What does “event-native” mean, and why does it matter?

Accepted Answer

Event-native means every transaction, API call, and ledger update is an event that carries full context from the moment it enters. Apache Kafka is the event backbone; Apache Iceberg unifies historical and streaming data. It is not a batch system with an event layer bolted on, which is why it is the prerequisite for agentic AI that must reason over real-time state.

Question 3

What are the three layers of the AFI Platform?

Accepted Answer

Top-down: the Experience Layer (white-label) is the institution’s customer-facing surface, under its own brand; the Orchestration Layer (event-native) is where banking orchestration happens, on Apache Kafka and Apache Iceberg; the Runtime Layer (container-first) is the base it runs on, individual microservices on Kubernetes, Helm, and Terraform.

Question 4

Does the AFI Platform replace our core or our payment rails?

Accepted Answer

No. The AFI Platform is an overlay, not a system of record. It reads the institution’s core, routes payments across the rails already in place, and powers the digital channels above. A rail integrated once flows to every channel.

Question 5

How does the AFI Platform handle failure?

Accepted Answer

Every category runs in isolation on the Runtime Layer. A failure in one — say, a payment rail — is contained at its boundary and does not propagate to identity, ledger, or reporting. This is architectural containment, not incident response.

Question 6

Who operates the AFI Platform?

Accepted Answer

The institution operates it. The AFI Platform is deployed on cloud environments the institution controls — AWS, Google Cloud, or IBM Cloud for Financial Services — with the institution’s own identity, keys, and data boundaries. XYB provides the substrate, its updates, and its support model; day-to-day operations sit with the institution’s platform team, the way any modern infrastructure platform does.

Question 7

Is the AFI Platform production-grade?

Accepted Answer

Yes. It orchestrates 1M+ transactions per minute in production today. It unifies context in real time on Apache Kafka and Apache Iceberg. It is SOC 2 Type II attested. First production value lands in about 10 weeks, with no system replacement required.

The Banking Orchestrator. Unifying Context.

Bank Scale. Unified Context. Independently Audited.

Built Event-Native. From the Ground Up.

Event-native, not bolted-on.

Unified, not fragmented.

Governed, not retrofitted.

Countless Offerings. One Orchestrator.

Three Layers. One Event-Native Substrate.

Experience Layer

Orchestration Layer

Runtime Layer

One Backbone. One History. One Live Picture.

Event-native orchestration

Real-time data unification

Two Solutions. One Platform.

Digital Banking Your Customers Expect. Adapt in Weeks.

Own the Treasury Offering Your Customers Need. Adapt in Weeks.

The AFI Platform, in Plain Terms.

See the Platform Under the Hood.