Every AI action checked,
approved and recorded.
QUAICU Kernel is an AI governance kernel. It sits between your code and the action it is about to take. It checks the action against your policies, holds it for a person when a policy says so, and records what happened in a signed, append-only ledger. You run it yourself.
The open-source release is coming soon, under the Apache License 2.0.
Three answers.
An action runs only if a policy allows it.
| Your policy decides | What happens |
|---|---|
| Allow | The action runs, and it is sealed in the ledger. |
| Deny, or no policy matches | The action does not run. |
| Require approval | The action does not run. It waits in the approvals queue for someone else who holds the approver role. |
No matching policy, a policy that errors, an unknown caller or a failed ledger write all stop the action.
Whoever proposed an action cannot approve it. An approver must match the roles or users the policy names.
No account, no signup and no hosted service. With the starter configuration the kernel makes no outbound network calls.
Your function,
plus one line.
from quaicu import Kernel kernel = Kernel.local(policies="policies.toml") @kernel.guard(policy="payments.wire") # your function, plus one line async def send_wire(*, amount: int, to: str) -> dict: ... async with kernel.actor_context("alice", roles=("analyst",)): # who is acting await send_wire(amount=500, to="ACME")
[[policy.seed]] id = "wire-large-needs-approval" governs = "payments.wire" condition = "payload_amount >= 10000" decision = "require_approval" approvers = ["role:manager"]
- Two ways in. Embed the Python package in your process, or run it as a local HTTP service and call it from any language. Python 3.11 or newer.
- AI agents included. It governs an agent's tool calls over MCP: a denied or unapproved call never runs the tool.
- Policies are plain conditions. An action type with no matching policy is denied. When several match, deny beats require approval, which beats allow.
Policy, approvals
and a signed record.
| Layer | What it does |
|---|---|
| Policy engine | Policies written as CEL conditions, with a draft, review and activate lifecycle, and backtesting against recorded actions. |
| Ledger | An append-only Merkle log (RFC 6962) with signed tree heads, inclusion and consistency proofs, and an optional external witness. |
| Approvals | A human approval queue with separation of duties and expiry. |
| Consent | Purpose-bound consent, checked before an action is evaluated when a consent store is configured. |
| AI gateway | A model allowlist, PII masking, prompt logging and token budgets around model calls. |
| Also included | Durable workflows, event sinks, a model registry, fairness and drift sweeps, incident rollback, regulatory evidence packs, crypto-shredding for erasure, and an MCP server that governs agent tool calls. |
A starting point for the rules you answer to.
Drafts to adapt, not legal advice.
DPDP Act
Blocks processing without consent, outside the permitted purposes, or after a person has asked for erasure. Sends a transfer outside India to your data protection officer for approval.
EU AI Act
Blocks systems classed as prohibited and the banned practices. Sends a high-risk system run without human oversight, an AI that does not disclose itself, or unlabeled synthetic content to a person.
RBI and SEBI cloud and outsourcing rules
Blocks payment data stored outside India, storage without encryption at rest, and outsourcing without audit rights or an exit plan. Sends material outsourcing and transfers outside India for review.
The kernel enforces the rules you give it. Whether those rules are right for your business is for you and your counsel to decide. The packs are worked starting points, not certified compliance.
What it does not do yet.
- Version
- This is version 0.1.0. Interfaces may change.
- Tenancy
- One kernel serves one tenant.
- What the ledger proves
- That an entry was recorded and, against a key you pinned beforehand, that the log was not rewritten. A verifier cannot yet recompute an entry's hash from its readable fields.
- Independent review
- The ledger design is awaiting an independent cryptographic review.
- Signing keys
- With the default in-memory signer, the signing key changes on every restart. A key vault or cloud key service keeps it across restarts.
- Your obligations
- QUAICU Kernel is a governance control, not a substitute for your own legal and regulatory obligations.
Run it yourself,
or have us set it up.
We set it up and run it.
Our engineers wire the kernel into your product, write the policies with you and support it afterwards. Quoted like any other build.
Talk to usFree governance review.
A call that maps where AI acts in your product, and which of those actions should need an approval or leave a record.
Book a free governance reviewGuides from QUAICU Notes.
Open source,
coming soon.
Leave your email and we will tell you when QUAICU Kernel is released. Want to talk before then? Book a free governance review.