APIGQL Governance
Data Governance โ€ข AI Agents โ€ข Runtime Enforcement

Governed AI Runtime for Sensitive Enterprise Data

Classify and tag sensitive data, translate governance intent into enforceable policy, keep humans in the review loop, and constrain AI agents at runtime.

Explore Architecture
Why APIGQL exists

Govern enterprise data before it reaches AI, applications, or automated agents.

APIGQL is not only a federation layer. It connects sensitive-data discovery, field-level tagging, governance policy, human review, drift detection, runtime enforcement, AI-agent controls, and security risk intelligence into one continuous governance lifecycle.

Discoverโ†’ Tagโ†’ Governโ†’ Reviewโ†’ Detect Driftโ†’ Enforceโ†’ Observe / XDRโ†’ Improve
Primary developer story

Continuous Runtime Compliance

APIGQL continuously discovers, tags, governs, reviews, enforces, observes, and re-evaluates sensitive enterprise data and AI activity at runtime.

01

Discover & Classify

Scan structured and unstructured fields for PII, PHI, PCI, compensation, secrets, and organization-specific sensitive attributes.

PIIPHIPCI
02

Tag & Score

Attach field-level sensitivity tags, confidence, source provenance, and risk metadata that downstream policy can reference.

restrictedmaskhigh-risk
03

Generate Policy

Translate governance intent into runtime decisions and obligations such as allow, deny, mask, drop, or transform.

ALLOWMASKDENY
04

Human Review

Route uncertain or high-impact decisions to a reviewer with evidence, explanation, decision history, and audit context.

reviewapproveaudit
05

Constrain AI Agents

Agents retrieve and reason only over policy-approved context, with validation and enforcement applied before output is released.

RAGvalidateenforce
Continuous assurance

Continuous Runtime Compliance: Drift Detection + XDR Risk Intelligence

APIGQL continuously checks whether architecture, human decisions, policy, and runtime behavior remain aligned. Architectural drift, governance drift, and XDR risk turn runtime compliance into measurable scores with explanations and remediation.

Architectural Drift

Reference Architecture vs. Current State

50%

Upload a reference architecture, design document, or approved target-state artifact. APIGQL compares that baseline with the current architecture and highlights divergence.

Upload Design Extract Controls Compare Current State Score Drift Explain
Example finding
Expected: API access routed through approved policy enforcement layer
Observed: one workload bypasses the expected control path
Drift score: 50%
Governance Drift

Approved Classification vs. Human Decisions

72%

Detect when reviewer actions move away from the approved governance baseline. The score is accompanied by evidence and reasoning rather than treated as a black-box alert.

Baseline Tag Reviewer Change Policy Impact Risk Score Explain
Example finding
Existing classification: Clear
Reviewer change: Sensitive
Reasoning: downstream masking and access policy will materially change
Governance drift: 72%
XDR Risk Intelligence

Security Logs โ†’ Risk โ†’ Remediation

84

Ingest security and runtime logs, correlate suspicious behavior, assign a risk score, and produce evidence-backed remediation guidance.

Ingest Logs Correlate Score Risk Explain Remediate
Example finding
Multiple failed privilege checks + abnormal data access pattern
XDR risk score: 84 / 100
Suggested action: isolate identity, review access token, tighten policy, inspect related traces
Runtime observability

Jaeger + OpenTelemetry make governance decisions traceable.

Policy decisions, agent actions, enforcement outcomes, and runtime events can be correlated with distributed traces, giving teams evidence for why a request was allowed, masked, denied, escalated, or remediated.

Requestโ†’ Agent / Orchestratorโ†’ PDP Decisionโ†’ PEP Enforcementโ†’ OTel Spanโ†’ Jaeger Trace

Runtime Architecture โ€” Where Governance Is Enforced

Follow the runtime path below. Select any layer to inspect how governance, policy, enforcement, and observability connect.

Governance Workspace Classification โ€ข Review โ€ข Evidence
โ†’
Policy Control Plane Governance Intent โ†’ Runtime Rules
โ†’
Runtime Enforcement Fabric Zero Trust โ€ข Policy โ€ข Protection
AI Agent Orchestration MCP Orchestration
โ†’
Router / PEP Runtime Enforcement
โ†’
Runtime PDP Decisions
โ†’
Data Plane Federation
โ†’
Telemetry Loop Learning
Architecture explorer
Select a runtime layer
Choose any layer above to see its governance role, runtime flow, and enforcement responsibilities.

Runtime Security & XDR Enforcement

Zero-trust enforcement across APIs, data, and AI pipelines.

Zero Trust Enforcement
Continuous Runtime Compliance
Threat Detection
Continuous runtime compliance

Governed AI Execution Loop

A unified runtime pipeline that grounds, governs, validates, and enforces every AI and data interaction in real time.

Snapshot Ingestion AI Classification Real-Time RAG LLM Inference Agent Validation Policy Enforcement

This same execution loop powers GenAI, cybersecurity enforcement, compliance automation, and federated data access.

Select an industry to see governed AI in action.
MCP Orchestration

AI Agent Governance Engine

Specialized governance agents coordinate classification, retrieval, validation, and policy workflows, with MCP providing the interoperability layer for agent/tool orchestration.

Data Classification Structured & Unstructured
Policy Synthesis Governance โ†’ Runtime Rules
Snapshot-Grounded GenAI Hallucination-Free AI
Output Validation Policy & Fact Checks
MCP orchestration

MCP Context + Tool Orchestration

MCP standardizes how governance agents access approved context, tools, evidence, and runtime controls. It works with the existing orchestrator rather than replacing it: the orchestrator coordinates agent execution, while MCP provides a consistent interface for governed resources and tool calls.

1. Governed Context Expose approved tags, policy metadata, evidence, and runtime state to agents through controlled context resources.
2. Governed Tools Classification, policy lookup, validation, evidence retrieval, remediation, and enforcement are exposed as policy-controlled tools.
3. Agent Orchestration The existing orchestrator coordinates agent workflows while MCP provides standardized context and tool interoperability.
4. Audit + Observability Tool calls, policy decisions, reviewer actions, and enforcement outcomes are correlated with OpenTelemetry/Jaeger traces for end-to-end visibility.

Human-in-the-Loop + Explainable Governance

When controls trigger, teams can inspect decisions, ask โ€œwhy,โ€ and approve safe exceptions โ€” without disabling enforcement.

Ask โ€œWhy?โ€ Explanations Policy โ€ข Evidence โ€ข Next Steps
Human-in-the-Loop Review Approve โ€ข Escalate โ€ข Record
AI Agent Architecture + MCP Orchestration Governance Agents โ€ข Orchestration

Policy-Governed Generative AI

Snapshot Classify RAG LLM MCP Validate Policy Secure Output