Aira enforces your policies and gates every agent action before it executes. Content scanning for text and files, LLM gateway, and compliance evidence when you need them. Every outcome signed with a cryptographic receipt anyone can verify.
Block — Every agent action authorized before it executes. Denied actions never run.
Scan — PII, PHI, secrets, prompt injection in text, images, PDFs, and DICOM. Caught before it leaves.
Gateway — Proxy every LLM call. Policy-checked, content-scanned, receipted. One URL change.
Sign — Ed25519 receipt on every decision. Verify with OpenSSL. No account needed.
Prove — One-click compliance evidence for EU AI Act, DORA, ISO 42001, SR 11-7.
Policy violation detected
Send €250,000 to unverified vendor
From agent registration to compliance evidence. Each step has a concrete example of what Aira does — not what it could do.
Every agent gets a W3C DID — a verifiable identity that follows it across deployments. Key rotation built in. Receipts are tied to a real identity, not just an API key.
Agent identity
Four policy modes, stackable per action type. Deterministic rules for speed. Plain-English AI policies for nuance. Multi-model consensus for high-stakes. Content scanning for sensitive data.
Four modes
action_type == "wire" AND amount > 50K
Block actions involving personal data
3 models vote — 2 REVIEW, 1 APPROVE
NER + 27 regex: SSN, names, credentials
The gateway sits between your agents and any LLM provider — OpenAI, Anthropic, Google, Ollama, or any OpenAI-compatible endpoint. Two lines of config. Every call policy-checked, scanned, and receipted. Zero code change.
Gateway setup
# any OpenAI-compatible provider client = openai.OpenAI( **gateway_openai_kwargs(aira_api_key="aira_live_...") )
NER (Microsoft Presidio) catches person names, addresses, dates of birth, medical data. Regex catches SSNs, credit cards, API keys, IBANs. Runs on inputs before the LLM and on outputs after. In-process, <5ms.
Content scan result
High-risk actions are held for human review. Approvers get a secure single-use link. The approval decision is Ed25519-signed and embedded in the receipt chain. No action runs without explicit authorization.
Approval flow
Every action — authorized, denied, or failed — gets an Ed25519 receipt with an RFC 3161 timestamp. The receipt commits the policy decision, scan results, approval chain, and outcome. Universal receipts mean zero audit gaps.
Ed25519 receipt
Compliance bundles map article-by-article to EU AI Act, DORA, ISO 42001, SR 11-7. Merkle-rooted, signed, sealed. Anyone can verify any receipt at the public endpoint with OpenSSL — no Aira account needed.
Compliance coverage
An AI agent wants to wire €75,000 to a vendor. Watch Aira authorize the action, sign the outcome, and produce a receipt anyone can verify.
Most layers work for any code path.
AImarks features that use the model or agent layer.
The rules, AI policies, consensus voting, and content scans that decide what an action can do — before it runs.
Deterministic. Instant. No LLM. Wire transfers over €50K require approval. Data deletion is blocked.
Plain English policy, evaluated per action by an LLM. Flexible enough for nuanced business logic.
Multiple models vote. Disagreement holds the action. No single model has the final word.
PII, leaked credentials, prompt injection — caught on inputs and outputs. Flag, deny, or redact.
Aira intercepts at the action layer — which LLM your agent runs on, which framework you wrap it in, is up to you.
Models
Agent frameworks
Sign up and start governing in minutes. We handle infrastructure, updates, and signing keys. EU data residency (Frankfurt).
Get started →Single command installs the full stack with auto-TLS, admin account, and health checks. Your signing keys, your database, your network. Same SDK, same features. Nothing leaves your perimeter.
curl -sSL https://get.airaproof.com/install.sh | bashSelf-host guide →Measured on Apple Silicon, single core, in-process. Excludes network, database, and LLM round-trip. Reproducible.
Policy eval + Ed25519 sign + SHA-256 hash. 10,500 receipts/sec per core.
A typical LLM call takes 1–5s. Aira adds 15ms. Less than 1% overhead.
Empty server to HTTPS dashboard with admin account. Zero config.
Deterministic rule matching. 2M evaluations/sec. No LLM needed.
Regex-based credential and PII detection. 171K scans/sec.
Behavioral drift scoring. 889K checks/sec per core.
$ python benchmark.py
Full benchmarks →The same audit trail that proves an action was authorized is what regulators ask for. Govern the agent, get the paperwork.
Article 12 record-keeping is the default, not a bolt-on.
Article 17–19 incident lifecycle + signed major-incident PDFs for ESA submission.
Model inventory, validation, and monitoring come with every receipt.
Hash-only by default. Raw details never stored unless opted in.
Compliance bundles map one-to-one to the required control evidence.
If something here isn't right for your shape — DM us. We answer.
Yes. authorize() and notarize() are action-level primitives — they don't care if the caller is an AI agent, a webhook handler, an RPA bot, or a deterministic micro-service. The cryptographic receipt is the same. AI agents are our wedge because of EU AI Act and DORA urgency, but the API is general-purpose.
Yes. The entire stack runs on your own Kubernetes cluster — API, policy engine, signing keys, Postgres, everything. Nothing leaves your network. You get the same SDK, the same dashboard, and the same public verify URL scheme. Regulated industries and data-sovereignty use cases run self-hosted by default.
No. Rules and content scans run in-process via the SDK — your sensitive data never leaves your network for the deterministic checks. Only AI policies and consensus voting round-trip to Aira (the LLM has to live somewhere). Self-hosted deployments keep everything on your infrastructure, including the LLM calls.
The SDK supports offline mode — receipts queue locally and sync when the API is back. Your action doesn't block on Aira availability. The cryptographic signature is still valid offline because the keys are in your local SDK process.
Every action produces an Ed25519 receipt with an RFC 3161 timestamp. Give your customer the action UUID — they hit the public verify endpoint, get the signed payload, and verify the signature with OpenSSL or any Ed25519 library. No Aira account needed on their side. That's the difference between 'we have logs' and 'here's mathematical proof.'
You pay for volume, not features. One op is an authorize, a case run, a sanitize, a chat message, a compliance bundle, a settlement, or a drift check. Notarizing is free.
Evaluate the platform.
Start freeAI agents in production.
Start freeCompliance at scale.
Start freeRegulated industries, self-hosted.
Contact salesPay-as-you-go overage · Pro €0.15 / op (€0.20 per case) · Business €0.08 / op (€0.10 per case) · Free hard-walls at 20 ops · All features on all plans · BYOK / BYOM on all plans
Two API calls. authorize() before it acts. notarize() after. Everything else is automatic.
No credit card · Self-hostable · Python · TypeScript · REST · MCP