Incremental evaluation
Begin locally or in a non-sensitive test environment, inspect Observe decisions, and move tested policies to Enforce.
For public-sector teams
Build a verifiable path to governed model access.
Use staged policy, named workloads, minimal metadata, and versioned AWS infrastructure as a testable baseline. This is not an authorization for government workloads.
Implemented organization and workload-key policy
Validated AWS deployment infrastructure as code
Current availability stated for hierarchy, offline bundles, private networks, and retention controls
In plain language
Build a testable baseline without implying government authorization.
AI Gateway HQ provides versioned AWS infrastructure, workload policy, budgets, minimal metadata, and staged enforcement. Government authorization is separate. So are offline operation, restricted networks, supply-chain records, retention, and agency-specific requirements.
The readiness outcomeTeams can test the governance model with non-sensitive data in an authorized environment. They can also record every prerequisite for broader use.
For the operating team
Treat deployment boundary and update path as controls.
A government-ready package must name the owner for networking, identity, artifacts, keys, support, logging, recovery, and changes.
What administrators configure
Environment limits
Run pilots only in authorized environments. Set explicit limits for data, providers, networks, and accounts.
Release path
Require signed releases and automated infrastructure review. Customer-delivered offline bundles are not currently included.
Operations ownership
Document identity, key management, logging, retention, incident, backup, and support responsibilities.
What happens to each request
- 01Classify
Use explicit workload and data-class context; never infer authorization from a model name alone.
- 02Restrict
Limit eligible providers, models, credentials, and telemetry before the request can leave the gateway.
- 03Operate
Run the tested rule in Observe, Shadow, or Enforce according to the approved rollout stage.
- 04Review
Retain metadata evidence and administrative change history for authorized operational review.
See the working control
One place to see whether the control is actually in place for public-sector administration.
For public-sector administration, live API-backed counts for provider connections, routes, policies, requests, latency, and payload-storage posture.
- This public-sector administration view runs in the working customer console
- Exercised with safe OpenAI- and Anthropic-compatible simulators
- The public-sector administration capture excludes keys, prompt text, responses, and private email
For public-sector administration, live API-backed counts for provider connections, routes, policies, requests, latency, and payload-storage posture.
What administrators can change
The settings behind for public-sector teams.
For public-sector teams, the console shows each setting, its owner, and its scope so administrators can review changes before they reach live traffic.
Restricted-network package is not currently available
Customer-network data planes, signed releases, offline policy distribution, and local credentials still require implementation and validation.
Procurement transparency
Review current capabilities, dependencies, deployment limits, and missing assurance. No badge substitutes for that record.
Evidence, not assertions
Separate current capabilities from authorization work.
Procurement and security reviewers see what exists today and what remains. The page does not claim certifications the product has not earned.
Review security boundaries and current status- Environment limits: Run pilots only in authorized environments. Set explicit limits for data, providers, networks, and accounts.
- Release path: Require signed releases and automated infrastructure review. Customer-delivered offline bundles are not currently included.
- Operations ownership: Document identity, key management, logging, retention, incident, backup, and support responsibilities.
Questions teams ask
Questions about for public-sector teams.
What buyers, administrators, and security reviewers need to confirm for for public-sector teams.
Does AI Gateway HQ have a government authorization?
No. The current hosted service does not claim FedRAMP or another agency authorization.
Can it run in a restricted or disconnected network?
Not as a generally available package today. Offline policy, signed artifacts, local credentials, upgrades, and support paths still require implementation.
What can be evaluated now?
Workload identity, provider pools, staged policy, budgets, metadata evidence, and the AWS infrastructure baseline can be evaluated using non-sensitive data in an authorized environment.
Start safely
Start guided setupSee what the policy would do before it can block production.
Start with a provider connection, a limited workload key, and Observe mode; move to enforcement after your team confirms the result.