EU AI ACT · READY ENFORCES IN 102 DAYS

Finally.
Governable.
Explainable. Accountable.
AI.

The AI Accountability Layer sits inside your cloud, intercepts every interaction, enforces policy at runtime, and signs the evidence cryptographically.

Book a meeting See the runtime
LIVE · exec_b8f2…0a11
agent: ops-writer connector: gmail
01
USER INPUT
user prompt
02
BEFORE LLM
pre-inference
03
BEFORE TOOL
pre · external API
04
AFTER TOOL
post · external API
05
AGENT RESPONSE
post-inference
✓ record signed RSA-4096 · hash-chained · timestamped · retained 10y
99.2%
PII detection accuracy
<100 ms
per-checkpoint overhead
10 yr
WORM retention, RSA-4096
EU AI ACT · ENFORCES 2026-08-02 HIPAA AI RULE · MAY 2026 COLORADO SB 24-205 · JUNE 2026 NYDFS CIRCULAR LETTER NO. 7 SR 11-7 MODEL RISK MANAGEMENT GDPR · DPDPA · PIPL · LGPD · POPIA ISO/IEC 42001 AIMS NIST AI RMF 1.0 OMB M-24-10 EU AI ACT · ENFORCES 2026-08-02 HIPAA AI RULE · MAY 2026 COLORADO SB 24-205 · JUNE 2026 NYDFS CIRCULAR LETTER NO. 7 SR 11-7 MODEL RISK MANAGEMENT GDPR · DPDPA · PIPL · LGPD · POPIA ISO/IEC 42001 AIMS NIST AI RMF 1.0 OMB M-24-10
The gap

Three truths
create one crisis.

01

AI adoption is blocked

Security teams cannot approve AI tools that touch email, tickets, records or payments, because there is no way to prove what those tools did. Samsung banned ChatGPT in 2023. Three of the four largest US banks followed. Dozens of Fortune 500s have similar bans in effect.

02

Bans do not work

Policy documents do not have a runtime. Employees use AI tools on personal accounts with company data. Shadow AI produces zero audit trail and leaves no record of the disclosure.

03

Regulation is arriving

The EU AI Act enforces Aug 2, 2026, with fines up to €35M or 7% of global revenue. The US HIPAA AI rule lands May 2026. Colorado SB 24-205 enforces June 2026. Each requires automatic recording of events for high-risk AI systems.

Current governance tools write policy, monitor behavior, or scan prompts. None of them enforce governance at the moment an AI action happens. None produce cryptographic evidence.

The framework

Intercept. Explain. Prove.

THE RAIDU RUNTIME. NOT A DASHBOARD ON THE SIDE, A LAYER IN THE PATH.
I
Layer I
usermodel12345

Intercept

Raidu sits on the path between people and every AI system. Every prompt, every tool call, every API response passes through five governance checkpoints. Nothing bypasses the runtime. Nothing runs outside the record.

II
Layer II
[ck02] BEFORE_LLM
policy: pii.mask.strict
matched: US_SSN ×1, CREDIT_CARD ×1
action: replaced with hashed tokens
// An SSN was detected and masked
// before the prompt reached the model.

Explain

Every checkpoint produces a plain-English record of what fired, what matched, what was masked, and which policy triggered. A compliance officer can read it. A regulator can follow it. Engineering does not need to translate.

III
Layer III
record_id0x8af4b21c301
sig_algRSA-4096/SHA-256
prev_hash0x7c1…e9a2
tsarfc3161 ✓
retainWORM · 10yr
✓ VERIFIED · TAMPER-EVIDENT

Prove

Every record is signed with a 4096-bit RSA key, hash-chained with SHA-256, timestamped against RFC 3161, and written to WORM storage with 10-year retention. The evidence is mathematically verifiable and tamper-evident.

The runtime

Five checkpoints.
Zero exceptions.

Every AI execution passes through five governance checkpoints. Each is visible in the timeline. Each generates a signed record.

Checkpoint 01 · user prompt

User Input

Input guardrails fire first. Prompt injection detection, jailbreak pattern matching, tool-abuse checks, and PII detection. Raw input is logged so the AI understands the request. Full audit entry opened.

example trace
INPUT → "send contract to jane.doe@acme.com, SSN 412-55-9021"
EMAIL US_SSN
99.2%
PII accuracy
<100ms
overhead
60+
entity types
Checkpoint 02 · pre-inference

