Cross-cutting · Enabler layer01 / 05

The AI layer
for your OT environment.

Use AX-Office.ai within your aXite solution to analyse operational data on your own infrastructure. The scope depends on the deployment, with access and outputs governed by the customer.

AI within your solution02 / 05

AI on your infrastructure.

AX-Office.ai provides an AI layer within aXite solutions. You run it on your own infrastructure and govern access, analysis and outputs within your environment.

We define the tasks and integration for each deployment. The applications are set out below.

We benchmark our own models.

Note: AX-Office.ai is not sold separately. We supply it as part of an aXite solution, within the agreed deployment scope.

AX-Office.ai on-premises AI module

AX-Office.ai · on-premises AI module

The non-negotiable

Nothingleavestheenvironment.

Not the events. Not the analysis. Not the model. Self-hosted, air-gap compatible, governed by the customer.

Architecture principles03 / 05

Four principles. Non-negotiable.

The architecture is defined by four constraints, set at design time. Each is demonstrable, not aspirational.

  1. 01 /No data leakage

    Inputs are never stored externally, transmitted off-premises, or reused. Verifiable, not aspirational.

  2. 02 /No external training

    Operational knowledge and sensitive data are never used to train or refine outside models.

  3. 03 /Isolated by design

    Runs fully inside the customer environment. No cloud. No external APIs. The same air-gap discipline as OT.

  4. 04 /Governed by the customer

    Access, actions, and outputs follow the existing roles, authorisations, and governance model.

Regulatory position05 / 05

Continuous monitoring, inside the environment.

Article 21 of NIS2 requires appropriate and proportionate cybersecurity risk-management measures.

Local analysis may support relevant technical controls; applicable obligations, evidence and responsibilities are assessed for the organisation and deployment.

  • Self-hosted on customer hardware
  • No external API calls
  • No telemetry leaving the environment
  • Air-gap compatible by design
  • Governed by the customer access model