Platform
AI Border Gateway, Endpoint Guard, and Cortega Agents all run on one shared foundation. These modules aren't specific to any one of them; every component uses the same copy.
SSO
Enterprise identity providers (OIDC/SAML) for signing into the Cortega console itself, separate from the identities Cortega issues for LLM and MCP callers. See the Identity guide in Guides.
Your traffic data, queryable
Every request Cortega governs, across AI Border Gateway and Endpoint Guard, lands in one data store, queryable through the Cortega API with a scoped API key, so your own agents and scripts can pull traffic data directly.
Central observability
One Observability view for every LLM and MCP call, whichever component recorded it: model, tokens, cost, latency, and any guardrail finding. Team-spend, model-performance, and security-finding reports run over the same data.
A high-performance data warehouse and reporting engine
Traffic telemetry lands in a column-oriented store built for exactly this kind of query: aggregate millions of requests by team, model, or app in seconds. Insights and the Recommendations feature both read from it.
AI Bench
A benchmark runner that sends industry sample prompts through your gateway and model, with your guardrails active, and scores the results against the expected outcome. It covers general safety, healthcare, finance, legal, privacy/PII, and security red-teaming. The legal industry adds a hallucination check that looks up a model's own citations against a real case-law database, the same check Legal Agent runs on production traffic. See AI Bench.
Cortega API
Every console action is backed by a documented REST API: providers, models, teams, guardrails, identities, MCP servers, agents, and the traffic/analytics endpoints above. Scoped API keys, not session cookies, for programmatic access.
Audit logging
A record of administrative changes: who changed what, and when.
RBAC
Four built-in roles, admin, security reviewer, approver, and developer, enforced on both the server and the console, the same way across every component.
What's specific to a component, not the platform
Routing, guardrail enforcement, and MCP tool governance for gateway traffic are AI Border Gateway's own. Local, on-device interception and guardrails are Endpoint Guard's own. See AI Border Gateway and Endpoint Guard.