How Revolut runs AI at scale
Summary
Revolut, a regulated bank serving over 70 million customers across 40+ countries, manages AI at scale by focusing on a robust control plane rather than just the models themselves. Nikolay Donets, head of ML engineering, highlighted at RAAIS 2026 that the challenge lies in governance, cost controls, measurable fallbacks, and human review for its 200+ products. Since 2022, with the rise of large models via APIs, Revolut shifted from classical ML to a unified approach. They implemented a single gateway and governed AI by use case, aligning with the EU AI Act. This central platform, which now handles roughly twice as many generative use cases as classical ML, ensures "zero effort" upgrades and centralized compliance. Their AI assistant, AIR, evolved from a basic chatbot to a sophisticated system handling 25,000 calls monthly, resolving issues 8x faster, and boosting resolution rates from 17% to 80%. Revolut maintains strict human oversight, ensuring no life-changing decisions are made by AI.
Key takeaway
For AI Architects or MLOps Engineers building systems in regulated industries, Revolut's strategy underscores that operationalizing AI at scale hinges on a centralized control plane, not just model performance. You should prioritize establishing a single, governed gateway for all AI access and implement robust fallback mechanisms for external models. Critically, ensure human oversight remains the final arbiter for any life-changing decisions, even as AI improves efficiency.
Key insights
Scaling AI in regulated environments demands a robust control plane and use-case-centric governance over individual model focus.
Principles
- Govern AI by use case, not model.
- Centralize AI access via a single gateway.
- Implement multi-tier fallback chains for external models.
Method
Revolut established a single AI gateway with a governance layer, shifting from individual team libraries. They adopted use-case-based risk assessment, implemented fallback chains for external models, and embedded AI engineers in product teams while maintaining a central ML engineering group for standards.
In practice
- Deploy a central AI gateway for all product teams.
- Mandate per-model visibility, not just interface monitoring.
- Prioritize smallest effective models over newest.
Topics
- AI Governance
- MLOps
- Financial Services AI
- Generative AI
- AI Control Plane
- Revolut AIR
Best for: CTO, VP of Engineering/Data, Executive, MLOps Engineer, AI Architect, Director of AI/ML
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Air Street Press.