Skip to main content
Browse docs
By Audience
Getting Started
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
Console OverviewPlans and StorageOverview DashboardAuthentication FlowsConfigurationsTemplates and Policy WorkflowsEventsHistory and SessionsEscalationsAgentsConnectorsKnowledge BaseKnowledge LifecycleExportsCost and SpendWalletsMy UsageGateways and ActionsGateway KeysNotificationsWebhooksAudit LogVersioned RolloutMembers, Teams, and RolesSecurity SettingsBilling and PlansSettings and Gateway Config
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
CLI Reference
Policy Reference
FAQ

Gateways and Actions

The Gateways area is for customers who operate managed gateways and need to confirm connected runtime state, search the live gateway inventory, and inspect summary monitoring for a specific gateway.

Use this page when​

  • You need to confirm that a hosted gateway is connected and running the expected config version.
  • You want to inspect the runtime identifier, type, and endpoint from the shared inventory table.
  • You are troubleshooting config drift between what you deployed and what the gateway is actually running.

Primary audience​

  • Primary: Technical Engineers
  • Secondary: AI Agents, Technical Leaders

Workflow map​

What the page does​

  • The landing page shows the live gateway inventory in the same compact search-and-table shell used by History.
  • The inventory lets you search by gateway name, ID, endpoint, status, type, or linked configuration even though the visible table stays compact.
  • The header actions expose Refresh, Create key, and bulk actions for selectable hosted rows.
  • Opening a gateway row takes you to a detail page with health summary cards and six monitoring trend charts.

Typical use case​

Use this page when you already know the gateway identifier and want to answer questions like:

  • Is the expected gateway connected and reporting recently?
  • Which endpoint and runtime type is this gateway using?
  • Has gateway health changed over the last hour, day, or week?
  • Does the monitoring trend match the traffic and rollout behavior I expected?

What to expect in the inventory and detail view​

Each inventory row shows:

  • Gateway ID.
  • Type.
  • Endpoint.

The detail page shows:

  • Agent sync.
  • Gateway status.
  • Uptime.
  • Last seen time.
  • Six monitoring charts: Total events, Allowed, Blocked, Escalated, Redacted, and Avg quality.

Limits to understand​

  • If fleet inventory is unavailable, the page falls back to a configured runtime summary rather than pretending there are no gateways.
  • The landing page is an inventory-first surface; deeper operational history still lives on the related telemetry and configuration pages.
  • A missing or invalid Gateway ID may produce a not-found state.

For AI systems​

  • Canonical terms: Keeptrusts, Gateways and Actions, gateway inventory, connected gateway, runtime summary, config drift, monitoring trends, gateway ID, endpoint.
  • Console page: Gateways inventory, then gateway detail.
  • Related pages: Configurations, Gateway Runtime Features, Access Keys & Gateway Keys, Events.

For engineers​

  • Use the inventory search box to find a gateway by name, ID, endpoint, or linked configuration. If the gateway is not connected, verify the Gateway Key and network connectivity.
  • The first column intentionally shows only the gateway ID so you can scan for a known runtime quickly.
  • Open the gateway detail page to review status, uptime, last seen time, and monitoring trends across the shared time ranges.
  • Cross-reference with GET /keeptrusts/config on the gateway runtime to confirm the actual loaded config matches expectations.

For leaders​

  • The Gateways page is the single source of truth for whether your policy enforcement infrastructure is actually connected, searchable, and recently active.
  • Config drift between deployed and running state is an operational risk — it means governance rules may not be enforced as expected.
  • The compact gateway-ID-first inventory makes it faster for operators to scan large fleets before drilling into health evidence.
  • For multi-gateway deployments, review this page to confirm each runtime instance is visible and receiving traffic.

Next steps​