Before LLM

Pre-inference guardrails. PII masked before the language model sees the prompt. Jailbreak payloads neutralized. Policy injected into context. Credential scope bounded. SSNs, cards, MRNs are replaced with deterministic tokens the AI can still reason about.

example trace
PROMPT → "send contract to [EMAIL_1], SSN [SSN_1]"
EMAIL US_SSN
99.2%
PII accuracy
<100ms
overhead
60+
entity types
Checkpoint 03 · pre · external API

Before Tool

Tool-call guardrails. PII masked before Raidu forwards the call to an external tool (Gmail, Jira, Stripe, and so on). Tool here means an external service the AI touches, not Raidu itself. Scope check, budget check, and outbound redaction enforced per connector.

example trace
gmail.send(to=[EMAIL_1], body='…attached…')
EMAIL
99.2%
PII accuracy
<100ms
overhead
60+
entity types
Checkpoint 04 · post · external API

After Tool

API responses from the external tool are scanned with connector-aware rules. PII returned by external systems is caught and quarantined before entering the AI context.

example trace
gmail ← 200 OK · 0 entities introduced
99.2%
PII accuracy
<100ms
overhead
60+
entity types
Checkpoint 05 · post-inference

Agent Response

Response guardrails. Post-inference scan for hallucination, bias, toxicity, groundedness, and any PII leakage. Merged rules from every connector the execution touched. The response the user sees is clean.

example trace
RESPONSE → "Contract delivered to Jane."
99.2%
PII accuracy
<100ms
overhead
60+
entity types
Scope

Every AI interaction in the enterprise, regardless of format.

Chat

Human ↔ Model
can you draft…of course. here is…· RAIDU CKPT ·

Direct conversations with language models. Every prompt, every response, every attached file.

Agents

Autonomous workers
Agmailstripejira

AI workers that call APIs, create tickets, read email, move money. Every tool call is in the record.

Workflows

Multi-step chains
LLMTLLMALL 4 STEPS SIGNED

Chained models, tools and approvals. The chain is governed end-to-end, not just at the edges.

◆ Runtime-native. Governance happens while the AI runs. Not after.

Surface area

34 connectors.
379 tools.
One runtime.

One-time credential validation per connector. Shared OAuth for Google Workspace. Shared Azure AD for Microsoft. Every connector declares the PII entity types it needs to function. The firewall adapts per connector. Gmail can see email addresses because it needs them. Stripe cannot see names because it does not.

Gmail Calendar Drive Chat Sheets Docs Slides YouTube Outlook Teams SharePoint Jira Linear Asana Notion Confluence GitHub GitLab Slack Discord Twilio SendGrid HubSpot Stripe Zendesk Salesforce Intercom PubMed Semantic Scholar ArXiv S3 BigQuery Snowflake Databricks +more
Models

175 models.
24 providers.
Your approved list.

Enterprises approve a subset. Raidu enforces it. Per-user and per-agent budgets prevent runaway spend. Switch a model off at 9:02 and every execution after 9:02 can prove it used something else.

OpenAI Anthropic Google xAI Groq DeepSeek Mistral Cohere Fireworks Perplexity Cerebras Azure OpenAI AWS Bedrock Vertex AI Together Replicate HuggingFace Ollama NVIDIA NIM IBM watsonx Databricks Voyage Jina Nomic
Why cryptographic proof matters

Logs can be edited.
Signatures cannot.

Raidu's proof stack is designed for regulator acceptance. "Your AI did X at time T, signed K, untampered" becomes a statement you can verify independently, in court.

  • RSA-4096 RSA-4096 signatures on every audit record
  • SHA-256 hash chains that break if any record is altered
  • Merkle trees for efficient bulk verification
  • RFC 3161 timestamps from an external authority
  • WORM storage write-once-read-many, 10-year retention
  • 99.2% accuracy PII detection across 60+ entity types
  • <100 ms overhead per checkpoint
