AI that works inside your boundary.
Custom AI built around one workflow, run where the data already lives, reviewed by people and recorded for audit. Custom AI engagements are contracted with Genyra L.L.C-FZ, the separate Dubai company that operates genyra.ai. Genyra.com describes the practice; the agreement names the company doing the work.
Start from the workflow, keep the model inside the boundary, operate it with the same discipline as any other system.
Custom AI engagements are contracted with Genyra L.L.C-FZ in Dubai, which operates genyra.ai. This site describes the practice; nothing here is a product offer.
- Document store matter files · scans · PDFs
- Retrieval index this organisation only
- Model runtime build 2026.10-03 · no training
- Audit log append-only · kept by the client
Question · A. Reyes · 11:32
Which clauses limit assignment?
- [1] MSA-2041.pdf · clause 14.2 Neither party may assign this agreement without the prior written consent of the other.
- [2] Schedule-3.pdf · clause 3.5 Consent is not required for an assignment to an affiliate, provided the assignor remains liable.
- [3] Amendment-2.pdf · clause 2.1 Clause 14.2 applies to any assignment arising from a change of control.
Three clauses limit assignment. The agreement may not be assigned without the other party’s written consent [1]; an assignment to an affiliate needs no consent while the assignor remains liable [2]; and the consent requirement applies to an assignment arising from a change of control [3].
- [1] MSA-2041.pdf · clause 14.2
- [2] Schedule-3.pdf · clause 3.5
- [3] Amendment-2.pdf · clause 2.1
Limits. Drawn only from the three documents above. Correspondence and any later amendment outside the matter file were not checked. Whether a change of control has occurred is for the reviewer.
| No. | At | Who | Record |
|---|---|---|---|
| 0415 | 2026-10-14 11:32:04 | A. Reyes | question · M-2041 |
| 0416 | 2026-10-14 11:32:05 | system | retrieved 3 · MSA-2041, SCH-3, AMD-2 |
| 0417 | 2026-10-14 11:32:09 | system | draft · model 2026.10-03 |
| 0418 | 2026-10-14 11:40:51 | A. Reyes | approved · docs MSA-2041, SCH-3, AMD-2 · model 2026.10-03 |
Which decision should the model inform, and who signs it off?
The work may cross more than one discipline. Start with the task, then follow its dependencies.
Custom AI solutions
AI systems designed from a workflow the organisation already runs, grounded in its own material, with people in the decision and a record of every answer. Custom AI engagements are contracted with Genyra L.L.C-FZ, the separate Dubai company that operates genyra.ai. Genyra.com describes the practice; the agreement names the company doing the work.
One practice. One contracting entity.
Genyra LLC is a Delaware company; Genyra L.L.C-FZ is a separate company in Dubai, United Arab Emirates, and operates genyra.ai. Custom AI work described on this site is contracted with Genyra L.L.C-FZ. The agreement for an engagement states the contracting entity, the scope, the access granted and where processing takes place, before any material is shared.
Start from the workflow, not the model.
A useful system begins with a task someone already performs: reviewing a contract, triaging a claim, preparing a case summary, answering a question from the organisation’s own records. We write down the inputs, the decision, who makes it and what evidence they need. The model is chosen to serve that, and only that.
Run it where the data lives.
Models run inside the client’s environment or in a dedicated one, with the document store, retrieval index, model runtime and audit log inside one boundary. Nothing is used to train a model. Residency, access and logging are decided and written down before the first prompt is sent.
People decide. The record proves it.
Drafts and answers cite the documents they came from. A named reviewer approves or sends back. Every answer, its sources, the model version and the reviewer’s decision are recorded, so an auditor, a regulator or a colleague can see what the system did and why.
Operated, versioned, under change control.
A deployed system has an operator, monitoring, a version history for models and prompts, a change process and a plan for incidents and cost. We can operate it, train the organisation’s own team to, or hand it over with the records needed to do so.
- Custom solutions
- Private deployment
- Managed operation
Bring the workflow and its constraints.
Describe the task, the people who perform it, the documents involved and the rules on where data may be processed. We will discuss what can be automated, what must stay with a person, and the access an engagement would need. Do not send client records or confidential material in the first message.
Questions we are asked.
Short answers in the same terms as the page. Anything specific to your systems is agreed by enquiry.
- Which company contracts custom AI work?
- Genyra L.L.C-FZ in Dubai, a separate company that operates genyra.ai. The agreement for an engagement names the contracting entity and the governing terms explicitly.
- Is our data used to train models?
- No. Documents, questions and answers are used to retrieve and to answer, and for your own evaluation. They are not used to train or fine-tune a model unless you ask for that in writing.
- Does the system make decisions on its own?
- People decide. Drafts and answers cite the documents they came from, a named reviewer approves or sends back, and each decision is recorded with the model version.
- Which models do you use?
- The model is chosen for the task, the data rules and the environment, and is named in the design together with its version. Models can run entirely inside your own environment.
Discuss a custom AI engagement
From an unanswered question
to an engineered possibility.