Skip to content

Company brain and AI knowledge base in Dubai and the UAE

In short. Aiwah Labs builds company brains for businesses in Dubai, Abu Dhabi and across the UAE: internal AI knowledge bases that answer staff questions from your documents in Arabic and English and show the source. The first use case is live within a week, and we build on it. Typical setup is from about AED 9,000.

Company brain implementation overviewAll services in Dubai

Container operations at a port
Starting price
AED 9,000
Typical one-time setup, in UAE dirhams. No monthly maintenance fee.
Timeline
First use case in 1 week
We build on top of it, one use case at a time.
Languages
Arabic, English
We test retrieval across both languages on your own documents.
Office
Dubai, UAE
Serves businesses across Dubai, Abu Dhabi and the wider UAE.
You own
Code and data
Plus the prompts and the accounts set up for you.

What is a company brain?

A company brain is an internal system that answers staff questions from your own documents and records. It shows the source, and it refuses what the asker may not see. It prepares answers. A person still approves anything that changes a record.

Uploading a folder to a public chatbot makes a private copy outside your control, under that product’s retention rules. A company brain runs inside your operation, with permissions, a source for every answer, and a store you own. For the wider controlled workflow, see knowledge and back office.

  1. Your documents, drives and tools

    Only the sources named in the engagement are connected.

  2. Index with permissions

    Access follows the source system where it exposes a list.

  3. Answer with its source

    The passage used is shown. A weak match is reported as weak.

  4. Person approves changes

    Nothing that changes a record runs without a person.

How a question moves through a company brain, and where a person approves.

Where it helps in Dubai.

Scenarios the setup is built around. Each one ends in a record or a person, not a dead end.

An SOP and policy brain for a free-zone company

Staff ask how to raise a purchase request or request leave. The answer comes from the current SOP, shows the passage, and refuses a folder the asker cannot open.

Onboarding for new starters

New joiners ask the questions they would put to a colleague. The answers come from the HR handbook and procedures, in Arabic or English.

Finding what was agreed with a client

Someone needs the terms of a past contract. The brain finds the clause and shows the page, within what that person may open.

What we build.

We connect the sources your team uses today, as long as each one has an interface. We agree the list before we build.

Sources

Google Drive, SharePoint, OneDrive, Confluence, Notion, email exports, or the internal database your team treats as the record. The engagement names the list, and it stays the list.

Retrieval

Each answer cites the passage it used. When the source is missing or the match is weak, the system says so.

Permissions

Where the source system exposes an access list, the answer follows it. Where it does not, we scope a narrower source instead of guessing.

Where it runs

The index sits in your own cloud account, in a region you choose. Staff ask in Slack, Teams or a simple web page. The models that draft the answer can be swapped later. The files stay yours.

Staff question, Arabic and English
Team member:

أين أجد نموذج طلب الإجازة؟

In English: Where can I find the leave request form?

Company brain

ستجده في مجلد الموارد البشرية، ضمن سياسة الإجازات.

In English: You will find it in the HR folder, under the Leave Policy.

Team member:

Who approves a purchase request over the limit?

Company brain

The finance director approves it first, then the purchasing officer places the order. This is in section 3 of the Procurement SOP.

Source shown

Procurement SOP, section 3. Answered within this person’s folder access.

Answers follow the folder access each person already has.

Illustrative example. Not a real conversation.

From one real case to a live path.

First use case in 1 week. We build on top of it, one use case at a time.

  1. Days 1–2Audit

    Audit the questions staff ask

    We list the repeated questions, the folders they should come from, and who may see each folder.

  2. Days 2–3Design, before build

    Separate permission from search

    We trace who can open each source today, so the brain never becomes a side door around it.

  3. Days 3–5Build

    Index the agreed sources

    Only the named sources get connected. Every answer keeps a link back to its passage.

  4. Days 5–6Test, before anyone relies on it

    Score a sample of answers

    Real questions get scored for the right source, a correct refusal and the right permission. That sample is the accuracy check.

  5. End of week 1First use case

    Put it where the work happens

    Staff ask inside the tool they already open. The first use case is live within a week.

  6. Then, use case by use caseAfter the first use case

    Build on top of it

    The next use case goes on top of the first, one at a time, with the same source for every answer and the same permissions.

Talk to sales.

Prices are in UAE dirhams and exclude taxes. They are one-time setup, not a subscription.

Typically from aboutAED 9,000One-time setup

No monthly maintenance fee. No vendor lock-in. The client owns the code and the data.

Talk to sales
  • The sources agreed in the engagement, such as files, a drive, or a tool with an interface
  • Answers that show the source they used
  • Permissions that follow the source system where that system exposes them
  • A person reviews any step that would change a record
  • You own the code and the data. Model providers keep their own service terms.

Usage, such as LLM tokens, is passed through at provider cost. We add no markup.

