Agentic AI is the next major architectural shift in banking technology. Just as cloud computing transformed infrastructure and microservices transformed application design, intelligent agents will transform how banks automate operations, serve customers and support employees. Many institutions are beginning this journey with open-source frameworks such as LangChain, LangGraph and other orchestration technologies. These are outstanding engineering tools. But they should not become the enterprise architecture.

At Emirates NBD, we believe every large bank should engineer its own enterprise agentic framework — one that leverages open-source technologies underneath while presenting a stable, governed platform for application teams. This is the philosophy behind our Leap AI Agentic Framework, and it is one of the major pillars of our AI strategy: Leap is what allows us to ship AI at the relentless pace this technology demands, with every control a regulated bank requires engineered in from the first line of code.

History offers a useful analogy. Few enterprises expose Kubernetes directly to thousands of application developers. At Emirates NBD, we instead built internal platforms — paved roads — that standardise security, networking, observability, deployment pipelines and operational practice. Kubernetes became an implementation detail rather than the interface developers build against. The same engineering principle applies to agentic AI.

The hard problem for banks is not calling a large language model. Connecting to GPT, Claude, or Gemini is a few lines of code. The real challenge is ensuring that every AI solution complies with enterprise security standards, regulatory expectations, data governance policies and architectural principles. Banks must control how agents authenticate to core banking systems, how sensitive customer data is protected, how every decision is audited and explainable, how reasoning is traced end-to-end, where human oversight is enforced for material actions, and how agent behaviours are monitored in production. These are enterprise concerns, closer to model risk management than to prompt engineering, and they extend well beyond the scope of any open-source framework.

This is where an enterprise framework such as Leap creates lasting value. Rather than asking every engineering team to solve these problems independently, Leap delivers them as platform capabilities. A team building on Leap inherits authentication, authorisation, observability, audit logging, model governance, prompt management, evaluation, cost and token controls, and enterprise tool integration by default. An agent built on Leap is, in effect, born governed. Engineers focus on the business problem; the platform guarantees the controls.

An equally important benefit is technology independence. The AI ecosystem is moving at an extraordinary pace: new foundation models, orchestration frameworks and reasoning techniques appear almost monthly. Applications tightly coupled to today’s technologies will require continuous refactoring tomorrow. By introducing a stable enterprise abstraction layer, banks can adopt new models and frameworks inside Leap without touching business applications. The platform evolves; the applications remain stable.

An enterprise framework also establishes engineering consistency at scale. Without common standards, different teams inevitably adopt different frameworks, integration patterns and governance models — creating fragmentation, duplicated effort and operational risk that no regulated institution can afford. Leap defines a single architecture for every AI solution, enabling thousands of agents to be developed with the same engineering practices, security controls, and operational tooling. There is one way to build an agent, and it is the governed way. This consistency becomes ever more valuable as AI adoption scales across the enterprise.

None of this diminishes the importance of open source. On the contrary, the rapid innovation taking place in the open-source community is one of the greatest strengths of the current AI ecosystem, and open source is part of Emirates NBD’s engineering DNA. Banks should actively leverage technologies such as LangChain and LangGraph. The key architectural decision is simply where those technologies belong: inside the enterprise platform, not defining its external interface. By integrating open-source innovation centrally, the bank enables every engineering team to benefit from new capabilities without introducing fragmentation or increasing operational complexity.

Ultimately, the competitive advantage of banks will not come from owning the best language model. Foundation models are rapidly commoditising, and institutions will continue to adopt whichever models offer the best combination of performance, cost, and regulatory suitability. The durable differentiator will be the engineering platform that governs, secures and operationalises those models at scale.

The Leap AI Agentic Framework embodies this philosophy. It is not intended to compete with open-source orchestration frameworks, but to provide the enterprise abstraction layer that allows the bank to embrace them safely and consistently. By combining the innovation velocity of the open-source ecosystem with bank-grade governance, security and architectural discipline, Leap enables us to build thousands of intelligent agents on a foundation that remains stable even as the AI landscape shifts around it. In banking, speed and control are usually presented as a trade-off. However, build the right platform and it compounds. This is the architecture that will set apart the leading banks in the era of AI.