AI Agent Development Company in Jeddah

Start by counting the agent roles and naming the estate they will run inside: a scoped Jeddah agent proof of concept, or production agent systems — Bayan customs automation for a Jeddah Islamic Port freight forwarder, Nusuk-integrated Hajj operator copilot, SAMA-aligned SNB treasury agent. Scope drivers include PDPL data classification, NCA ECC scoping, a working prototype, Arabic plus English UI, integration count, regulatory scope, and the number of agent roles. NCA Critical Systems agents inside SABIC Jeddah or other CSCC-classified estates trend higher because of sovereignty and air-gap testing requirements. Pricing is fixed-fee with milestone billing in SAR, VAT itemised on the ZATCA tax invoice, and no open time-and-materials clauses.

Saudi Arabia's Personal Data Protection Law (PDPL), enforced by SDAIA since September 2024 after the one-year transition, treats agent-driven automated decisions as a regulated activity. Lawful basis (consent, contract, or legitimate interest as recognised in the executive regulations), purpose limitation, data minimisation, and breach notification within seventy-two hours all apply. Cross-border transfer requires SDAIA approval or an adequacy decision, so we keep agent memory, vector stores, and tool-call logs inside AWS me-central-1 (Riyadh) or Azure Saudi Arabia by default. Every agent action is logged with the data subject identifier, the purpose code, and the legal basis, and your DPO gets a one-click PDPL Article 9 access request export. We also build the Arabic-language consent UX with explicit opt-in, withdrawal, and re-consent flows.

Yes. ZATCA Phase 2 (integration phase) requires resident taxpayers to integrate with the Fatoora platform via API, generate cryptographically signed XML invoices in UBL 2.1 format, embed QR codes, and submit invoices for clearance (B2B) or reporting (B2C) within prescribed windows. Our agents wrap that integration end-to-end — extracting invoice data from procurement workflows, generating the signed XML with the right tax categories and SAR amounts, calling the Fatoora compliance API, handling clearance responses, and writing back to SAP, Oracle, or Microsoft Dynamics. For Jeddah freight forwarders and petrochemical resellers we have handled the mandatory 15 percent VAT reverse-charge edge cases and the bilingual Arabic and English invoice layouts ZATCA expects. The agent retries on Fatoora timeouts, escalates to a human on rejection codes, and keeps the cryptographic stamp chain intact for the seven-year retention.

Yes. Licensed Hajj and Umrah operators in Jeddah and the wider Makkah region work through the Ministry of Hajj and Umrah's Nusuk platform (formerly Tawakkalna Services for pilgrimage) for visa issuance, group registration, and itinerary management. Our agents authenticate against the Nusuk operator APIs, coordinate pilgrim data flows under PDPL with explicit consent, and run multilingual support across Arabic, Urdu, Bahasa Indonesia, Turkish, French, and English using fine-tuned Arabic-first models with proper diacritisation handling. Transport scheduling agents coordinate with licensed land transport companies regulated by TGA (Transport General Authority), and accommodation booking agents respect the seasonal pricing rules around Hajj. PII stays inside Saudi regions, every pilgrim interaction is logged for the ministry's reporting requirements, and Arabic RTL is the default UI direction rather than a localisation afterthought.

The Saudi Central Bank (SAMA) issued AI and machine learning guidance covering governance, risk management, explainability, and Sharia compliance for Islamic finance workloads. For agents inside SNB, Al Rajhi, Riyad Bank, or Banque Saudi Fransi Jeddah branches we run a SAMA AI risk classification at discovery, build the explainability layer (decision logs, feature attributions, counterfactual reason codes) into the agent rather than bolting it on, and add a Sharia compliance gate for any agent that touches Murabaha, Ijara, Sukuk, or other Sharia-structured products. Model risk management documentation aligns with SAMA's expectations on independent validation, challenger testing, and ongoing monitoring. We coordinate with the bank's internal Sharia board and risk function from week one, not at deployment, so the audit trail does not need a retrofit.

We default to AWS me-central-1 (Riyadh, launched in 2024 and the first AWS region inside Saudi Arabia) for general-impact PDPL workloads, and Azure Saudi Arabia (Jeddah and Riyadh paired regions) where clients have existing Azure enterprise agreements through SNB, SABIC, or Aramco-adjacent suppliers. AWS me-south-1 (Bahrain) is acceptable for non-critical workloads where SDAIA cross-border conditions are met. NCA Critical Systems Cybersecurity Controls (CSCC) workloads run on dedicated tenancy with hardware security module (HSM) key management, often paired with self-hosted models on Saudi GPU instances. We document residency in the data processing addendum signed under PDPL, in the NCA ECC compliance attestation, and in the SAMA model risk file when applicable, so your audit team and SDAIA assessors get a single source of truth without a vendor handover.

Yes. Bayan is the Zakat, Tax and Customs Authority (ZATCA) electronic customs declaration system used at Jeddah Islamic Port for import and export clearance, and Fasah is the integrated logistics platform covering trucking permits, manifest matching, and port community workflows. Our agents authenticate against Bayan and Fasah APIs through licensed broker accounts, extract bill of lading and commercial invoice data, file declarations with the correct HS codes and SAR-denominated values, coordinate physical inspection slots with the customs officer roster, and reconcile against the Fatoora e-invoice trail. For a Jeddah Islamic Port forwarder we cut declaration cycle time from forty minutes manual to under four minutes agent-assisted on standard cargo, with human review held for high-value or restricted-goods lanes. Every declaration carries the cryptographic signature chain ZATCA expects for the audit window.

A typical Jeddah agent deployment — Bayan and Fatoora reconciliation for a Jeddah Islamic Port forwarder, Nusuk-integrated Hajj operator copilot, SAMA-aligned SNB treasury workflow, SABIC Jeddah shift-planning automation — takes sixteen to twenty-four weeks from kickoff to graduated production rollout. Weeks one through four cover PDPL classification, NCA ECC scoping, integration discovery against your SAP, Oracle, or in-house systems, and the Arabic RTL design spike. Weeks five through twelve are agent build, tool wiring, evaluation harness, and Sharia or industry compliance gates. Weeks thirteen through eighteen run shadow mode against historical decisions, then gated human-in-the-loop in production. Weeks nineteen onward graduate autonomy on the low-risk lanes first, with hard guardrails on PDPL-sensitive flows. If your data is messy, add four to six weeks for ingestion and a quality baseline before agent training begins.