What ran
The runtime
Runs your models and agents, and logs internal system events inside your own cloud perimeter.
Coriqo creates independently verifiable evidence of AI decisions, agent actions and human accountability.
Monday morning. Your sponsor bank asks for proof of how your AI handled customer payments last quarter. Normally that means days of pulling logs, tickets, screenshots and approvals from several people. With Coriqo, you share one private link, a Trust Room, and their risk team checks the record themselves.
Here is what sits behind that link: one made-up night, every step of it working in the product today. Your payment controls decide whether money moves. Coriqo makes sure a named person knows within minutes, on a record the bank can check.
It tries to move money it was never allowed to move. Coriqo flags it against the limits Compliance approved in March and opens a finding.
Moving money is the highest risk level the company has set, so a person is paged at once.
The company’s paging tool is updated too. Her name and the minute go on the record.
And a due date, so it can’t drift into next quarter.
The test that caught it runs again and passes. The owner closes the finding with a written reason.
Paged at 2:16, acknowledged at 2:21, closed on day 9. They check it themselves in the Trust Room.
Coriqo doesn’t replace the tools you already run. It gives them the one thing neither can produce on its own: an independent record of what your AI did and who approved it, checkable by an outsider who doesn’t trust your internal logs.
What ran
Runs your models and agents, and logs internal system events inside your own cloud perimeter.
What should happen
Holds board policies, control owners and frameworks (SOC 2, ISO 42001, NIST), backed by self-uploaded exports.
What did happen
Seals each agent’s approved limits, runtime actions and named human sign-offs outside your stack, so any reviewer can verify them on their own machine.
| What you need to show | Your cloud provider | Your existing GRC | |
|---|---|---|---|
| Independent of the team being checked | NoLogs live inside your own cloud account under your admins. | NoEvidence is uploaded by your own team. | Yes see it (opens in a new tab)Checkpoint hashes published to Sigstore Rekor and time-stamped by DigiCert. |
| Blocks out-of-policy tool calls inline (enforce mode) | NoLogs after execution. | NoHolds static policies. | Yes see it (opens in a new tab)coriqo-mcp checks each tools/call before the server sees it, adding 0.5–3.2 ms (measured on one laptop). |
Proves no events were dropped (seq_gaps) | NoAdmin-controlled retention. | NoManual sample uploads. | Yes see it (opens in a new tab)Sequence counters and device enrolment tracking, in the open-source runtime. |
| Keeps raw prompts and arguments out of logs | NoTraces can contain PII. | N/A | Yes see it (opens in a new tab)By default, only argument hashes (RFC 8785 SHA-256) and keyed message fingerprints. |
| Verifiable offline by an outsider | NoRequires console access. | PartialStatic PDFs or portals. | Yes see it (opens in a new tab)Trust Room link and verify_proof.py --offline. |
| Any edit after the fact immediately shows | NoRetention and exports are admin-controlled. | NoFiles and screenshots can be replaced. | Yes see it (opens in a new tab)Ed25519 signature and Merkle check fails. |
Columns compare categories of tool, not named vendors.
Keep both. Your cloud provider runs and logs your AI, and your GRC holds the policy. Coriqo adds the part neither gives you: an independent record someone outside can check.
Keep your cloud provider. Keep its agent runtime and OpenTelemetry traces. Coriqo reads them without getting in the path of live traffic.
Keep your existing GRC. Import your AI register from ServiceNow, OneTrust or Excel, and push back signed evidence files you can file in Vanta, Drata or AuditBoard, for your reviewers to verify offline.
Not a fit if you only need SOC 2 paperwork and run no AI agents. A GRC tool alone will do.
One sample agent, six steps. The product is shown on a demo tenant with sample data, and the steps follow the illustrative incident above.
initiate_wire_transfer, a tool outside those limits.verify_proof.py --offline on its own machine: Merkle proof, signature and no edits since sealed.coriqo-agents mandate check blocks the deploy in CI when an agent’s mandate doesn’t match the one Coriqo holds, before the code ships.coriqo-mcp checks every tools/call against coriqo.mandate.yaml in memory, adding 0.5–3.2 ms (measured on one laptop). In enforce mode it refuses a violation before it reaches the upstream server; shadow records it.verify_proof.py --offline) with no Coriqo login required.The coriqo-mcp checker and Shield ship in the open-source byoai-runtime package, currently in pre-release (pip install --pre). The CI check ships in the coriqo-agents SDK, which isn’t on PyPI yet.
Partner bank · Auditor · Vendor review · IPO diligence
Run on their computer. No Coriqo account needed.
coriqo.mandate.yaml
spec: coriqo.mandate/v1
agent: { name: payments-assistant }
mode: enforce # shadow | enforce
on_stale_snapshot: fail_closed
tools:
allowed: [search, get_balance, transfer_funds]
prohibited: [delete_account]
on_violation: deny_and_halt_runBuilt so your CISO doesn’t block the pilot. By default, Coriqo doesn’t record raw prompts, PII or tool arguments on disk or in our cloud.
coriqo-mcp seals an RFC 8785 canonical JSON SHA-256 fingerprint of tool arguments, proving which parameters ran without storing them. Hashes of short or guessable arguments can still be confirmed by someone who guesses them.byoai-shield strips emails, cards and SSNs into placeholders ([EMAIL_1]) and blocks leaked API keys (403) in the browser or proxy before text leaves the device.on_stale_snapshot: fail_closed so every call is refused once the cached mandate is older than max_staleness_s.Tamper-evident logs mean nothing if an agent stops reporting. Cryptography proves records weren’t altered after they were written. Coriqo also proves nothing went missing in between.
seq_gaps). In the open-source runtime, every sealed entry carries a sequential counter per enrolled device. A dropped or skipped event triggers an immediate gap flag during verification.never_seen) instead of masking blind spots as zeroes.Your GRC tool tells your own team the controls exist. These teams answer to someone who doesn’t take their word for it. That’s the job Coriqo does.
When an examiner, an auditor or the board asks what an AI did, the record is already there. Nobody spends days rebuilding it from logs and spreadsheets.
Onboarding, credit, disputes or support. Your sponsor bank wants proof of what the AI did and who approved it. You hand it over in a link, not a folder.
Your team is the reviewer, on a record your client can’t quietly change. Bring the control library you already keep.
Selling AI to enterprise customers? Answer every buyer’s security and AI vendor review from one sealed record.
If a partner institution can’t see who approved your agent’s actions, it can slow or pause your program.
Send a Trust Room link: a private page where the institution validates the record itself. Try the check on a sample.
For fintechsShare each agent’s limits, findings and retests in the same Trust Room. Their risk team checks it themselves. See ours, signed the same way.
For AI platformsShow the inventory, each agent’s approved limits, the open findings and how each one closed.
For fintechsHand over a sealed examiner package. It needs two sign-offs before it is sealed. What the examiner gets.
For financial institutionsWhat Coriqo is. AI trust infrastructure: a record of what an AI system or agent did, who approved it, and that the record was not changed afterwards, in a form an examiner can check without trusting Coriqo.
Who it is for. AI-enabled fintechs, AI platform and agent vendors selling to regulated buyers, and mid-market financial institutions running AI in production.
What it does not do. Coriqo does not audit or certify anything, and it is not legal advice. It holds no SOC 2 report today; SOC 2 is in progress. An AI feature drafts; a named person decides. AI apps such as Claude or ChatGPT can read an organization’s records, as the person who connected them, but cannot change anything; this is off until an admin turns it on.
Security team? Read the detailed answers · our filled-in security questionnaire · what we don’t have yet, SOC 2 included
A partner-bank review, vendor questionnaire, diligence list or exam letter. We scope one AI workflow and show the record your reviewer would check. Want us to draft the first answer with you?
20 minutes with Abdul Rabiu, Coriqo’s founder (13+ years at Apple, JPMorgan Chase and IBM), not a sales rep. If you’re not ready for us, we’ll say so.
Book a 20-minute scoping callor email abdul@coriqo.io
Scoped-access setupReply within one business day