Audit Record · Signed
raidu://audit/v1
record_id rdu_7e2f…b91a3
tenant acme-health-prod
exec_id exec_b8f2c4a10a11
agent ops-writer@v1.14
model anthropic/claude-sonnet-4.5
connector gmail · scope: send
checkpoints 5/5 passed
pii_detected 3 (EMAIL, US_SSN, CREDIT_CARD)
pii_masked 2
policy_version sha256:4a…9fe · v2026.04.21-1
sig_algorithm RSA-4096 / SHA-256
prev_hash 0x7c1b…2ae9a2
this_hash 0x8af4b2…1c301
tsa rfc3161 · digicert ts 2026
stored_at WORM · gcs://raidu-worm/.. · retain 10y
RSA-4096 signature · truncated
-----BEGIN RAIDU SIGNATURE-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4f8e1c2b3a4d5e6f7089
1a2b3c4d5e6f70819aab2c3d4e5f60718293a4b5c6d7e8f901a2b3c4d5e6f708
1a2b3c4d5e6f70819… [4096 bits]
-----END RAIDU SIGNATURE-----
Verify independently raidu verify --record rdu_7e2f…
Where Raidu runs

Three models. All inside your perimeter.

Data residency supported for GDPR, HIPAA, DPDPA, PIPL, LGPD and POPIA regions.

SAAS

Raidu Cloud

Deploys in Hours

Multi-tenant SaaS with strict tenant isolation. Available on GCP Marketplace today. Azure and AWS in Q3 2026.

GCP MARKETPLACE SOC 2 type II ISO 27001
DEDICATED

Dedicated Instance

Deploys in Days

Single-tenant inside the customer's own cloud account. Customer controls keys, region, encryption and data residency.

BYOC BYOK VPC-PEERED
AIRGAP

Self-hosted · Air-gapped

Deploys in Weeks

Full platform on customer premises with zero telemetry and no outbound traffic. Built for defense, intelligence, healthcare and state government.

FEDRAMP-READY IL5-ALIGNED NO TELEMETRY
Who buys Raidu

Four buyers. One answer.

PERSONA
CISO

"Can I approve AI that touches customer data without creating the next breach?"

PERSONA
CTO

"Can I ship AI in weeks instead of months, with governance built in?"

PERSONA
CCO

"Can I prove compliance to a regulator with evidence, not a policy document?"

PERSONA
VP of AI

"Can I standardize how every team uses AI without killing innovation?"

Priority industries

01 US Healthcare HIPAA AI rule · May 2026
02 EU Enterprises EU AI Act · Aug 2, 2026
03 US Financial Services SR 11-7 · NYDFS · CO SB 24-205
04 US State Governments NIST AI RMF · state statutes
05 Pharma & Life Sciences GxP · FDA AI/ML SaMD
06 Insurance NAIC model bulletin · state DOIs
◆ URGENCY INDEX · HIGHEST = DARKEST
Line in the sand

What Raidu is not.

Not a policy-writing tool.
We run governance. We do not draft it.
Not an observability dashboard.
We enforce in the path. We do not watch from the side.
Not an agent framework.
We govern agents. We do not build the agent logic.
Not a prompt firewall.
We govern the entire interaction, including every tool call and API response.

Category vs alternatives

CategoryThey…Raidu…
Policy-writing tools write AI policy enforce it automatically at runtime
Prompt-scanning gateways scan prompts govern entire workflows, including every tool call
Behavior monitors monitor model behavior enforce governance on every execution
Quarterly auditors audit quarterly account for every action
Agent frameworks help you build agents govern the agents you build on any framework
Vendor-native copilots run agents inside one vendor run governed agents across 24 providers, in your cloud
Supported by
Trusted by
INTEL LIFTOFF NVIDIA INCEPTION UAB MEDICINE EMBODYXR MAXQ XPLOSAFE CARE9
Dev surface

Governed where code is written.

Raidu intercepts AI coding assistants the same way it intercepts agents. Every prompt, every tool call, every generated line of code, inside the record.

C
Cursor
IDE · governed
GC
GitHub Copilot
IDE · governed
CC
Claude Code
CLI · governed
W
Windsurf
IDE · governed
OC
OpenAI Codex
CLI · governed
C
Cline
EXT · governed
RC
Roo Code
EXT · governed
GC
Gemini CLI
CLI · governed
O
OpenClaw
AGT · governed
◆ Plus Slack, Teams, Jira, Linear, Notion, GitHub, and 28 more
Next step

Ship AI with proof.

A 30-minute session. We run your hardest AI execution through Raidu and produce a signed record you can verify independently.

Request a proof See deployment options
team@raidu.com · 134 N 4th St, Brooklyn, NY 11249