Run in your own cloud tenancy.
Private cloud or VPCAgent Hive runs inside your private network, connected to your systems through approved paths.
- Private tenancy and network rules
- Model access set by agent role
- One place for traces and evaluation
The same research, applied to each domain’s evidence, rules and owners.
A reference workflow: connect technical evidence, coordinate specialist agents and keep engineer validation on the whole decision path. Shown on two demanding workflows: FE analysis review and non-conformance disposition.
The questionA machined bracket failed incoming inspection. Can we use it as is, rework it or scrap it, and what does the analysis say?
Part, supplier, quality and configuration evidence for this non-conformance.
Prior dispositions, simulation, tests and reports on the same feature.
The solver stays the validation authority. Agents set up the check; engineers run and review it.
Use as is, rework or scrap, with sources and reasoning attached.
After approval, a governed update goes back to the source workflow.
Use as is is not supported: margin falls to 1.4 against a required 1.5. Rework to blend the edge restores 1.7, as on two earlier NCs.
Solver runs and engineering checks happen under engineer control, and their results are reviewed before use.
An authorised engineer approves, revises or escalates. Agents recommend; they do not decide.
Bring source evidence together, keep its authority, and give every agent and reviewer the same technical context.
Agent Hive
Agent HiveNon-conformances, inspection results and supplier records.
Drawings, specifications, models and analysis results.
Prior dispositions, reviews and change records.
FE review and non-conformance disposition show how engineering evidence and enterprise workflow meet without blurring authority.
Models, assumptions and result fields are available.
Regions that need attention are connected to context.
Constraints and design implications stay visible.
Recommendation, report and next action are approved.
Tables, procedures and KPIs across the systems engineers already use, with lineage. Agents read it; engineers can browse it.
Dimensions, tolerances and notes are read off drawings and certificates, then linked to the part, the feature and the requirement they belong to.
Provenance trail. Provenance of “on-time rate = 0.874”: on-time rate = 0.874 ← query run ← metric definition ← delivery policy §4 (read right to left: the fact was derived from each step in turn). Every step: entity “on-time rate = 0.874” (the fact in the answer); wasGeneratedBy query run. activity “query run” (2026-10-21 · 09:14); wasAssociatedWith analyst agent, used orders dataset, used metric definition. agent “analyst agent” (ran the query). entity “orders dataset” (snapshot 2026-10-20); wasDerivedFrom ERP export. entity “metric definition” (v3 of 3), versions v1 first draft; v2 excludes cancelled lines; v3 late = after promised date; wasDerivedFrom delivery policy §4, wasAttributedTo data steward. entity “ERP export” (nightly load). entity “delivery policy §4” (source document). agent “data steward” (approved v3).
Criteria reflect engineering evidence, known cases, reviewer needs and the limits of each specialist tool.
| Question | v1 | v2 | v3 |
|---|---|---|---|
| Which drawing revision applies to this NC?Evidence coverage | ✓ | ✓ | ✓ |
| Has this feature been dispositioned before?Evidence coverage | ~ | ✓ | ✓ |
| Does the measured wall thickness keep margin?Analysis | ✗ | ~ | ✓ |
| Which load case governs the bracket?Analysis | ✗ | ✓ | ✓ |
| Open every source behind the recommendationTraceability | ✓ | ✗ | ✓ |
| Rework or scrap: what changes downstream?Known case | ~ | ~ | ✗ |
| Who must approve a use-as-is on a safety part?Approval | ✓ | ✓ | ✓ |
Configuration, revision, requirements, analysis, tests and history.
Every recommendation opens the exact evidence used.
Reviewed historical cases and agreed acceptance criteria.
Agents recommend. Authorised engineers approve.
Private cloud, VPC and on-premises patterns keep the same context, permissions, approval gates and audit record.
Agent Hive runs inside your private network, connected to your systems through approved paths.
The platform, the models and every trace stay on infrastructure you operate.
| Runs in | QpiAI managed environment | A dedicated network in your cloud | Your data centre (Docker / Compose) | An isolated network |
|---|---|---|---|---|
| Operated by | QpiAI | Agreed per engagement | Your team | Your team |
| Tenancy | Multi-tenant, isolated | Single-tenant | Single-tenant | Single-tenant |
| Data at rest | Managed environment | Your cloud and region | Your network | Inside the perimeter |
| Models | Managed models | Approved endpoints | Local, or via a policy gateway | Local models only |
| Outbound | Operated by QpiAI | Private connections | One controlled egress path (hybrid) | None |
| Identity | Your identity rules | Enterprise identity | SSO and RBAC | Local SSO and RBAC |
| Updates | Rolled out by QpiAI | Agreed per engagement | New image version, pulled | Signed offline packages |
| Audit | Audit history | Audit history | Local audit history | Local audit history |
Air-gapped Graph, agents and models run inside an isolated network; updates arrive as signed offline packages.