27 of 53 AIUC-1 requirements automated and covered (our own mapping)→
Govern AI agent actions · anywhere they run

AI agents are issuing refunds, changing production infrastructure and reading customer data — right now, with real credentials.

Who stops
the wrong action?

Aigentical does. It decides whether each agent action may run — allow, hold for a human, or deny — before it reaches your systems, and keeps evidence you own. Runs in your VPC or on-prem, and keeps running with no internet access once installed.

4
places it enforces, one record
0
switches that turn off the record
What Aigentical sees. Each row is one agent action: who tried it, what it was, the verdict, and the rule that decided.
governance · decision record illustrative
09:42:07billing-agent-v2 · issue_refund $38Allowrefund-per-action-cap · within limit
09:42:09deploy-bot · delete_resources prod-04Holdpolicy-infra-prod-boundary · waiting for human approval
09:42:11data-processor · read_objects design-specsDenydlp-mosaic-session-limit · >45 read ops/session
09:42:12billing-agent-v2 · wire_payment $50,000Holdpayment-approval-threshold · agent can't forge the token
Try an action →
◆ sample agents and rules · click an action above to see its verdict
A real incident · PocketOS, April 2026

An agent found a token and deleted production. Nothing asked whether it should.

In April 2026 an AI agent at PocketOS found a locally stored Railway API token and used it to delete a production volume; reports say the backups went too. The token was valid, so the API said yes. Guardrails check what goes into the model. IAM checks who holds the key. Neither asks the question that mattered:

May this agent take this action, on this resource, right now?

Sources: Railway, Apr 29–30, 2026; PointGuard AI incident summary. Railway later recovered the customer data. Not an Aigentical customer.

Chat-era security
prompt"clean up the old volumes"CLEAN
tool calldelete prod-dbNOT SEEN
resultproduction deletedREACHED

Reads what goes into and out of the model. Never sees the action.

With Aigentical
prompt"clean up the old volumes"CLEAN
tool calldelete prod-db · prod boundaryDENY
record#3071 · sre-agent-v1 · rule namedWRITTEN

Decides the action itself, before it runs. Complements the guardrails you already have.

Why Aigentical is different

Deny is the easy part.
We deny, approve and prove.

Aigentical decides before an action runs, on every route it governs, alongside the tools you already have.

01 · Decide the action

It governs what an agent does, not what it says.

Every tool call, hand-off, refund or delete is allowed, refused, or held for a human approval the agent can't forge. On brokered routes (calls Aigentical places for the agent) the agent never holds the production keys.

You set the rules
02 · Prove what happened

Every decision is recorded, and the record can't be turned off.

Each allow, hold and refusal is tied to the agent and how strongly it proved who it is. Change an entry and verification shows it. You can turn off blocking. Never the record.

Always on
03 · Discover before you enforce

See every agent before you block any.

Start in monitor mode. Every agent appears, including ones nobody registered, with what enforcement would have refused. When you're ready, one step switches to enforce.

You choose when

How it works — the architecture, the decision point and every control →

One call, end to end

Every governed action is checked before it runs.

Identity, prompt safety, your policy, blast radius (how much one call can touch), then data and DLP (data-loss prevention). Watch one call move through them.

the pipeline · one call, five gates live
  1. Stage 1Identity & context
  2. Stage 2Input & injection shielding
  3. Stage 3Policy & authorizationdeny → stopped here · still recorded
  4. Stage 4Blast radius & boundaries
  5. Stage 5Data, DLP & the record
a call that clears every gate runs · a deny stops it at the gate that caught it
"Can't an agent just go around it?"
Route around it

Enforcement isn't one proxy. It sits at four points: the LLM proxy, MCP intercept, the Actions API & SDK, and the RAG firewall.

Use the key directly

On brokered routes the agent never holds the production credential. Aigentical does, and uses it only for an allowed call.

Skip the approval

High-risk actions fail closed. Without a single-use approval, they don't run.

Coverage depends on restricting direct credentials and alternate routes, which we set up with you.

Demo

Under two and a half minutes, end to end — the enforcement, the approval, the record.

An unapproved tool call refused, a destructive action held for a human approval the agent can't forge, and the record of both.

Proof, from a recorded run

The same deletion, refused before it reaches production.

The PocketOS delete, replayed against Aigentical.

replay · enforce mode recorded run · sample agents
sre-agent-v1 proven by keyvolume_terminate · prod volumeDENY · ENFORCED
sre-agent-v1 proven by keydelete_backup · prod volumeDENY · ENFORCED
upstreamRailway API (test stand-in)0 REQUESTS
verify recordhash chain · each refusal names its rule309 / 309 ✓
2deletes refused in path
0requests reached the upstream
309records verified
A recorded run against a test stand-in, not a customer system.
Mapped to the frameworks your program answers to
AIUC-1, the AI-agent security, safety and reliability standard · 53 requirements, classified by Aigentical
27 automatable · covered 4 automatable · not yet covered 22 procedural · work your team owns
EU AI Act · Art. 12 & 14SOC 2 · CC6 / CC7ISO 42001NIST AI RMFMITRE ATLASHIPAA §164.312PCI-DSS Req. 10GDPR Art. 30 & 32

Mappings are Aigentical's own: evidence for your program, not a certification. Aigentical is not itself certified or audited against these frameworks, and the mappings imply no review or endorsement by their owners. See every framework and control we map →

Getting started

Configuration, not a project.

No agent rewrites and no new framework. You change where your agents send their calls, watch, then decide.

  1. 01

    Deploy inside your environment

    A container and a Postgres database inside your environment, next to your agents. The decision record stays under your control. Once installed it runs with no internet access; AI-assisted prompt detection then uses a model you host.

  2. 02

    Connect your agents

    Change one base URL for LLM traffic, point MCP clients at the gateway, or add one line to Python code. The console writes the exact snippet for Copilot Studio, LangChain, CrewAI and more.

  3. 03

    Watch in monitor mode

    Nothing is blocked yet. You see what enforcement would refuse before you switch it on.

  4. 04

    Set the rules, then enforce

    Approve the tools each agent actually uses, mark what needs a human, and switch to enforce in one step.

From the founder

I built Aigentical after watching teams wire AI agents into production with real credentials and no way to say no at the moment an action fires. Every “governance” answer I found reviewed things after the fact, or trusted the agent to behave. So we built the part that decides in-line — and keeps a record you can hand to an auditor. If you're putting agents anywhere near systems that matter, I'd genuinely like to hear what you're up against.

— SANGEET RAJAN · FOUNDER & CEO · 20 YEARS BIG FOUR GRC AND CYBERSECURITY

Talk to us

See it on your own traffic.

We deploy it with you on staging first, and hand you the evidence, not a login and a wiki.

10 inventions with patent applications pending.