Keel
Join the waitlist
  1. Keel
  2. Features
  3. Governance and audit

You decide how far the agent goes

Teams are right not to trust black-box agents. In Keel every agent action is bounded by a workspace setting, checked on the server, and recorded with who approved it.

Join the waitlistHow it works
Workspace settings, approvals

Even small changes wait for a person. This is where new workspaces start.

  • Add a comment ◆ Waits for approval
  • Add a label ◆ Waits for approval
  • Link a commit to a task ◆ Waits for approval
  • Shift task dates ◆ Waits for approval
  • Reassign a task ◆ Waits for approval

What it does

  • Three approval levelsSuggest only, auto low-risk, or approve everything. New workspaces start with every change waiting for a person.
  • RolesOwner, Admin, Member, and Guest, checked on the server for every request.
  • Private projectsHidden from lists, search, and AI answers for anyone who is not a member.
  • Audit logWho did what, why, and who approved it, filterable by actor, object, type, and date, with CSV export.
  • Workspace isolationPostgres row-level security on every workspace table, with an isolation test suite on every change.
  • Untrusted inputText from chat, docs, commits, and meetings can never grant tools or change policy.

How it works

Every flow in Keel follows one loop: a signal becomes a risk, a risk becomes a proposal, and only an approval changes the plan.

See the full loop

  1. Pick an approval level for the workspace.
  2. Agents read and propose within it.
  3. Anything beyond it waits for a person.
  4. Approved actions run with the approver’s permissions.
  5. The audit log records every step.

Governance and audit questions

What are approval levels?

A workspace setting that decides what agents may do on their own: suggest only, apply low-risk changes like comments and labels, or wait for approval on everything.

Is every AI action audited?

Yes. Every executed change writes an event with the agent, the reason, the evidence, and the person who approved it.

Can other workspaces see our data?

No. Isolation is enforced in the database with row-level security and tested on every change.

Related features

Proposals and approvalsEvery change arrives as a proposal with evidence; people approve. Ask Keel and searchAsk about the project in plain words; every answer cites its sources. Team collaborationComments, chat, live updates, review hand-offs, and notifications.

Try it on your own launch

Keel is in early access. Join the waitlist and we will write once, when your workspace is ready.

Join the waitlistAll features