Product
A workbench built for governance, not just visibility.
Five concepts that distinguish ModelAIr from every diagramming tool you have used. These are not features. They are the model.
01 — Typed Node Schema
Structured objects · Domain-specific properties · Queryable schema
AI system components as structured typed objects
In ModelAIr, every component in your AI system is a typed node — not a generic shape. A language model is not a box labelled 'LLM'. It is a structured object with properties: model family, version, hosting environment, data residency, access controls.
The same principle applies across the entire system. Data stores carry retention and sensitivity properties. Orchestrators carry execution mode and escalation paths. Human checkpoints carry role, authority scope, and response-time requirements.
The schema is the governance. When you place a component on the canvas, you are not drawing — you are declaring a structured record that can be queried, exported, and audited.
02 — Assertion Levels
Signal · Advisory · Authoritative · Governance constraint
Signal. Advisory. Authoritative.
Every AI component in ModelAIr carries an assertion level. This is not a label — it is a governance constraint that defines what the component is actually permitted to do in the system.
Signal: the component produces outputs that are observed but not acted on autonomously. Advisory: the component produces outputs that inform human decisions. Authoritative: the component produces outputs that trigger downstream action without human approval.
The distinction matters legally, operationally, and architecturally. ModelAIr makes it explicit and exportable. The assertion level is part of the governance record from the moment the component is placed.
03 — Authority Boundaries
Autonomous perimeter · Human-in-the-loop · Compliance-ready
Where does autonomous authority end?
Authority boundaries define the perimeter of autonomous AI action within your system. ModelAIr lets architects model this explicitly — drawing a boundary is a first-class design action, not an afterthought.
Within the boundary: AI components may act autonomously. Outside it: a human checkpoint is required before action proceeds. The boundary is visible in the diagram, encoded in the governance record, and exportable to compliance artefacts.
This is the question regulators and risk teams are asking. ModelAIr gives architects the mechanism to answer it with precision rather than inference.
04 — Edge Semantics
Transport · Auth · Data sensitivity · Reliability
Connections that carry typed meaning
In most architecture tools, connections are lines. In ModelAIr, every connection between components is a typed edge carrying structured properties: transport protocol, authentication method, data sensitivity classification, and reliability characteristics.
A connection between a model and a data store is not a line. It carries the protocol (REST, gRPC, message queue), the authentication method (API key, OAuth, mTLS), the classification of data in transit, and the reliability model (sync, async, best-effort, guaranteed).
Edge semantics are part of the governance output. The connection is as much a governed object as the components it connects.
05 — Governance Output Model
Queryable record · Audit-ready · No export step
The diagram is the governance artefact
There is no export step. There is no documentation layer. The design workspace in ModelAIr is the governance record. As architects design, the governance model is built automatically — structured, queryable, and ready for audit.
The output can be queried directly: which components carry authoritative assertion levels? Which data stores handle sensitive data? Which human checkpoints are in the critical path? These are answerable from the model — not from a PDF.
When regulators ask for AI system documentation, ModelAIr gives organisations something they can actually stand behind. Not a diagram. A governed, structured record of how the system is built and what it is permitted to do.
Built for architects under governance pressure.
Join the beta and tell us what you're working with.