Let AI agents act in your systems. Keep control of every action.
CortexHub checks every tool call before it runs. Routine work goes straight through, risky actions wait for the people your policy names, and anything your policy forbids is blocked. Every decision is signed into evidence your auditor can verify.
- Claude, ChatGPT, your own agents and ours, through one gateway
- One sentence per policy, checked by code, not an AI model
- Signed evidence mapped to 7 compliance frameworks
Any agent. Any model. Your rules.
- ClaudeAllowedHubSpot: Read the Q3 pipelineDecided by: Toolkit decision: HubSpot read tools run
- Ava, a Co-workerNeeds approvalStripe: Refund $1,200Decided by: Org floor: refunds over 500, Finance approves
- ChatGPTNeeds approvalGmail: Email 240 customersDecided by: Group floor: sends externally to over 100 recipients, the member approves
- GitHub CopilotBlockedGitHub: Delete a protected branchDecided by: Tool override: delete_branch on protected branches is blocked
- Support agent (SDK)BlockedZendesk: Export every customer recordDecided by: Org floor: exports data that touches PII, blocked
- CursorAllowedJira: Open a ticketDecided by: Toolkit decision: Jira write tools run
A toolkit the agent's group was not given? The call is refused.
Agents now move money, email customers and change records. Who approved that?
Claude, ChatGPT and the agents your teams build connect straight to company systems. Each one arrives with its own keys, its own settings and its own logs, so there is no single place to decide what they may do and no single record of what they did. When an agent gets it wrong, the liability is yours.
No single control
Every assistant and agent is set up on its own. A rule you set in one does not reach the next.
No record you can stand behind
When a customer or an auditor asks what an agent read, changed or sent, the answer is spread across vendor logs and screenshots.
Security has to say no
Without control and proof, agents stay in pilots, or people use them anyway, outside any policy.
added to the average breach cost at organisations with high levels of shadow AI.
of agentic AI projects, at least, will be cancelled by the end of 2027, due to rising costs, unclear value or inadequate risk controls.
Every agent goes through one gateway. Your policies sit outside all of them.
Claude, ChatGPT, GitHub Copilot and other assistants connect over MCP, the open standard AI assistants use to reach tools. Agents your developers build connect through the CortexHub SDK. CortexHub's own Co-workers (an AI assistant for each employee) and organisation agents (shared AI teammates for a team) use the same path. Before any call runs, the gateway checks who is acting, for whom, and what the call would do.
Control sits outside every agent, ours included, so no agent can talk its way past it. Credentials stay in a vault and never reach the model. See what happens when something goes wrong
Build each policy as one sentence. Code decides every call, never an AI model.
Set an organisation floor every group inherits, a floor for each group, and one decision for the read, write and destructive tools of each toolkit. Tighten a single tool with conditions on its own fields. What the page shows is what runs.
- One sentence per policyPick what the tool does, the decision, who it is accountable to and when it applies: "When a tool that moves money as a refund then require approval, accountable to Finance, only when money over 500."
- Deterministic, checked by codeEvery floor item, toolkit decision and tool override is checked by code, the same way on every call. No AI model decides a live call.
- New tools are covered automaticallyCortexHub classifies every tool by what it does (moves money as a payment or a refund, sends externally, deletes) and recommends floors for the tools you connect. Floors match what a tool does, not its name, so a toolkit you connect next month is covered the day you connect it. A call no decision covers is blocked.
- Tighten one toolAn override on one tool asks first or blocks it, only when its own fields match, such as an amount over 500. An override only tightens its toolkit decision, never loosens it.
- Try a call before it happensEnter sample arguments for a tool and see what your policies decide for that group, who approves and what decided it. Nothing runs.
When a tool that moves money as a refund then require approval, accountable to Finance, only when money over 500.
- Applies to
- Every group
- Governs now
- and any refund tool you connect later
- Approves
- Finance
Amounts are read in real units: a refund a tool sends in cents is compared with 500 pounds or dollars.
Risky actions wait for the right person.
When a policy says a person must decide, the call pauses before it runs, and the people that policy is accountable to decide: the member the agent works for, your back office, or a group or people you name, such as Finance. An org admin can step in, recorded as an override. They decide in Slack, in the Approvals inbox or inside their AI assistant. Scheduled work nobody is watching waits too.
Follow one request from start to finish. Pick a kind of agent to replay it.
Akhil asks a Co-worker in Slack to update a deal in HubSpot.
Akhil messages the Co-worker in Slack, where the team already works.
Every action, signed into evidence your auditor can check.
Each decision is recorded with the agent, the person it acted for, the policy that decided and who approved. Records are signed and hash-chained, so any change breaks the chain and names the record. The evidence maps to SOC 2, ISO/IEC 42001, the EU AI Act, NIST AI RMF, NIST AI 600-1 (the GenAI profile), ISO/IEC 23894 and the OWASP Top 10 for LLM applications.
- SOC 2
- ISO/IEC 42001
- EU AI Act
- NIST AI RMF
- NIST AI 600-1 (GenAI profile)
- ISO/IEC 23894
- OWASP Top 10 for LLM apps
Who, what and why
Every record names the agent, the person or end user it acted for, the policy that decided and the approver.
Verifiable offline
Export the evidence for any period and verify it without trusting CortexHub.
Gaps point to their fix
Readiness is measured from what your agents actually did, and every gap names the setting that closes it.
This is readiness evidence for your own audits. CortexHub is CASA validated, and SOC 2 is in progress. See the framework mapping
Control you can check for yourself.
Every call is decided by code, the evidence verifies offline, and an agent reaches only what its group was given.
Every governed action is signed into a tamper-evident, hash-chained record.
Governed agents to deploy, under the same policies.
Co-workers
An AI Co-worker for every employee, in chat and Slack, that only uses what its person is allowed to use.
Learn moreBrain
The memory a Co-worker builds as it works: people, projects and decisions, which you can see and correct.
Learn moreRoutines
Scheduled, multi-step work that shows every step, the reason for it and where a person approved.
Learn moreIntegrations
The tools your teams use, plus any OpenAPI spec or MCP server you bring as a governed toolkit.
Learn moreCommon questions
Start with one workflow
Your first governed workflow, live in minutes.
Connect an assistant, connect a system, set a policy and run it. Tell us what you want your agents to do and we will help you choose where to start.
For the enterprise
See it govern your agents.
Book a demo to see policies, approvals and the audit trail on your own tools and security requirements.

