Platform / Integrations
Does it meet the stack you already run?
GovernorAI governs agents it did not build, on infrastructure it does not own — so every integration here is an insertion point into something you already operate, not a platform you are asked to move onto.
ENFORCEMENT SEAMS
Where the decision is applied.
If a gateway already sees the call, that is where the decision goes. Each adapter is a thin protocol translator: it parses the tool call off the wire, builds the canonical execute request, and expresses the verdict in that protocol's own terms.
01Gateway and proxy adapters
failure_mode_allow: false is required.tools/call is governed; initialize, tools/list, ping and notifications pass through untouched.auth_request, Traefik ForwardAuth, an AWS Lambda authorizer, Apigee or Azure APIM. Allow returns 200, deny returns 403. This pattern cannot rewrite a body.02LLM gateways — governing the model call itself
CustomGuardrail.ext_proc filter.The gateway keeps the provider credentials, the connection and the retry behaviour. GovernorAI registers as a guardrail on the gateway that is already there and answers a question; it does not sit in the token path.
Shaped-argument materialization end-to-end is live for the AWS Bedrock inbound seam today. Until the generalized gate lands, the other adapters enforce allow, deny and pause end-to-end but do not return shaped arguments. Forward-auth cannot rewrite a body at all, by protocol — it emits a header instead. Both limits are properties of the seam, not roadmap language.
PLATFORMS
Named platform coverage.
Each of these has a page describing exactly what is and is not governed at that seam.
DISCOVERY SOURCES
Where unregistered AI activity shows up.
The discovery surface is derived from live wiring, so it cannot claim a source the backend cannot actually ingest.
01Agent frameworks
Framework runtimes are registered rather than found: an operator declares them, or they heartbeat themselves in. A framework install groups many agents under one process, so it is counted once, not once per agent.
02Identity and consent
03SIEM, log and telemetry
ddtags into user, host and env dimensions and reading the nested attributes object.governor.request_count, governor.request_latency, governor.policy_evaluation_duration.DECLARE AND OPERATE
Policy as a reviewed artifact.
This catalog lists only what an adapter, connector or parsing contract exists for. Environments we ask about during a briefing — Azure AI Foundry, Vertex, Salesforce, OpenAI Agents, Semantic Kernel, AutoGen — are questions about your stack, not claimed integrations, and are deliberately absent from the tables above. No integration count is stated anywhere on this page: a number invites a comparison the number cannot survive, and the seam is what determines whether governance is possible, not the tally.