In short

  • Inside your boundary: the model, the platform, the indexes and the logs run in your data centre, in a private cloud in your country, or on a site with no internet connection.
  • You hold the keys: Orchestra uses your own key management, and NoorAI never holds your master keys.
  • We do not see your content: routine maintenance is done without access to content.
  • Permissions as they are: an answer only uses documents the person asking could already open.
  • Every answer has a source: every answer cites where it came from, and every question, answer and action is recorded.
  • You decide what an assistant may do: sensitive actions need a person's approval, and any assistant can be stopped at once.

Where it runs, and where the data stays

The same release runs in your data centre, in a cloud region in your country, in your own tenancy on a public cloud, or on a site fully cut off from the internet. Documents, prompts, answers, logs and keys do not leave that boundary. Calls to an outside model are off by default; only you can switch them on, and only for content you choose. What air-gapped really means.

Encryption keys

Whoever holds the encryption keys holds the data. So Orchestra uses your own key management, and NoorAI does not hold the master keys. If you revoke a key, the data encrypted under it becomes unreadable.

NoorAI's access

  • Maintenance without content: the part of the system that handles configuration is kept apart from the part that handles your documents, so the people who maintain Orchestra never see what your staff ask.
  • Emergency access: off by default, needs your approval, is limited in time and is recorded.
  • Updates: updates and settings arrive as signed packages. On an offline site your own team imports each update, and it is applied when you decide.

Access rights

Each document's permissions come over from the system that holds it, and the assistant searches only what the person asking may open, so anything else never reaches the model. When the assistant carries out a task, it acts with the permissions of the person it serves, no more. In a group of companies, each company has its own space, and sharing across companies is a decision both sides make. The details are in an AI assistant should only know what you know.

Assistants and actions

No assistant gets full authority on day one. It starts by answering questions, then drafts work for a person to send, then acts after a named approver says yes, and acts alone within set limits only once the results show it is ready. Any assistant can be stopped at once. Text inside a document or an email is read as information; it cannot give the assistant new tools or wider access.

Audit trail

Every answer cites the passages it used, and the reader can open the original document. Every question, answer and action is recorded in a log that cannot be altered, so an auditor can tell later what the system was asked, what it answered and who approved each action. Five layers, with a security control at each one.

Quality before launch

Before anyone uses it, Orchestra is tested on real questions from your own documents, agreed with your team, including dialect and Arabic mixed with English. Nothing goes live if it fails that test, and every update goes through the same test. How we evaluate before launch.

What you build stays yours

Your data, search indexes, assistant definitions and any model tuning made for you belong to you, and they export in open formats.

The hosted option

Everything above describes running inside your boundary. With the hosted option, Orchestra runs on NoorAI's infrastructure, in a hosting location agreed with you in the contract, and the data is processed only there. So we recommend it for work whose data may leave your network, and running it on your premises for everything else.

Data protection

Keeping data and keys in the country helps with data protection laws, such as Egypt's personal data protection law and Saudi Arabia's PDPL, and with sector rules on outsourcing. Every contract comes with data processing terms. Your compliance team owns the final assessment; we provide the evidence. The rules, country by country.

How to run a security review with us

  1. A call with an engineer: we answer your security team's first questions.
  2. A non-disclosure agreement: then we send the technical proposal and the architecture description, and answer your security questionnaire.
  3. A pilot: it runs inside your environment, and your team checks for itself what this page says.

Book a 30-minute call, or write to contact@nooraisolutions.com.

Frequently asked questions

Does any data leave our network?

No, when it runs on your premises. Documents, prompts, answers, logs and keys stay inside your boundary, and calls to any outside model stay off unless you switch them on.

Does Orchestra need an internet connection to work?

No. It runs on a fully offline site, and your team imports the updates itself.

Can NoorAI staff see our content?

No. Routine maintenance is done without access to content; emergency access is off by default, needs your approval, is limited in time and is recorded.

Is our data used to train the model?

No, not without your written agreement. Any model tuning made for you belongs to you.