Banking intelligence built for Saudi financial institutions.

We help banks put AI to work across credit, risk, operations and customer engagement, on top of the core and channel systems you already run, and designed against SAMA, NCA and PDPL expectations from day one.

Arabic-firstRight-to-left customer and staff experiences
Audit by designEvery decision and change attributable
Cloud or on-premiseDeploy inside the bank's own environment
Vision 2030 alignedDigital and financial-sector programme goals

حلول الذكاء الاصطناعي للبنوك في المملكة العربية السعودية

تساعد كروكس البنوك السعودية على توظيف الذكاء الاصطناعي في قرارات الائتمان، وكشف الاحتيال، وفحص المستندات، والخدمات المصرفية المفتوحة، وبرامج الولاء، مع تصميم يراعي متطلبات البنك المركزي السعودي (ساما) والهيئة الوطنية للأمن السيبراني ونظام حماية البيانات الشخصية، وبما يدعم مستهدفات رؤية 2030.

Why banks call us

The pressure points we are usually brought in to solve

Slow, manual credit decisions

Applications wait on document checks and manual review while customers apply elsewhere.

Fraud and risk moving faster than rules

Static rules miss new patterns and generate alerts analysts cannot clear in time.

Legacy cores limiting change

New products and open banking integrations take quarters because the core was not built for APIs.

AI without governance

Models in production without validation, monitoring or an audit trail create regulatory exposure.

Low digital engagement

Customers open an app, transact once and rarely return without a reason to.

Fragmented data

Customer, transaction and risk data sit in separate systems, so every model starts from scratch.

Architecture

One intelligence layer beside your core

We add decisioning and analytics next to core banking rather than replacing it, so risk stays low and value arrives sooner.

Channels
Mobile app
Internet banking
Branch & RM tools
Open APIs
Crux intelligence layer
Decision engine
Credit & risk models
Document AI
Loyalty & engagement
Systems of record
Core banking
Cards & payments
CRM
Data platform
Impact

What faster decisions can look like

Retail lending: illustrative before and after
Planning scenario for a consumer lending flow
Typical todayWith Crux
Time to credit decision (min)
240
5
Manual document review (% of cases)
85
25
False fraud alerts per 100
60
22
Time to launch a new product (weeks)
24
8
Illustrative scenario for planning conversations, not a guaranteed result. Actual outcomes depend on your data, processes and systems.
How we deliver

From first workshop to production in four steps

  1. 1

    Discover

    Map one high-value use case, its data, owners and regulatory constraints.

  2. 2

    Prove

    Build a working slice on your data in a controlled environment and measure it against today's process.

  3. 3

    Govern

    Validate models, document decisions and agree monitoring, approvals and audit with risk and compliance.

  4. 4

    Scale

    Roll out channel by channel, hand over to your teams and extend to the next use case.

Regulation & governance

Designed against the frameworks banks answer to

SAMA
Alignment with the SAMA Cyber Security Framework, outsourcing and operational-risk expectations.
NCA ECC
Controls mapped to the National Cybersecurity Authority Essential Cybersecurity Controls.
PDPL
Data minimisation, consent, retention and in-Kingdom data handling by design.
Model risk
Validation, explainability, drift monitoring and approval workflows for every model.
Auditability
Append-only decision and change history with maker-checker on every configuration change.

Crux designs and builds against these frameworks. Formal compliance and certification remain the responsibility of the institution and its regulators.

Questions

Answered plainly

Do you replace our core banking system?

No. Our solutions sit beside core banking and channel systems and consume data from them. The core remains the system of record.

Can the solutions run inside our own infrastructure?

Yes. They are containerised and can run on-premise, in a private cloud or in an in-Kingdom cloud region, depending on your data residency requirements.

How do you handle model governance?

Models go through validation, documentation and approval before release, then are monitored for drift and performance with a full audit trail.

Which banking areas do you cover?

Credit decisioning, document intelligence, fraud and financial risk, open banking, core modernization, and loyalty and engagement.

How long does a first project take?

A scoped proof on one use case typically takes weeks rather than quarters. We agree timelines after a discovery workshop.

هل تدعم حلولكم المتطلبات التنظيمية السعودية؟

نصمم ونبني الحلول وفق أطر ساما والهيئة الوطنية للأمن السيبراني ونظام حماية البيانات الشخصية، مع مسار تدقيق كامل وواجهات عربية. يبقى الامتثال الرسمي مسؤولية المؤسسة والجهات التنظيمية.

Next step

Start with one use case and prove the value

In a working session we map your highest-value use case, the data it needs and the controls your risk and compliance teams will expect.