Keel Docs
Control your AI before it runs. Hard limits, policy, and tamper-evident audit — enforced before any request executes.
Keel is the AI control plane for governed execution. It sits between your application and AI providers, evaluates policy and budget before governed execution, and records tamper-evident audit evidence on the documented public surfaces.
On Keel-managed routes, no request reaches a provider before passing the decision boundary.
Route guarantees are not identical: permit-first is still decision-only plus later caller-reported closeout, while Keel-managed routes own execution directly.
Use the docs map to choose the right starting point across product, architecture, and security.
Understand the product boundary, active public surfaces, and the current scope of the platform.
Create a project, add a provider key, and send one governed request through Keel.
Review the public runtime model behind permit-first governance and execution.
Read the current security posture, isolation model, request-freshness controls, and prompt-firewall limits.
Public mental model
- decision before execution
- execution only if permitted
- evidence always recorded
- one governance boundary across supported providers
What Keel covers
- permit-first decisions with
POST /v1/permits - governed execution with primary runtime
POST /v1/execute, provider-neutralPOST /v1/executions, and provider-native/v1/proxy/* - project-scoped usage, audit, and evidence readback on documented public surfaces
Recommended path
- Read Overview to choose the right path through the docs.
- Read What is Keel to understand the product boundary and active public surfaces.
- Run Quickstart to get a governed request through the stack.
- Use Architecture and API Reference to understand the runtime surface.
- Review Security, Threat Model, and Known Limits before production rollout.
API reference
The API reference section now includes authored docs for the first public developer-facing routes. Start with API Reference, then use Execute, Executions, Permits, Proxy Execution, Idempotency, and Errors.