AI Gateway Admin Settings

• General — Organization details that define how the gateway presents itself and how users join. This tab shows and lets you configure your Gateway URL (the inference endpoint your applications call for LLM requests) and your MCP Gateway URL (the endpoint AI agents use to call MCP servers through the gateway). It also lets you manage allowed email domains so that users from approved corporate domains can self-provision into the organization without requiring an explicit invitation.
• Gateway Registration — Available for Enterprise customers running AI Gateway in Hybrid deployment mode. Gateway Registration connects a self-hosted data plane (running in your own Kubernetes cluster) to the AI Gateway management plane, so that configuration — prompt templates, routing configs, integrations, and API keys — is pushed from Strata Cloud Manager to your data plane without request payloads leaving your environment.
• Authentication — Organization-wide authentication settings, including SSO configuration (AI Gateway supports SSO with any custom OIDC provider) and service account management for Admin API access.
• Encryption — Key management settings for encrypting credentials and sensitive data. This tab supports integration with your organization's KMS so that secrets referenced in integrations and configs are managed under your own key hierarchy.
• Security — Organization-level security controls, including settings that govern how the gateway handles inline configurations, blocks unauthorized API usage patterns, and enforces TLS requirements for data plane communication.
• Organization Properties — Custom metadata properties that can be attached to the organization and inherited by workspaces. Organization properties are used to enrich analytics and audit logs with business context (for example, cost center, environment tier, or compliance classification).
• Organization Guardrails — Content policies that apply to every workspace in the organization, regardless of workspace-level guardrail settings. Organization guardrails enforce a baseline security posture — for example, a PII detection rule or a prompt injection policy — that no workspace can bypass. Specific workspaces can be explicitly excluded from an organization guardrail if needed.
• Plugins — Custom extensions that add capabilities to the gateway pipeline. Plugins can intercept and transform requests and responses, integrate with external services, or enforce custom business logic that is not covered by built-in guardrail types.