QALIBRE/
relay
Gateway control plane
Sign in to Relay
Use your workspace access key to inspect governed AI traffic.
relay
Gateway control plane
Use your workspace access key to inspect governed AI traffic.
relay
Control plane / Overview
A governed view of the AI requests your workspace can see.
Usage approvals
Control plane / Requests
Metadata only. Prompt and tool content is never shown here.
No active filters. Search and event filters apply to the latest 100 matching request events.
These controls filter the latest 100 matching request events in your scope. Conversation IDs group requests only; they do not expose chat contents or change authentication.
Control plane / Model registry
Configured route destinations, token limits and prices.
Control plane / Spend controls
Current limits and usage returned by the gateway.
Control plane / Guardrails
Read-only policy values currently enforced by the gateway.
Identity / Access lifecycle
Request scoped access, manage grants, and reveal generated keys once.
Loading access records…
Observe / Audit trail
Request activity and administrative changes for governance and reconciliation.
No active audit search.
Administration / Settings
Configure model routing, request logging, and retention.
Changes apply after saving. Turning off a provider stops its assigned routes.
Models and prices available through your providers.
Changes are staged until you save.
Choose the provider and model each API alias will use.
A fallback model must support at least the same token limits as its primary model. Provider fallback retries another hosting provider for the selected model.
Request data
Storage
Current storage health and request log retention.
Data retention
Preview and delete request events strictly older than the selected UTC time.
Choose a past UTC cutoff and preview the matching request logs.
Only request events are deleted. Usage accounting, budget reservations, administrative audit events, settings history, and keys are retained.
Request approvals
By default, another administrator must approve your access request.
Accountability
Who changed the configuration, when, and the previous and new values.
Destructive action
Remove saved application data and return the control plane to its initial configured state.
Data removed: provider configurations and stored credentials, model settings and mappings, saved gateway settings, Entra user records, access requests and keys, stored sessions, usage and request history, and administrative audit and settings history.
Configuration retained: database schema and migration metadata, deployment environment, authentication configuration, environment credentials, and static legacy API keys. Environment defaults may repopulate providers, models, or settings after sign-in. Entra user records are recreated when users sign in again.
Stored sessions are deleted. Stateless legacy signed-in sessions in other browsers remain valid until they expire; sign those out separately. This reset cannot be undone without restoring a database backup.
Preview current row counts before arming the reset.
QUOTA REQUEST
Ask a manager or admin for temporary usage. Only amount and reason are sent.