# Managed AI operation — Genyra

> Managed AI services for deployed systems: an operator, monitoring, version history for models and prompts, evaluation, change control and incident planning.

Canonical page: https://genyra.com/ai/managed-operation

Monitoring, versioning, change control, cost and incident handling for an AI system in use, with a named operator. 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.

## Watch the system, not just the servers.

Operation covers the usual measures of an environment and the ones particular to an AI system: how often answers are sent back by reviewers, how often the system reports that the material holds no answer, which documents are retrieved and which never are. These are reviewed on a schedule with the organisation, and they are the first sign that something has changed.

Managed operation is contracted with Genyra L.L.C-FZ in Dubai, which operates genyra.ai; genyra.com describes the practice. The agreement names the operator and the responsibilities on each side.

## Models and prompts are versioned.

Every model build and every prompt in use has a version, and every logged answer records which versions produced it. A change to either is a release: tested against the organisation’s evaluation set, recorded, and reversible. No model or prompt changes quietly.

## Change control that the organisation can see.

Changes to the model, the prompts, the retrieval index, the permitted documents or the boundary are proposed, reviewed, approved and recorded. The organisation decides who approves each class of change. The record shows what changed, when, by whom and what the evaluation showed.

## Cost and capacity, stated and watched.

A private deployment has a known capacity: the compute it runs on, the volume it can handle and what it costs to run. Usage is measured against that, growth is planned rather than discovered, and the organisation sees the figures before a change in capacity is made.

## Incidents have an owner and a record.

A wrong answer that reached a person, a document indexed that should not have been, a failed release or an outage is handled as an incident: contained, examined, recorded and reported to the organisation with what will change. The audit log and the version history are what make the examination possible.

## Who operates it.

The agreement names the operator. We can operate the system under the terms agreed, operate it jointly while the organisation’s team learns it, or hand it over with the runbooks, version history and records needed to operate it alone. In every case the organisation retains its data, its logs and its evaluation set.

## Related work

- [Private AI deployment](https://genyra.com/ai/private-deployment): Private AI deployment: self-hosted LLMs, retrieval and audit logs on-premise or in a dedicated environment. Residency by design, no training on your data.
- [Custom AI solutions](https://genyra.com/ai/custom-solutions): Custom AI solutions built around a task your people already perform: contract review, claim triage, case summaries and answers from your records, sources cited.
- [Managed infrastructure](https://genyra.com/infrastructure/managed-infrastructure): Managed infrastructure enquiries covering maintenance, monitoring, access, change control, recovery and service responsibilities.

Contact: contact@genyra.com

Genyra LLC and the Dubai business Genyra L.L.C-FZ / Genyra.ai are distinct entities. Project scope and the contracting entity are agreed explicitly.