What is AKA Security?
AKA builds the open-source security layer for the agent harness. AI Traffic Control (AI-TC) detects and protects sensitive data across every prompt, tool call, MCP server, and RAG pipeline.
Questions, answered.
What Agent Harness Security means, how AI-TC and Forward Deployed Security Engineers work, and how to get started.
What is Agent Harness Security?
AI agents run through four layers: orchestration, tool calls, identity, and data access. That stack is the agent harness, and it is the surface AKA secures. AI-TC scans every prompt and tool call across all four layers before it runs.
What is AI Traffic Control (AI-TC)?
AI-TC is AKA's open-source security engine for AI agents. It scans every prompt and tool call and keeps regulated data on your machine.
Is AI-TC open source?
Yes. AI-TC and the AKA kits ship in the open on GitHub under an open-source license.
Is AKA Security SOC 2 or ISO 27001 certified?
Yes. AKA Security is certified SOC 2 Type II and ISO 27001, and both reports are available through the trust center.
What's the difference between Community and Enterprise?
AI-TC Community is free for individual use. AI-TC Enterprise adds central control across an organization. See the pricing page for the full editions comparison.
What is Forward Deployed Security?
AKA embeds Forward Deployed Security Engineers, or FDSEs, in your environment. They build the security controls your agents need, run them inline, and keep them current as your stack changes.
Which agent harnesses does it support?
AI-TC supports Claude Code today, with more harnesses on the way. The AKA kits, claude-tools and preflight-skills, run on Claude Code, Codex, and Antigravity now.
Where does my data go?
Regulated data stays on your machine. Detection and enforcement run locally, so PCI, PHI, and PII never reach a model or a third party. The one exception is the optional setup calibration: only if you turn it on, AI-TC sends what its first history scan finds to the model API to be rated, so it can tell a real leak from routine noise. It goes to the model provider, never to AKA, and you can withdraw the consent at any time.
Who is behind AKA Security?
AKA Security was founded by Will Lin, Tom Burger, and Josh Scott, along with a bench of security engineers from teams across the industry.
How do I get started?
Try AI-TC for free on GitHub, or reach out through the contact page.