- +Read-only access to one production agent runtime, or the logs and configuration that describe it.
- +A security or compliance contact who can confirm access boundaries and evidence needs.
- +About one hour per week for kickoff, evidence questions, and readout scheduling.
Kommit Pilot
Prove the audit trail around one production agent.
The Kommit Pilot is a fixed-scope governance review for an existing agent: who owns it, what it can access, which policy applies, what evidence exists, and where human approval is missing.
01 /pricingChoose Pilot
02 /pilotConfirm scope
03 intakePicklist details
04 /book-demoSchedule kickoff
05 handoffStart with evidence
State 1 / Pilot landingCustomer gives us Customer gets back
A governance Pilot, not an engineering workflow tool.
This is for Director of Compliance, Head of Risk, CISO, and AI governance owners who need defensible evidence before agent adoption scales.
- +Audit-trail export for the agent in scope.
- +Policy coverage report against the controls agreed at intake.
- +Control gap analysis with evidence gaps separated from control gaps.
- +Prioritized recommendations for the next controls to automate.
State 2 / Intake
Short form, mostly picklists.
Tell us enough to scope one production agent and route you into the existing kickoff scheduler. No long discovery form, no second booking tool.
Scope guardrail: one production agent, read-only evidence sources, one security or compliance contact, and a kickoff slot booked through the existing scheduler.
Prepare
Agent runtime owner, read-only logs or config path, and access-boundary reviewer.
Kickoff
One production agent, evidence sources, policy questions, and readout audience.
Handoff
Audit export, policy coverage report, control gaps, and recommended next controls.