Keel is the operating layer that makes agentic AI safe, observable, and auditable. Every change your people or your agents make carries a record of who did it, who approved it, and which controls fired. When an agent does something unexpected, you answer what happened instead of guessing; when someone asks for proof, you are not assembling it after the fact.
This is Keel's 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.
| When | Who | Actor type | Where | What | Run outcome |
|---|---|---|---|---|---|
| 2026-08-12 01:27 | Claude Code | agent | GitHub: keelport/keel | repo:keel | running |
| 2026-08-28 18:05 | steventchir | human | GitHub: keelport/keel | keelport/keel#195 | succeeded |
| 2026-08-28 17:48 | steventchir | human | GitHub: keelport/website | The feed and figures learn the three-way actor taxonomy | succeeded |
| 2026-08-28 17:45 | steventchir | human | GitHub: keelport/website | keelport/website#8 | succeeded |
| 2026-08-28 17:38 | keel-ops | service | Databricks: keelport | checked the evidence dashboard against its governed source | succeeded |
| 2026-08-28 17:38 | keel-ops | service | GitHub: keelport org | checked branch protection against the manifest | succeeded |
| 2026-08-28 17:32 | keel-ops | service | GitHub: keelport/keel | linked architecture decisions to their implementing commits | succeeded |
Work still in flight first, then newest first, as of 2026-08-28.
You cannot safely put an agent on an ungoverned estate. Keel installs the golden path first: gated deploys, protected branches, drift detection, rollback. The foundation agents can safely operate on, and the one your team needed anyway.
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.
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.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.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.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.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.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.Keel's own estate is governed by Keel. Every change on record so far was merged by the founder without an independent approver, and the system flagged every one.
Live figures from the ledger, as of 2026-08-28. They move.
A thirty-minute walkthrough of the live evidence, then what standing this up on your estate looks like. Write to hello@keelport.ca.