Connect agent governance to the systems you already operate.
BuildMoat’s runtime gateway checks agent actions against each agent’s approved boundaries and can hold or block out-of-scope actions before they execute. Your identity, payments and core systems remain the enforcement points for their own domains. BuildMoat ties them to one governed control and evidence record.
BUILDMOAT CONTROL PLANE
Agent estate
Agents · models · tools
Control estate
Identity · APIs · workflow
Assurance estate
GRC · policy · audit
Integration model: managed, client-scoped connections, not a self-serve marketplace. During architecture discovery, we agree the systems, data, permissions and deployment requirements for each workflow.
Seven system domains. One accountable record.
Start with the evidence needed to govern one material agent workflow. The systems shown are examples to assess, not a promise of out-of-the-box support.
01 · Identity & access
Identity, authority and permissions
Associate activity with user, workload or agent identities, then link roles, approvals and access-review evidence.
02 · Policy, risk & regulation
Obligations mapped to controls
Reference regulatory updates, policies and control objectives alongside owners, review dates and decisions.
03 · Workflow & case management
Approvals, exceptions and remediation
Keep approvals, incidents, attestations and remediation in established case-management workflows. Use Slack and email as escalation channels for out-of-bounds activity. Pause an individual agent without taking the service offline. Restart requires the accountable Senior Manager's recorded rationale.
04 · Documents & evidence
Governed records and artefacts
Reference mandates, policies, approvals, tests and assurance records in repositories your firm already governs.
05 · Agents, models & orchestration
Agent configuration and activity
Record agent and model versions, deployment context, available tools and relevant runtime events. Recording the model and version behind each agent gives visibility of vendor model changes and supports mapping AI dependencies into resilience planning.
06 · Agent tools, APIs & MCP
Tool calls and downstream actions
Trace tool, function and API calls against approved scope, policy checks and action outcomes.
07 · Core business systems
Business and customer outcomes
Connect agent activity to the transaction, customer, case or operational outcome that matters.
Security and deployment boundaries
Each client environment is configured with scoped identities, roles, integration credentials and administrative audit trails. Data minimisation, retention, export and deletion are agreed during design. Encryption is applied in transit and at rest; regional, dedicated or customer-controlled deployment options are assessed against requirements and availability.
Choose the connection pattern for the control requirement
Not every workflow needs a real-time control point. Use the lightest pattern that meets the evidence, control and resilience requirements. BuildMoat’s runtime gateway checks agent actions against approved boundaries and can hold or block them before execution. Identity, payments and core systems remain the enforcement points for their own domains.
Agent telemetry (OpenTelemetry)
Ingests client-scoped traces of agent tool, function and API calls via OpenTelemetry (OTLP) to compare activity with approved boundaries. Works with LangChain and custom or in-house agents.
Event or webhook ingestion
Receive structured activity, approval, configuration-change and exception events.
API and evidence connector
Read or reference approved configuration, permissions and evidence on an agreed schedule or event.
Workflow integration
Link or route approvals, incidents, attestations, remediation and reporting in client tools.
Runtime gateway
Holds or blocks agent actions that fall outside approved boundaries before they execute. Observe mode supports shadow running before enforcement.
Secure batch exchange
Exchange structured assurance evidence where a live connection is not practical.
From architecture discovery to governed operation
Start with one material agent workflow. Map its authority, evidence, data flows, dependencies and deployment constraints, then expand when the evidence model is proven.
Discover
Map the workflow, accountable roles, agent authority, data flows, evidence sources and deployment needs.
Configure
Set up agreed connections, evidence fields, control mappings, workflows and permissions.
Validate in Observe mode
Check signal quality and evidence completeness in Observe mode before switching the gateway to Enforce mode.
Operate and govern
Activate agreed exception workflows, reporting, review cadence and assurance.
See where BuildMoat fits in your architecture.
Bring one agent workflow and the systems it touches. We’ll map control points, evidence sources, permissions and a practical first integration path.
30-minute review · No system access required to start