Skip to content
nuhaa.ai

How nuhaa.ai works

Connect. Understand. Ask. Verify.

What sits between an enterprise question and an answer somebody can act on, described without the jargon and without skipping the parts that matter to a security reviewer.

The four stages

Four movements, and only the last one is visible.

  1. Connect

    Trusted sources are brought into one governed layer: documents, policies, reports, databases and business systems. Each source keeps the access rules it arrived with, and connecting one never widens who can see it.

  2. Understand

    nuhaa.ai learns how your organization is structured, what your terms mean, and which figures your teams actually use. Your house terminology is taught once and applied everywhere afterwards.

  3. Ask

    A question in Arabic or English is answered from the material the asker is entitled to reach. Documents and data are consulted together when the question needs both.

  4. Verify

    The answer arrives with its sources, and administrators can review what was asked and what was returned. An answer nobody can check is not an enterprise answer.

The shape of it

Your sources stay where they are and keep doing what they do. nuhaa.ai reads them, and the three products are three ways of asking the same governed layer a question.

Sources are connected during implementation, with your approval, one at a time.

Documents
Contracts, reports, manuals, presentations and scanned files in Arabic and English.
Policies
Procedures, standards, delegation of authority and the rules people are asked to follow.
Data
Governed databases and warehouses, queried read only and answered in business language.
Reports
Periodic packs and dashboards, read for what changed rather than re-rendered.
Business systems
The operational platforms that hold your transactions, records and workflow state.
Knowledge repositories
Shared drives, portals and libraries where institutional memory accumulates.

Showing the work

nuhaa.ai shows the steps it took while it takes them: the sources it chose, the query it wrote, the passages it read. That is partly a trust device and partly a practical one. An analyst who can see the query can correct the assumption behind it in seconds.

  • The reasoning is visible while the answer is being produced.
  • Citations are attached to the answer, not offered as an afterthought.
  • Nothing is executed on your systems as a side effect of a question.

The controls that run on every question

Four things nuhaa.ai does whether or not you ask.

  • Isolate

    Each organization is a separate tenant. Every query that touches organizational data is bound to that tenant before it runs.

  • Authorize

    The asker’s permissions decide the material available to answer with, at the moment of asking rather than at the moment of indexing.

  • Constrain

    Generated database queries are read-only. Text from a document is treated as information, never as an instruction to the system.

  • Record

    The question, the sources and the response are written to an audit trail that administrators can review.

What happens to your content

The part procurement reads twice.

  • Your content is not used to train models that any other customer benefits from.
  • The models that answer your questions run on infrastructure inside the Kingdom.
  • Your content is not sent to a third party model provider.
  • Each organization’s data is isolated from every other organization’s data.
  • On-premise deployment is available where residency requires the content to stay inside your own perimeter.

A working platform, your documents or a governed sample of your data, and the questions you actually need answered.