Product

How Gateplex Works

Gateplex sits between your AI agents and the systems they act on. Every action is intercepted, evaluated against your rules, and assigned a verdict before it reaches the target. The client cannot override the server verdict.

intercept lifecycle · sequence pipelineactive evaluation
01 / Step 1

Agent Execution Surface

Agent sends action

  • POST /tools/wire_transfer
  • agent_id: "treasury-ops-01"
  • amount: "$48,200 USD"
  • model: "gpt-4o"
intercept
02 / Step 2

Gateplex Inline Gateway

Gateplex evaluates

  • deterministic rule match
  • no model inference
  • server-side evaluation
  • verdict written to audit chain
forward
03 / Step 3

Target Production System

Verdict returned before execution

  • core banking · CRM · SQL
  • reached only on ALLOW
  • blocked calls never egress
  • held calls await a reviewer
traffic is evaluated before it ever reaches a production system

Observability

Complete Observability

Every agent action is captured in real time with full context. Each intercept record stores the agent identity, model name, input payload, output, verdict, triggered rule name, transaction amount if detected, PII types detected if any, and a server-measured timestamp. Records are immutable from the moment of creation.

The Live Feed shows intercepts as they arrive across all agents and projects in your organisation. Filter by verdict, agent, date range, or rule. Every record is queryable and exportable.

Nothing your agents do happens without a complete, verifiable record behind it.

live telemetry records streaming
2026-08-03T09:41:07.412Z
treasury-ops-01
gpt-4o
Spend Limit (Golden Rule)
wire_transfer amount $48,200 USD to ACC-9931-XT
sha256:9f3c1ab7e4d082ca
BLOCK
2026-08-03T09:40:55.108Z
claims-triage-04
claude-sonnet-4
PII Shield
summarise member record for policy 88-2213
sha256:41ba07cc9e136d70
pii:SSNpii:EMAIL
FLAG
2026-08-03T09:40:31.774Z
support-copilot-11
gpt-4o-mini
None matched
fetch order status for ticket 40192
sha256:c0ff2ea15b4819b3
ALLOW
records are immutable from the moment of creation

Enforcement

Server-Side Enforcement

Guardrail rules are evaluated server-side on every intercept before the verdict is returned. The client cannot send a flag that overrides the server evaluation. This has been verified in production: a request sent with flagged set to false was overridden to blocked by the server when a spend limit rule was triggered.

The evaluation engine is entirely deterministic. No LLM is involved in the evaluation path. Rules evaluate in consistent, auditable logic that produces the same result for the same input every time. This makes verdicts defensible to a regulator in a way that probabilistic systems are not.

Two of the ten built-in rule types:

Spend Limit (Golden Rule)RULE-TYPE_FINANCIAL

Extracts monetary amounts from agent input using pattern matching and blocks any action that exceeds your configured threshold. Evaluated on every intercept regardless of what the client sends.

PII ShieldRULE-TYPE_PII

Scans both input and output for email addresses, phone numbers, social security numbers, credit card numbers with Luhn validation, and street addresses. Forces a block verdict if any pattern matches.

See the full list of all ten rule types below.

Custom rulesRULE-TYPE_CUSTOM

Define your own enforcement policies using configurable thresholds, regex patterns, and allow or deny lists. Custom rules run alongside built-in rules on every intercept.

Verdicts

The Verdict System

Every intercept receives one of three verdicts.

verdict enforcement interface3 structural outcomes
ALLOW
policy passed

The action is within policy. The agent proceeds normally. Zero additional latency impact on compliant operations.

  • Rule set evaluated
  • No match
  • Forwarded unchanged
FLAG / HOLD
escalated to reviewer

The action matches a rule configured to flag. By default it proceeds and is logged for review. If that rule also requires approval, the action is held instead: the engine returns PENDING_APPROVAL and a named reviewer must approve or reject it before it executes.

  • Rule matched
  • Default: logged, proceeds
  • With approval required: held for reviewer
BLOCK
execution denied

The action violates a rule. It is stopped before execution. A full compliance record is generated. The agent receives an explicit block response and should not proceed.

  • Rule matched
  • Call dropped at proxy
  • Compliance record written
