Short videos, learning paths and feature guides, including the four KrisVen tools coming to AWS Marketplace. Each feature is labelled with its current status, so you know what you can try today.
Watch one of these first. Both use synthetic data.
A tour of governed memory, expert reasoning, human review and the Decision Ledger.
The four tools, how onboarding works and answers to common concerns.
Each path takes about 20 minutes and uses only the pages on this site.
Where AI decisions create cost and risk, and what changes once each one can be proven.
How approved knowledge, human review and sealed records answer the question months later.
The architecture, the MCP tools and how an agent reaches them through your gateway.
Status labels: Sandbox you can try it in a KrisBox sandbox today. Coming soon built and tested, waiting on an external listing. Planned designed, not built yet.
Agents read only knowledge that a person has approved, and every answer cites its source.
Domain checks run before a decision goes out, and anything outside policy goes to a person.
Each decision is sealed with an Ed25519 signature over what it relied on, and anyone with the public key can verify it later.
Agents act only within limits you set: which tools they may use and when a person must approve.
Agents from other companies can discover KrisVen and transact with it over A2A, MCP or REST, using test payments only.
Four tools in one remote MCP server, billed per operation through your AWS account.
KrisVenkrisven_read: approved context, with sourceskrisven_write: drafts that wait for a person to approvekrisven_seal: a signed record of a decision and its evidencekrisven_verify: checks a record and names any changeSeal can work from SHA-256 fingerprints of your documents instead of the documents themselves.
Add KrisVen to your gateway as an MCP target, and every agent behind it sees the four tools.
A container version of KrisVen that runs inside your own AWS account. It is designed but not built.
A short self-assessment showing where your AI decisions are hard to prove today.
Get your score →The listing is not live yet. This is how onboarding will work once it is published.
Find KrisVen in AWS Marketplace and subscribe. Charges per operation appear on your AWS bill.
Who: your AWS buyer or adminAWS sends you to KrisVen Studio, where you link the subscription to your organization and choose which tools to enable.
Who: your KrisVen adminAn OAuth client is delivered to Secrets Manager in your own AWS account. It is never emailed or shown on screen.
Who: automaticAdd KrisVen as an MCP target in AgentCore Gateway, or in any MCP client, using those credentials.
Who: your platform engineerLoad the policy, thresholds and precedents for one workflow, then approve them so agents can read them.
Who: your domain ownerCall krisven_seal on a decision, then run krisven_verify on it, the way an auditor would.
KrisVen needs to prove what a decision relied on. It does not need a copy of your documents to do that.
The knowledge you choose to load into governed memory, such as approved policies and thresholds, is stored by KrisVen. Supporting documents for a decision can stay with you as fingerprints.
Not yet. The listing is being prepared. This page will be updated when it is published.
Pay per operation, with separate counts for Read, Write, Seal and Verify. Charges appear on your AWS bill. Prices will be shown on the listing.
No. krisven_write creates a draft. Only a person in your organization can approve it into governed memory.
Your credentials stop working, and further calls are refused. You can still verify records you sealed earlier, offline, with the public key.
No. Any MCP client that supports OAuth client credentials can call the tools. AgentCore Gateway is one convenient option on AWS.
In a KrisBox sandbox with synthetic data. Ask for access.
Start with one workflow. Seal one decision. Verify it the way an auditor would.
Talk to us about a KrisBox sandbox, or get your AI Trust Score first.