Governance Pilot

Request access to the Keon Governance Pilot.

Add receipt-backed governance to an existing AI workflow through the Keon MCP Gateway. Qualified pilot users receive 1,000 governance calls to test policy checks, receipt generation, and proof-of-execution workflows without adopting the full Keon platform.

1 pilot tenant
1,000 governance calls
MCP Gateway access
Signed governance receipts
Pilot Context

Runtime governance first.

This pilot validates Runtime governance, tenant isolation, signed receipts, and MCP Gateway reliability. Cortex memory, Collective cognition, and full Control onboarding are intentionally excluded.

Existing AI workflow
What model, framework, agent stack, or automation needs a governed Runtime boundary.
Policy and receipt need
What policy check should happen and which receipt-backed outcome must be preserved.
Pilot fit
Expected volume, environment, feedback willingness, and whether anonymized learnings may be used.
Pilot Boundaries

What qualified pilot access includes.

This is a proof-generation pilot for teams testing Runtime governance against a real workflow boundary. It is not a full Keon platform trial.

Included
1 pilot tenant
1 API key or secure retrieval path
1,000 governance calls
MCP Gateway access instructions
Basic policy/governance check
Signed governance receipts
Tenant-scoped receipt history when enabled
Exportable receipt bundle when enabled
Offline verifier status link
CAES/CPP standards links
Feedback path or pilot report request
Explicitly excluded
Cortex memory
Collective cognition
Full Control onboarding
Custom agent orchestration
Long-term storage guarantees beyond pilot terms
Compliance certification claims
Production SLA
SOC 2 claims
SSO/SAML/RBAC unless already implemented
Custom enterprise support unless manually approved
Join Path

Dead-simple pilot path.

Submit the form. Keon approves or queues a real pilot tenant. You receive tenant details and MCP Gateway instructions by email.

01
Request submitted
Your Runtime governance use case reaches the Keon team.
02
Pilot fit reviewed
We check whether the workflow fits a Runtime-only MCP Gateway pilot.
03
Pilot tenant queued
Qualified requests are queued or approved for one pilot tenant.
04
MCP Gateway access prepared
The tenant, API-key retrieval path, and Gateway instructions are prepared outside this public site.
05
Access details sent
You receive tenant details, secure key retrieval instructions, docs, standards links, and feedback steps by email.
Trust Artifacts

Verifier and standards links.

Pilot users should be able to inspect receipt posture without trusting hosted UI claims. The open-source offline verifier is tracked as a first-class trust artifact and is not claimed as available until published.

Keon Offline Verifier
Coming soon. This repo does not currently include an open-source offline verifier artifact.
CAES StandardCPP Companion ProtocolCAES GitHub repositoryCAES website