- CTRL
- compute-travel-expense-pre-approval
- VERSION
- v3
- ISSUED
- 2026-05-12 14:32:07 UTC
- SEALED BY
- ⌃ Sarah Chen · Finance
- RECEIPT
- rcpt_3f7a92b8e4c1
- ROOT
- 0x4e2a...b71c
Your AI runs your rules.
Not its training data.
Upload your policies. Your AI invokes them as typed Ctrls — answers, calculations, data lookups, signed actions. Every call leaves an Ed25519 Receipt of Record your auditor can verify.
Verify offline → curl ctrlai.com/api/receipts/rcpt_3f7a92b8e4c1
Your AI is creative about how to help. It is not creative about your rules.
Most AI products either over-promise (“the AI runs your company”) or under-deliver (“the AI drafts an email”). Ctrl AI does the procedural work — the 60–80% of white-collar work that is routing, reconciling, checking, drafting. Your team verifies. The verify loop replaces the processing loop. Your team got their week back.
How to help
Reading the question. Picking the right Ctrl. Composing multi-step plans. Asking clarifying questions. Spotting gaps in your coverage.
What your rules mean
Inventing logic. Judging policy questions. Generating numbers or facts from training data. Acting destructively without a signed gate.
Judgment, not processing
The 20–40% of work that needs judgment: sign-offs, exceptions, hard people calls, strategy. The procedural 60–80% — the part that ate the week — is handled.
Three primitives. One signed unit.
LLMs guess. RAG paraphrases. Ctrl AI answers from typed Ctrls your humans signed — every reply, every action, every time. Hallucination is not mitigated; it is structurally impossible.
Ctrls
Typed callable functions signed by humans. Input schema. Output schema. Post-conditions. The LLM picks a Ctrl and calls it — it does not invent behaviour from prose.
Missions
Standing directives with success criteria. Auto-evaluated as Ctrls run. The agent has commitments, not just answers.
Cases
Durable working memory with an append-only event log. A multi-week decision is a single Case with every signed action attached.
Upload a folder. Ninety seconds to your first cited answer.
The visceral demo. No abstract pitch, no decks. You see your own company reflected back, and you watch the AI answer your question from your rules — with receipts. This is the whole product.
- §3·1
Ingest
Drop a folder of your policies — PDF, DOCX, MD, HTML.
Cloud connectors for Drive / SharePoint / Notion ship next. Until then, drag-drop is your friend. 50 files, 25 MB extracted text.
- §3·2
Posture
In 60 seconds, your company reflected back: departments, roles, gaps.
“Your company has 6 departments. Legal has 47 docs and 0 Ctrls. Finance has 12 docs and 0 Ctrls. You appear to be missing documentation for Security/IT.”
- §3·3
Ask
Type a question. Every sentence cites a signed Ctrl. Every chip opens the Receipt.
Pick from suggested questions derived from your own docs, or type your own. The answer is a sequence of typed Ctrl invocations, each producing a verifiable receipt.
- §3·1Ingestrunning
- §3·2Posturequeued
- §3·3Askqueued
Already onboarded? See every workspace surface →
Every reply, a signed Ctrl. Every action, a Receipt.
The work your team does every day — approvals, reviews, decisions — becomes typed Ctrls a human signs. The LLM has one job: pick the right Ctrl and call it. It cannot reply any other way.
Your workflow isn’t here? Ctrls are typed callable functions — anything a human team handles on a checklist becomes one. Tell us about yours.
Every action leaves a Receipt of Record.
On every invocation we sign the inputs, outputs, signers, and trust level with an Ed25519 key, then append the digest to a chained-hash transparency log. Any counterparty — your auditor, your customer, your regulator — can verify the receipt offline with one curl and one signature check.
# Verify any Ctrl AI receipt offline curl -s https://ctrlai.com/api/receipts/rcpt_3f7a92b8e4c1 \ | jq '.receipt' > receipt.json # Fetch the public signing key curl -s https://ctrlai.com/.well-known/ctrlai/receipt-keys \ > keys.json # Verify the Ed25519 signature node verify.js receipt.json keys.json # → SEALED · entry #1,847 · root 0x4e2a...b71c ✓
No SDK required · No vendor lock · Cryptographic, not theatrical
You don’t author governance. You install it.
Expert co-signed bundles of typed Ctrls — 30–60 templates each, pre-mapped to the regulation’s clauses. Install in five minutes. Map your SOC 2 controls to Ctrls. Map every HIPAA Audit Control to a Ctrl. The auditor reads your receipts.
Four tiers. BYOK at every tier.
You pay Anthropic, OpenAI, or Google directly for inference. We charge for Ctrls, Receipts, and Packs — never per seat. Free is permanent, Starter and Business are self-serve. Talk to us only if you’re Enterprise.
Free
For individuals and tiny teams. Permanently free — not a trial.
- —Up to 10 people
- —5 Packs installed
- —25 signed Ctrls
- —100 invocations / month
- —Public Trust Portal
Starter
For small companies. Self-serve credit card; no sales call.
- —Up to 50 people
- —All Packs included
- —200 signed Ctrls
- —Unlimited invocations
- —Private Trust Portal
- —Email support
Business
For mid-market. Unlimited Ctrls, SSO, custom Packs.
- —Up to 250 people
- —Unlimited signed Ctrls
- —SSO + SAML
- —Custom Packs co-signed
- —Advanced delegations
- —Priority support
Enterprise
For 250+ ppl, regulated industries, named signers.
- —Unlimited everything
- —Concierge onboarding
- —SOC 2 report under NDA
- —Dedicated CS + SLAs
- —On-prem option (year 2)
- —BYOK or our keys
The Ctrl is signed.
The Receipt is the proof.
Upload a folder. Ninety seconds to your first cited answer. The work your team actually does — approvals, reviews, decisions — backed by Ctrls humans signed and Receipts your auditor can verify.