Produkt

Control your AI gateway, guardrails, regions, and agent workflows from one place

Manage providers, API keys, guardrail policies, regions, logs, alerts, agents, billing, and developer access across your Outgate deployment.

Outgate Console is the operations cockpit for secure agentic AI. Configure which models your organization can use, how requests are routed, what sensitive data is protected, which regions traffic runs through, and who has access to gateway credentials and developer tokens.

Gateway
John
Anfragen heute
184.3K
+12% vs gestern
Aktive Provider
7
in 3 Regionen
Alerts (24h)
23
8 PII, 15 Credentials
Geschätzte Kosten
€42.18
Monat bisher
ProviderStatusAnfragenLatenz
AnthropicHealthy92.1K412ms
OpenAIHealthy61.4K388ms
Smart RouterHealthy30.8K

Most teams adopting AI agents quickly outgrow scattered provider settings, local credentials, and unmanaged usage. LLM providers, API keys, and routing rules end up spread across teams. Security policies are hard to enforce consistently across chat, CLI, and API traffic. Logs, alerts, costs, and regional deployments are difficult to inspect in one place.

Outgate Console gives platform, security, and engineering teams a central control plane for their AI gateway. Configure providers, guardrails, regions, agents, and developer access from a single interface, and watch traffic flow through the gateway in real time.

What you get

01

Provider and routing control

Connect OpenAI, Anthropic, local models, smart routers, failover routes, and custom backend LLMs. Manage provider credentials, exposed gateway endpoints, model availability, and per-provider usage from one place.

02

Guardrail policy management

Create and attach guardrail policies that detect, anonymize, or block sensitive data before requests reach upstream models. Manage tool access, detection rules, alerts, and the protected detection vault.

03

API keys, developer tokens, and access

Mint, revoke, and monitor API keys for gateway access. Manage personal developer tokens for og CLI, OAuth grants, organization members, MFA, roles, and plan-gated access.

04

Logs, alerts, metrics, and cost visibility

Watch traffic flow through the gateway in real time. Inspect request logs, alert triggers, latency, token usage, error rates, cache usage, provider performance, and estimated model costs.

05

Region and deployment governance

Provision and manage regions for private, regulated, or multi-region deployments. Control where traffic runs, which providers are active per region, and how regional gateway infrastructure is exposed.

06

Agent operations

Define agent runtimes, manage sandbox sessions, inspect project volumes, choose sandbox images, and control how autonomous workflows run across your organization.

Wie es funktioniert

From gateway setup to governed AI traffic

  1. 01Admins connect upstream model providers such as OpenAI, Anthropic, local models, or private LLM backends
  2. 02Console creates gateway endpoints, API keys, routing rules, and provider shares for teams and applications
  3. 03Security teams define guardrail policies for PII, credentials, secrets, tool usage, and sensitive project data
  4. 04Developers use Chat, og CLI, or direct API access through the protected Outgate Gateway
  5. 05Requests are inspected, anonymized, blocked, or routed according to the active policies and selected region
  6. 06Console shows logs, alerts, metrics, token usage, latency, provider health, and estimated cost in real time
  7. 07Admins adjust policies, keys, providers, regions, and agent settings as usage evolves

Bring AI governance into daily operations

Onboard providers, issue keys, enforce security rules, monitor traffic, and support developers without leaving the browser.

Frequently asked questions

Outgate Console is the management web app for Outgate. It lets teams configure providers, gateway endpoints, API keys, guardrail policies, regions, users, agents, logs, alerts, metrics, and billing.
No. Organization admins use Console to manage policies, users, regions, and billing. Developers can also use it to manage personal access tokens, OAuth grants, and CLI access.
Yes. Console manages the providers, regions, guardrails, developer tokens, OAuth grants, and gateway policies used by Outgate Chat and og CLI.
Yes. Console supports upstream provider configuration for services such as OpenAI, Anthropic, local models, smart routers, failover routes, and private backend LLMs.
Yes. Teams can create guardrail policies, attach them to providers, manage tool controls, inspect alerts, and review anonymized detections.
Yes. Console includes request logs, alert views, token accounting, latency metrics, error rates, provider metrics, model usage, and estimated cost reporting.
Yes. Pro deployments can manage regions, select the active region, provision regional infrastructure, and route traffic through the selected gateway region.
The og CLI uses Console for OAuth login and developer token authorization. Admins can manage those tokens and authorized apps from Console.