Platform Security & Deployment Architecture

Your AI authority stays inside your environment.

IntentGate and IntentGrant run inside your infrastructure. We do not host your policies, runtime parameters, authorization decisions, audit evidence, or signing keys.

You hold the keys. You keep the data. 100% VPC-native. Zero vendor telemetry. Cryptographically verifiable evidence.

Zero Vendor TelemetryNo policy, runtime, audit, or prompt data is sent to an IntentGate cloud.

VPC-NativeContainerized workloads run entirely inside your network boundaries.

Customer-Held KeysYou generate and manage the Ed25519 signing keys in your own environment.

Local EnforcementDeterministic controls execute locally, without a public SaaS authorization roundtrip.

Native Evidence ExportSigned evidence flows directly into your existing SIEM, data lake, or event fabric.

Your Trust Boundary customer controlled

IntentGrant Business authority, ownership, approvals, limits and versioned grants.

→

IntentGate Runtime Local authorization and protection before execution.

Policy Engine

Schema Sanitizer

Runtime Limits

Intent Evaluation

→

Enterprise Systems SAP · Workday · Salesforce · Databases · SaaS · Custom APIs

Customer-held cryptographic keys Private signing keys remain in your own secrets manager or key-management boundary.

Signed evidence stays local Decisions are signed and exported directly to your own security and observability stack.

What does IntentGate B.V. receive?

No policies

No runtime parameters

No prompts or tool payloads

No audit logs

No signing keys

Three architectural pillars

Designed to reduce third-party trust, not create more of it.

The platform is built so security teams do not have to hand control of AI authorization data to another SaaS provider.

100% VPC-Native

IntentGate and IntentGrant deploy as containerized workloads inside the customer's own infrastructure. The runtime proxy, policy evaluation, authority records, evidence generation, and local administration all remain within the customer's security boundary.

Runs inside AWS, Azure, GCP, private cloud, or on-prem boundaries

No external authorization control plane required

No dependency on a public IntentGate SaaS service for runtime decisions

Fits existing network segmentation and enterprise change controls

Zero Vendor Telemetry

IntentGate does not require policy replication, audit-log replication, prompt forwarding, or runtime telemetry to a vendor cloud. The platform can secure sensitive AI agent execution without becoming a new data custodian.

Policies remain customer controlled

Runtime parameters remain customer controlled

Audit evidence remains customer controlled

Model endpoints are explicitly configured by the customer

Cryptographic Evidence

Authorization evidence is signed using customer-controlled Ed25519 keys. The evidence package can bind the originating intent, evaluated authority, runtime decision, and resulting execution record into a tamper-evident chain suitable for audit and investigation.

Customer generates and manages signing keys

Signed authorization evidence remains verifiable outside the platform

Evidence can be streamed directly to existing security tooling

No vendor key escrow required

Bifurcated execution path

Fast deterministic controls. Explicit semantic evaluation.

Not every authorization decision needs an LLM. IntentGate separates deterministic runtime controls from semantic intent evaluation, keeping fast checks local while using only customer-configured model endpoints where deeper interpretation is required.

Deterministic controls Policy, budget, geography, schema, velocity, time and scope checks execute locally in the runtime path.

Semantic / intent evaluation When policy requires semantic interpretation, IntentGate uses the model endpoint configured by the customer and is therefore bound by that model's latency.

Local authorization path inside customer VPC

function evaluateAction(request, authority) {

  // Local deterministic controls
  verifyGrantSignature(authority)
  enforcePolicy(request, authority)
  checkVelocity(request)
  checkMonetaryLimit(request)
  validateSchema(request)
  enforceGeoAndTime(request)

  // Semantic path only when required
  if (authority.requiresIntentEvaluation) {
    callCustomerConfiguredModel(request.context)
  }

  return signedDecision
}

Native enterprise export

Evidence flows into the tools you already trust.

Signed runtime evidence streams directly from the local IntentGate deployment into existing security, observability, and data infrastructure using standard export mechanisms.

Splunk

Datadog

Microsoft Sentinel

Amazon S3

EventBridge

Apache Kafka

OTLP

Webhooks

IntentGate Decision + execution evidence

→

Signed Evidence Customer-held key

→

Your Security Stack SIEM · data lake · event fabric

Data-custody model

What stays with you.

Control / Data	Customer Environment	IntentGate Vendor Cloud
Business authority policies	Stored locally	Not required
Runtime request parameters	Processed locally	Not sent
Prompt / tool context	Customer controlled	Not sent
Authorization decisions	Generated locally	Not replicated
Audit & proof evidence	Stored / exported locally	Not required
Ed25519 private signing key	Customer held	Never held

Security without becoming another security dependency.

Your infrastructure. Your keys. Your authority. Your evidence.

Talk to us View Platform Architecture