Choosing the right product
AI Border Gateway and Endpoint Guard are independent capture points; each stands on its own. Cortega Agents read the traffic either one records.
What each covers
| AI Border Gateway | Endpoint Guard | |
|---|---|---|
| Governs traffic sent through your gateway | Yes | |
| Sees AI usage on employee devices your gateway never sees | Yes |
Cortega Agents, including AI Verifier, read traffic from AI Border Gateway, from Endpoint Guard, or both, once you turn that traffic source on for the agent. See Cortega Agents for the full catalog.
A short answer for each case
- You route, cost-control, and secure LLM/MCP traffic that already goes through a gateway you control: AI Border Gateway.
- You worry about AI usage on laptops and desktops that never touches your gateway. A developer using a personal AI tool, a browser assistant, a local MCP tool: Endpoint Guard.
- You need responses automatically checked for a specific failure mode. A hallucinated legal citation is the flagship example today: Cortega Agents, specifically AI Verifier.
- More than one of these is true: use more than one. They compose; none of them is a prerequisite for another.
Deciding between On-Prem, SaaS, or Dedicated? See Online vs Hosted.