A quick tour of airlock
If you have 8 minutes, the video on this page walks through airlock end to end: open the Control Room, connect a tool, set policy on it, reach it from 3 different AI clients, then watch a destructive action get held until a human approves it. If you do not have 8 minutes, here is the same tour in writing.
What airlock is, briefly
airlock sits between the AI clients your team already uses (Claude, ChatGPT, Copilot, Cursor, VS Code) and the external tools they call (Notion, GitHub, Salesforce, internal APIs, anything with an OpenAPI spec). One place to set policy, approve sensitive actions, detect anomalies, and manage your organisation's skills and agents.
Opening the Control Room
Signing in is 1 OAuth click. The Control Room opens on the catalog: every tool you have connected (Notion, GitHub, Linear, Salesforce, and so on) sits next to airlock's own native tools, Memory and Management. The sidebar has Skills, Agents, Analytics, Security and Settings.
Adding a tool in about a minute
Adding a new integration is 1 click: pick the tool, run OAuth, choose the workspace. airlock syncs the available actions and the new tile lands in the catalog ready to govern. No engineering, no YAML, no waiting on the platform team.
Setting policy: read-only or approval
Each tool gets per-action policy. On Notion, for example, reads are free but moves, updates and deletes can require an explicit human approval. You pick who can approve. The policy is applied server-side, every time the tool is called, from every AI client.
The cross-vendor moment
This is the part that is hardest to picture without seeing it. The same airlock URL added to Claude, ChatGPT and VS Code exposes the same 15 connected services across all of them, with the same rules. Switch AI clients tomorrow, your governance does not move. The AI client does.
Watching governance happen
The proof is in trying to break it. Ask the AI to delete a Notion page. The call leaves the AI, hits airlock, and stops at the approval gate. A pending request appears in the Control Room: someone wants to update a page in Notion. The approver clicks approve, the call goes through, and the audit log records who asked, what they asked for, and who said yes. Refresh Notion, the page is gone. Every action attributable.
What is next
Deep-dive videos following: the skill library, agent management, the security rules and anomaly detection in more depth. Follow airlock on LinkedIn for those.