Bring one call, thread or workflow. We scope from there.

Book a call

What you own at the end.

You own

  • The code
  • The index and the data store
  • The prompts and the question sets used to check answers
  • The cloud and model accounts, which can sit in your name
  • The build itself, with no vendor lock-in

Controls that stay in place

  • Answers show their source. A weak match is reported as a weak match.
  • Permissions follow the source system where it exposes them.
  • Nothing that changes a record runs without a person.
  • No monthly maintenance fee and no vendor lock-in. You own the code and the data. Model providers keep their own terms.

Integrations

Every source in. One place to ask.

The brain reads the places your knowledge already lives, keeps each file’s permissions, and answers inside the tool your staff already open.

Documents and drives

  • Google Drive
  • SharePoint
  • OneDrive
  • Dropbox
  • Box
  • Confluence
  • Notion

Mail and sheets

  • Gmail
  • Outlook
  • Google Sheets
  • Excel
  • Airtable

Records and tickets

  • Salesforce
  • HubSpot
  • Zendesk
  • Jira
  • Asana
  • ClickUp

Databases

  • PostgreSQL
  • MySQL
  • MongoDB
  • Snowflake
Company brainOne index that keeps who may see what

Staff ask in

  • Slack
  • Microsoft Teams
  • Google Chat
Examples, not the full list. Logos do not imply a partnership with their makers.

Not on the list? We still connect it.

If your system lets data in or out, we connect to it. If it does not, we find a workaround, and we tell you how dependable that route is before we build. We also connect scanned PDFs, old file shares, intranet pages, email archives and any internal system with an export.

  1. API or webhook

    The clean route. Most modern tools have one, and many older ones do too.

  2. Database or export

    No API? We read the database, or a scheduled CSV or SFTP export.

  3. Email and shared folders

    We pick up the reports, invoices and attachments your system already sends.

  4. Screen automation

    For a portal with no other way in, a bot works the screen the way your team does, with every step logged.

How we approach integrations →

What changes in Dubai.

Serves businesses across Dubai, Abu Dhabi and the wider UAE.

A company in Dubai, mainland or free zone, tends to keep its rules in several places: an HR handbook in Arabic and English, a procurement SOP on a shared drive, an approval matrix in somebody’s inbox. A company brain gives staff one place to ask. The answer comes from the current document, shows the passage, and refuses a question about a folder the asker cannot open. We start with an audit of the questions your staff ask, in Arabic and in English, and we test retrieval across both languages on your own documents.

Data protection decides where the index sits. The UAE’s Personal Data Protection Law, Federal Decree-Law 45 of 2021, applies to electronic processing of personal data inside or outside the UAE, generally requires consent, and sets conditions for sending data abroad. Staff files hold exactly that kind of data: ID copies, contracts, salary letters. So the design starts with a short list of what the brain may read, an index that sits in a UAE region of your cloud account where your provider offers one, and a record of which model provider sees each question. A question sent to a model hosted abroad counts as a transfer, and the build treats it as one. Ask your counsel to check the PDPL’s executive regulations as they stand when you start.

A company registered in the Dubai International Financial Centre has a second law to read. DIFC Law No. 5 of 2020 is the centre’s own data protection law, so the audit starts by naming which regime covers each source the brain will index.

Sources behind the local points

  1. The UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) came into force on 2 January 2022. It applies to electronic processing of personal data inside or outside the UAE, generally requires consent, and sets requirements for cross-border transfers.

    UAE Government portal, data protection laws (updated 4 December 2025)
  2. The Dubai International Financial Centre has its own data protection law, DIFC Law No. 5 of 2020, listed by the UAE Government alongside the federal Personal Data Protection Law.

    UAE Government portal, data protection laws (updated 4 December 2025)

Straight answers.

Can a company brain keep our data inside the UAE?Local

Yes, where your cloud provider offers a UAE region. We place the index and the store there and name every model provider that sees a question. A provider hosted abroad counts as a transfer under the PDPL, which we design for.

Does it work with Arabic and English documents?Local

Yes. We test retrieval across both languages in the audit, so a question in Arabic can find an English policy and the reverse. We report the results on a sample of your real questions before you rely on it.

How much does a company brain cost in Dubai?Local

Setup is typically from about AED 9,000, one-time, scoped after the audit. There is no monthly maintenance fee. Model usage is billed at provider cost, with no markup from us.

How long does it take?

The first use case is live within a week, and we build on top of it, one use case at a time. We do not quote a total timeline. Which use case comes next, and how many sources and permission rules it involves, is agreed as we go.

Will staff see documents they should not?

No. Where the source system exposes an access list, the answer follows it. Where it does not, we scope a narrower source, so the brain never becomes a side door.

Bring one workflow.

Tell us the call, the thread or the record. Every setup on this page starts with a call.

Book a call