Skip to content
Capaintel

Architecture

A governed intelligence layer on top of the systems you already run.

Capaintel doesn't replace your ERP, MES or QMS. It connects to them, builds shared context, and lets people and agents act on that context under the rules you set.

  1. 01

    Sources

    ERP · MES · QMS · documents · machines

  2. 02

    Data Hub

    Connect and normalize

  3. 03

    Context Engine

    Assemble what matters

  4. 04

    AI Operators

    Investigate and prepare

  5. 05

    Manufacturing OS

    Where teams work

  6. 06

    Decisions & Actions

    Approved and logged

Six stages show how data moves from source systems to an approved action. They are not the modules: the platform's eight modules are described on the Platform page.

A-01Layers

Five layers, one governance plane.

Each layer has a single job. Governance — identity, permissions, approvals, audit and cost — spans all of them.

  1. L5

    Experience

    Manufacturing OS · APIs

    Role-specific workspaces for plant, quality and planning teams, plus APIs for embedding Capaintel in existing tools.

  2. L4

    Agents

    AI Operator

    Task-scoped agents with an explicit toolset. Each tool call is checked against policy before it runs.

  3. L3

    Context

    Context Engine

    Retrieval over records, documents, events and the entity graph, filtered by the requester's permissions, producing a context pack per task.

  4. L2

    Knowledge

    Document Intelligence · entity model

    Documents are parsed, classified and linked to a shared model of parts, assets, lines, suppliers and events.

  5. L1

    Data

    Data Hub

    Pluggable connectors ingest and normalize source data, keeping lineage back to the system of record.

Governance · Observability & Governance module

A-02Context Engine

Context packs, not database dumps.

Agents don't get blanket access to your data. For each task the Context Engine retrieves the relevant records, documents, history and relationships, applies the requester's permissions, and passes a cited context pack to the agent.

  • Data Hub records
  • Documents
  • Events & history
  • Entity relationships

Context Engine

Assembles what this task needs — and only what the requester may see.

Context pack · per task

  • Facts
  • Relationships
  • Documents
  • History
  • Permissions

Handed to the agent or person doing the work, with sources attached.

Data Hub records, documents, events and entity relationships flow into the Context Engine, which produces a task-specific context pack of facts, relationships, documents, history and permissions.

A-03Agent action lifecycle

Every agent action follows the same governed path.

Policies decide which actions run automatically and which pause for a person. Every step is written to the audit log with the evidence used.

  1. 01

    Request

  2. 02

    Context pack

  3. 03

    Plan

  4. 04

    Policy check

  5. 05

    Approval

    When policy requires

  6. 06

    Execute

  7. 07

    Audit log

A-04Connectors & deployment

Pluggable connectors. Your choice of models and hosting.

Connectors are added per source system. Inference is model-agnostic, so you can choose models that fit your policies and costs, and private deployment is available when data must stay in your environment.

Source categories

  • ERP
  • MES
  • Quality management (QMS)
  • Maintenance (CMMS / EAM)
  • PLM & engineering
  • Historians & IoT
  • Document stores
  • Email & collaboration

Specific system support is confirmed per engagement — ask us about yours.

A-05Enterprise readiness

Built to fit how manufacturers run IT.

Capaintel connects to the systems you already have and follows the access and approval rules you set.

Review Security
  • API-first

    Every capability is available through documented APIs.

  • Role-based access

    People and agents see only what their role allows.

  • Auditability

    A complete record of activity, approvals and data access.

  • Private deployment options

    Run in your own cloud environment when required.

  • Model-agnostic inference

    Choose the AI models that fit your policies and costs.

  • Pluggable data connectors

    Connect the systems you have rather than replacing them.

  • Human approval gates

    Configurable checkpoints before agents change anything.

Want the technical walkthrough? Talk to our team.

Book a Demo