AI Agent Development Company in Doha

Arabic-first design and data classification are the two things that shape a Doha agent budget. A scoped agent proof of concept is a six to ten week engagement covering tool-use design, an Azure OpenAI or Fanar baseline agent, and Arabic-first prompt scaffolding tuned for Khaleeji-dialect users. A production banking, energy, or government agent adds Law 13/2016 classification, QCB cybersecurity alignment for banking, an evaluation harness, and Qatar Digital ID integration where citizen identity is in scope. Full agent platforms layer on multi-agent orchestration, Fanar or Jais fine-tuning, and Sharia-screening hooks. Doha sits close to Dubai and slightly above Riyadh for comparable scope because of the QatarEnergy and QIA talent premium and in-country residency operational cost. We give fixed-fee proposals rather than open T and M estimates, with QAR pricing for onshore Qatari entities and USD pricing for QFC-licensed clients.

Law No. 13 of 2016 was the first dedicated personal data protection statute in the GCC, predating UAE, Bahrain, and Saudi Arabia by several years. It is administered by the Compliance and Data Protection Department (CDP) inside the Ministry of Communications and Information Technology, with detailed guidance published from 2021 onward. It imposes consent and purpose limitation obligations, requires breach notification, and treats biometric, health, and religious-belief data as sensitive categories. Our discovery phase produces a Law 13 data flow map, a lawful basis assessment, identifies sensitive categories, and produces a Transfer Impact Assessment for any non-Qatar inference call. Citizen agents and QCB-regulated banking agents are kept fully in-country on Azure Qatar Central or AWS Bahrain me-south-1 only under documented contractual safeguards. We document Article 7 data-subject-rights handling so CDP inspections have a clear answer. QFC-licensed clients additionally receive a QFC Data Protection Regulations framing with QFCRA-aligned controller-processor terms, which differ from the onshore Law 13 regime.

Yes. We build agents for QatarEnergy upstream and midstream operations (HSE incident triage, permit-to-work workflows, vendor onboarding under Tawteen in-country value, North Field expansion coordination across Ras Laffan and Mesaieed) and for Qatar Investment Authority portfolio operations (portfolio company onboarding, deal-pipeline summarisation, regulatory filing automation for Tasdeer-export and Qatar Free Zones Authority workflows). For QatarEnergy we pattern against published HSE methodology, IOGP lifesaving rules, and the Tawteen subcontracting expectations, with agent outputs in Arabic, English, Urdu, Hindi, Tagalog, and Malayalam for the operator workforce. For QIA we build under the AUM-scale governance expectations of a sovereign wealth fund managing USD 475B, with full audit trails, Sharia-screening hooks where portfolio companies require, and a Law 13 data-flow map sized to QIA's compliance team. Agents that touch QatarEnergy or QIA data stay onshore on Azure Qatar Central by default.

Doha's Islamic finance sector is significant — QIB is the largest Islamic bank in Qatar, Masraf Al Rayan and Dukhan Bank cover the rest of the segment, and Sharia compliance is reviewed by board-level scholars who sign off product structures. Our agents that touch Murabaha, Ijara, Musharaka, Sukuk, Wakala, or Takaful flows ship with a Sharia-screening hook that filters non-compliant references (interest-bearing instruments, prohibited industries, non-halal supply chains) before agent output reaches a customer. The screening hook is configured per client Sharia committee guidance, with rule definitions stored in a versioned policy repository so committee reviews can update the rule set without code changes. For Sukuk and capital-markets agents we additionally screen against AAOIFI Sharia Standard 17 and 21 on tradable Sukuk. We do not replace human Sharia review — the agent flags ambiguous cases to a committee-routed inbox with the original prompt, the agent reasoning, and an audit trail.

Yes. The Ministry of Interior's Metrash2 platform covers residency, vehicle, and household services. Hayya is the post-World Cup entry platform that evolved from FIFA accreditation into a general visitor and event-pass identity layer. Sehha is the Ministry of Public Health's citizen health record. Qatar Digital Government integrates these into a single citizen-services umbrella under MoTC and the Government Network. We build agents that integrate against the published Qatar Digital ID standard for citizen authentication, route paperwork through Metrash2 APIs where exposed, and use Hayya for event-pass workflows around Lusail Boulevard, Stadium 974 events, and Qatar Tourism campaigns. Every citizen agent ships with Arabic-first UX, a kill-switch routed to a Ministry-approved human reviewer, a Law 13 lawful-basis statement, and a documented retention schedule that matches the relevant Ministry's records management policy.

Microsoft Azure Qatar Central (Doha) launched in 2022 as the first Azure region in the GCC and is the default in-country option for Law 13/2016 sensitive workloads, citizen-facing agents, QCB-regulated banking agents, and any project where CDP guidance favours onshore residency. AWS me-south-1 in Bahrain and me-central-1 in Riyadh sit roughly 60ms and 80ms away and serve as adjacent options when Azure is not preferred. Google Cloud announced a Doha region that is rolling out for clients with existing GCP estates. For maximum sovereignty we coordinate with Ooredoo's MEEZA Tier IV data centres in Doha, Qatar Datamation Systems, and Qatar Computer Services hosting partnerships, keeping personal data, prompt logs, embeddings, and agent memory inside Qatar. Cross-border inference is acceptable only when a Law 13 Transfer Impact Assessment passes, typically for non-sensitive internal tooling. We document residency in the data processing agreement so CDP, QFCRA, QCB (for banking clients), and internal audit have a clear answer.

A typical Doha agent (QCB-regulated banking onboarding for QNB or Commercial Bank, QatarEnergy HSE triage, QIA portfolio-company filing, Metrash2 citizen workflow) takes fourteen to twenty-two weeks from kickoff to production, assuming the regulatory mapping and Sharia-board review (for Islamic banks) sit inside scope. Weeks 1 to 4 cover Law 13 classification, QCB or QFCRA mapping, agent topology design, and Arabic prompt scaffolding. Weeks 5 to 12 are build, evaluation harness construction, red-team prompt-injection testing, and jailbreak evaluation. Weeks 13 to 18 cover Azure Qatar Central deployment, Qatar Digital ID integration where applicable, Sharia-screening hook configuration where applicable, shadow-mode deployment, and internal audit review. Weeks 19 onward are gradual production rollout with kill-switch monitoring. If you need a multi-agent orchestration platform or Fanar or Jais fine-tuning, add six to eight weeks. We have shipped to this cadence inside Qatari QCB-regulated stacks.

The Qatar Financial Centre (QFC) operates under a common-law framework distinct from the onshore Qatari civil-law regime, with its own Data Protection Regulations (Regulation 6 of 2021), its own dispute-resolution courts, and supervision by the Qatar Financial Centre Regulatory Authority (QFCRA) for licensed firms. QFC-licensed clients (a growing share of Doha fintechs, asset managers, and reinsurance entities) get a parallel framing on our agent projects — controller-processor terms aligned with QFC DPR rather than Law 13/2016, lawful-basis assessments under QFC DPR Article 6, breach notification under QFC DPR Article 22, and a QFCRA-aligned cyber-resilience narrative where the agent touches financial-services workflows. We document both regimes in parallel where a client straddles onshore and QFC entities. Pricing for QFC clients defaults to USD because QFC firms commonly book in USD.