Production in Saudi Arabia
Client files, extracted data, model inputs and outputs, application records, logs and backups stay in Saudi Arabia.
Security and deployment boundary
Data in Saudi Arabia. Keys with the institution.
Data never leaves Saudi Arabia. Keys stay with the institution. RSEEN runs single-tenant or on-premises, with application and inference data in-Kingdom.
Deployment options
Inside the institution
RSEEN can run inside institution-controlled infrastructure with agreed responsibilities, integrations, updates, support and recovery.
Integration routes
Inference, OCR, messaging, signing and client-system routes are documented within the deployment boundary.
Keys with the institution
The institution controls key custody, lifecycle, service permissions, recovery and break-glass access.
DEPLOYMENT BOUNDARY
- Single-tenant or on-premises deployment
- Institution-controlled keys
- Application, inference, logs and backups in Saudi Arabia
- Documented provider and integration boundaries
- Defined support and recovery paths
- Security evidence ready for review
INFERENCE IN PRODUCTION
In production the models run on the institution's premises or inside Saudi Arabia. We work with more than one in-Kingdom inference provider, and the route for a given deployment is agreed in the deployment review with the institution's security owner.
What your security team can inspect
- 01Access and support
- Who can access what, for which purpose, under whose approval, and how is break-glass access recorded and reviewed?
- 02Logs
- Which named event classes are covered, and what are the limits of coverage, retention, query and export?
- 03Backup and recovery
- Where are copies held, who controls keys, what recovery objectives apply, and how are restores tested?
- 04Retention and egress
- What is exported, deleted or retained at scope exit, with which evidence and accountable owner?
- 05Providers and data route
- Which providers receive which data classes, in which region, and what fallback applies if a route is ineligible?
- 06Authority and segregation
- How do identity, roles, segregation of duties and decision authority map to the institution’s model?
AUDIT TRAIL
The credit workflow remains attributable
RSEEN keeps an append-only, attributable audit trail of the supported credit workflow—who did what, when, and against which evidence. It is written for its readers: internal audit, the credit risk committee, and the SAMA supervisory examiner following one figure from source to decision.
Security diligence evidence
Your security team can review architecture decisions, threat models, test results, gap registers, and support and recovery procedures under NDA.
Shared-responsibility boundary
A security boundary your team can inspect.
Data never leaves Saudi Arabia. Keys stay with the institution. The map shows where each layer runs and who owns the decision.
Institution boundary
Decision and operating authority Identity, authority, keys, data policy and the credit decisionRSEEN platform boundary
Optional providers and connectors
Documented routes Inference, OCR, messaging, signing and client systemsBuilt into RSEEN
- Request bound to case, provenance and execution route
- Traceable case result or clear stop reason
- Credit tables computed by formula, with any withheld grade visible
- RSEEN Core works as a standalone product; further modules are planned and scoped with each institution
Configured for the institution
- Identity, roles, key custody and storage
- Provider eligibility, residency, egress and logs
- Backup, restore and recovery objectives
- Support, break-glass, retention, exit and connectors
RSEEN keeps an append-only, attributable audit trail of the supported credit workflow—who did what, when, and against which evidence. It is written for its readers: internal audit, the credit risk committee, and the SAMA supervisory examiner following one figure from source to decision.
The map keeps responsibility clear from evidence and computation through workflow and credit decision.
Review the deployment boundary with RSEEN.
Start with the deployment shape, data route, key custody and required integrations.