Turn "we govern our AI" from a claim into auditor-grade evidence.

Keel is the operating layer for agentic AI on Azure, Microsoft Fabric, and Databricks. Every change a person or an agent makes carries a record of who did it, who approved it, and which controls fired, in the form that OSFI B-13, NI 52-109, and Law 25 reviewers ask to see.

See the evidence How it works
Pre-launch. The evidence on this page is Keel's own.
Proof, not promises

We run our own controls on ourselves.

These figures are queried from the ledger that governs this company. The red one is the system flagging its own owner; the evidence page tells that story in full.

680
runs on record
4
by AI agents
488
by automated controls
59 of 59
changes merged without an independent approver
33
architecture decisions on record
Walk through the evidence

Live figures from the ledger, as of 2026-08-29 UTC. They move.

Every organization adopting AI agents faces the same two questions.

When the auditor asks what changed in March and who approved it, a folder of screenshots and a governance memo are not an answer. A memo says the controls exist. A ledger shows each one firing.

One

Can I let agents in without losing control?

You cannot safely put an agent on an ungoverned estate. Keel installs the golden path first: gated deploys, protected branches, drift detection, rollback. It is the foundation agents can operate on safely, and the one your team needed anyway.

Two

Can I prove what they did?

Every actor, human and agent, writes to one ledger held in your own estate. Who acted, under which identity, who approved, what the controls found. You read the same ledger your agents write to, row by row.

Every row below is Keel governing its own estate.

Two code repositories, a Databricks workspace, and the GitHub organization itself. Every change, deployment, and control run lands in the same table, whether a person, a pipeline, or an agent did it. There are no customers in this ledger yet.

When (UTC)WhoActor typeWhereWhatRun outcome
2026-08-12 01:27Claude CodeagentGitHub: keelport/keelrepo:keelrunning
2026-08-29 00:36keel-agent-keelport[bot] (for steventchir)agentGitHub: keelport/websiteFeed refresh: the redesign records itselfsucceeded
2026-08-29 00:31keel-agent-keelport[bot]serviceGitHub: keelport/websitekeelport/website#16succeeded
2026-08-29 00:29steventchirhumanGitHub: keelport/websiteThe evidence-document redesignsucceeded
2026-08-29 00:28steventchirhumanGitHub: keelport/websiteDeploy diagnostics: verify the token first, show full API responsessucceeded
2026-08-29 00:20steventchirhumanGitHub: keelport/websitekeelport/website#14succeeded
2026-08-29 00:17keel-agent-keelport[bot]serviceGitHub: keelport/websitekeelport/website#15succeeded

Queried from the Keel evidence ledger as of 2026-08-29 UTC. Work in flight first, then newest first.

A keel is the part of a ship nobody sees. It sits below the waterline and keeps the boat upright, so the crew can sail hard without thinking about it. Keel does the same job for a company adopting AI agents: the structure underneath that lets you move fast without tipping over.

How it works

Keel ships changes one opinionated way and keeps a record of everything that shipped.

One change, whichever actor makes it, moves left to right.

Change proposed Gate Ledger row Auditor export human or agent, signed named approver who, approver, verdict a query, not a hunt

One manifest, whole estate

A single reviewed file parameterizes a client: platform, environments, identity, approvers, evidence store. Repos generate from templates and onboard in dependency order with one command.

Stood up on a new client in a day.

Deploys that can't skip the gate

One merged commit flows dev to stage to prod; prod always pauses for a named human, who sees exactly what approving applies. No auto-approve path to prod exists. Not policy: structure.

A rollback is a governed deploy, not a bypass.

The estate can't quietly change

Daily controls compare live branch protection, approval gates, and infrastructure against what the manifest declares. Hand-edits and out-of-band changes become recorded findings the next morning.

Drift is bounded by time, not by luck.

One evidence base

Every control writes to one ledger: runs, events, alerts, rollbacks, tamper-evident and checkable after the fact. "Show me all unauthorized prod changes this quarter" is a query, not an archaeology project.

A control that isn't logged is a claim, not evidence.

Agents with accountable humans

AI agents get their own identity, cryptographically separate from any person's, and every agent carries the name of the person accountable for it. Supervision becomes gates and queryable evidence instead of watching.

Your agents' compute bill grows with the work; your payroll doesn't.

Governed to the exit

Create, govern, sync, roll back, retire. Offboarding is where orphaned access comes from, so leaving the fleet is as governed as joining it: one reviewed change retires a repo, and the record survives.

History is evidence: archived, never deleted.

Questions about the mechanism go to the same inbox: hello@keelport.ca.

For regulated teams

Most vendors sell controls. Keel sells evidence that the controls fired.

OSFI B-13 / E-23attributable records of automated and model-driven actions, with accountable-human mapping NI 52-109change authorization and separation of duties, evidenced per change at merge time Law 25 / SOC 2operating effectiveness demonstrated by daily recorded controls, not sampled screenshots ISO 42001AI actions governed under named human accountability, in one auditable graph

See it on your stack.

A thirty-minute walkthrough of the live evidence, then what standing this up on your estate looks like.

Write to hello@keelport.ca

Mail reaches the person who built Keel, not a queue. Say which stack your agents run on and the reply covers what the evidence layer looks like there.