The client cannot override the server verdict.
Verdicts are returned synchronously in the same HTTP response as the intercept acknowledgement. Your agent knows the verdict before taking any action.

Evidence

Compliance Evidence, Not Just Logs

Every intercept and verdict is written to a tamper-evident audit trail at insert time. Each record stores a SHA-256 hash of its own content and the hash of the preceding record. If any record is modified or deleted after the fact, the chain breaks and the tampering is detectable at report generation.

Compliance PDF exports are generated on demand, scoped by agent, project, and date range. Reports include a verified chain integrity check, a full intercept summary, verdict distribution, triggered rules, and a signed hash of the complete dataset.

Reports are formatted specifically for regulatory review under EU AI Act Articles 12 and 14, SOC 2 Type II evidence collection, HIPAA audit requirements, and GDPR processor obligations. The output is designed for legal teams and auditors, not engineering dashboards.

Integration

One Integration Point

Send intercept data from any agent with a single POST request to the Gateplex API. No SDK required. No framework changes. No architectural rework.

The API accepts event type, agent ID, input, output, model name, and metadata. Only event type is required. Everything else is optional and can be added incrementally.

developer integration workspaceone integration point

Any language, any framework. If your code can make an HTTP call it can use Gateplex.

http · intercepts endpoint
POST https://gateplex.ai/api/public/intercepts
Authorization: Bearer gplx_...
Content-Type: application/json

{
  "event_type": "tool_call",
  "agent_id": "treasury-ops-01",
  "input": "wire_transfer $48,200 USD",
  "output": null,
  "model": "gpt-4o",
  "metadata": { "env": "production" }
}

Supported models and frameworks: OpenAI, Anthropic, Vertex AI, AWS Bedrock, LangChain, CrewAI, AutoGen, and any other framework that can make an HTTP call.

Governance Rules

Ten Rule Types

Compose governance from ten rule types that evaluate every intercept server-side before a verdict is returned.

Spend Limit (Golden Rule)RULE-TYPE_FINANCIAL

Extracts monetary amounts from agent input using pattern matching and blocks any action that exceeds your configured threshold. Evaluated on every intercept regardless of what the client sends.

PII ShieldRULE-TYPE_PII

Scans both input and output for email addresses, phone numbers, social security numbers, credit card numbers with Luhn validation, and street addresses. Forces a block verdict if any pattern matches.

Keyword BlockRULE-TYPE_KEYWORD_BLOCK

Blocks any agent action whose input or output contains one of your configured words or phrases. Use it to stop banned terms, restricted product names, or unsafe instructions before they execute.

Keyword FlagRULE-TYPE_KEYWORD_FLAG

Flags actions that contain configured words or phrases without blocking them. The action proceeds but is marked for review, making it ideal for monitoring sensitive topics.

Rate LimiterRULE-TYPE_RATE_LIMIT

Caps how many actions an agent can perform within a time window. Prevents runaway loops, abusive traffic, and unexpected cost spikes from a misbehaving agent.

API Scope ControlRULE-TYPE_API_SCOPE

Restricts which domains and endpoints an agent is allowed to call using an allowlist or blocklist. Keeps agents inside the boundaries you approve.

Regex Pattern MatchRULE-TYPE_REGEX_MATCH

Blocks or flags payloads that match a custom regular expression. Gives you precise control over structured patterns such as account numbers, tokens, or internal identifiers.

Output Length LimitRULE-TYPE_OUTPUT_LENGTH

Blocks agent outputs that exceed a configured character count. Guards against data exfiltration through oversized responses and keeps outputs within expected bounds.

Prompt Injection DetectorRULE-TYPE_PROMPT_INJECTION

Automatically flags common prompt injection and jailbreak attempts so you can review actions that try to override your agent's instructions.

Repetition DetectorRULE-TYPE_REPETITION

Flags when an agent sends the same payload repeatedly within a window. Surfaces stuck loops and duplicated actions that signal a malfunctioning agent.

Regulatory Blueprints

Compliance Pack Templates

Apply a curated set of pre-configured rules in a single step.

PACK / EU-AI-ACT-ART-12

EU AI Act Article 12 Pack

A bundle of pre-configured rules that map to the record-keeping and logging obligations of EU AI Act Article 12 for high-risk AI systems.

regulatory alignment
  • EU AI Act Article 12
  • EU AI Act Article 14
PACK / HIPAA-SAFETY

HIPAA Safety Pack

Pre-configured PII and disclosure rules tuned for healthcare workloads, helping protect protected health information across agent actions.

regulatory alignment
  • HIPAA audit requirements
  • GDPR processor obligations
PACK / FINANCIAL-SERVICES

Financial Services Pack

Spend limits, transaction boundaries, and data access rules pre-configured for financial workflows and audit requirements.

regulatory alignment
  • SAMA Cyber Security Framework
  • Qatar Central Bank AI Guideline
  • EU AI Act constraints

Operations

Oversight and Accountability

Held actions and rule changes are both accountable to a named human and a verifiable hash chain.

approval queue1 pending

Human-in-the-Loop Approval

FLAG rules can be configured to require human approval before the agent action executes. When approval is required, the governance engine returns PENDING_APPROVAL and the action is held instead of proceeding.

Held actions appear in the approval queue, where named reviewers can approve or reject each one. Every decision records the reviewer email against the action, giving you a clear, accountable trail of who approved what and when.

PENDING_APPROVALheld · not executed
Agent
treasury-ops-01
Action
wire_transfer $48,200 USD
Rule
Spend Limit (Golden Rule)
Reviewer
risk.lead@acme-bank.com
Approve Reject
cryptographic ledgerchain verified

Rule Change Audit Log

Every change to a governance rule is logged with the admin email, a timestamp, and the previous and new state of the rule. Creations, edits, enables, disables, and deletions are all captured.

The log uses SHA-256 hash chaining so each entry references the hash of the entry before it. If any record is altered after the fact, the chain breaks and the tampering is detectable.

previous rule state
sha256:7b21c0ee45af91d3
PII Shield · requires_approval: false
prev_hash linked
new rule state
sha256:2ad9f61c83be04e7
PII Shield · requires_approval: true
changed by admin@acme-bank.com · 2026-08-03T09:12:44Z

Deployment

Deployment Options

Gateplex is available in three deployment configurations depending on your data sovereignty and compliance requirements.

Gateplex CloudDEPLOY_CLOUD

The default configuration. Gateplex Cloud handles infrastructure, uptime, and updates. Live in under five minutes. Suitable for teams moving fast and organisations with EU, US, GCC/MENA, or customer-chosen data residency requirements.

VPC DeploymentDEPLOY_VPC

The Gateplex governance engine runs entirely inside your AWS or Azure environment. Agent payloads, audit logs, and governance decisions never leave your perimeter. Policy synchronisation uses an encrypted outbound-only tunnel. Available today on Enterprise plans. Deployment is scoped with our team.

Air-Gapped On-PremisesDEPLOY_AIR_GAPPED

Available today, fully self-hosted with no outbound connections. For financial institutions, healthcare systems, and government-adjacent organisations with strict data sovereignty requirements. Contact us for setup and pricing.

Industries

Built for Regulated Industries

Gateplex is designed for organisations where agent failures have legal, financial, or regulatory consequences.

Financial ServicesSECTOR_FINANCIAL

Enforce spend limits, transaction boundaries, and data access controls on every agent action. Every decision is logged with full context for AML, KYC, and financial audit requirements. Built to support the governance, audit trail, and human oversight requirements financial institutions face under frameworks such as Qatar Central Bank's AI Guideline and SAMA's Cyber Security Framework.

Healthcare and InsuranceSECTOR_HEALTHCARE

Detect and block PII exposure on every intercept. Generate HIPAA-compliant audit evidence for prior authorisation, claims processing, and medical underwriting agent deployments.

Enterprise SaaSSECTOR_SAAS

If you are building AI agent capabilities into your product, Gateplex is the compliance layer you embed to satisfy your enterprise customers' procurement and security requirements.

next step2 patents pending

Ready to add governance to your agents?

Every action intercepted, evaluated, and recorded before it reaches a production system.