For app dev teams
Ship the agent, not the governance
You are building an application, and the governance is somebody else's requirement that lands in your sprint. Dome moves it off your backlog and onto the call path: one URL, no provider keys, and denials that tell you which rule fired.
Speed, with control
The governed path should be the fast path
Teams route around governance when the governed way is slower than the ungoverned one. That is a tooling failure, not a discipline problem.
Calling a Gateway is less work than wiring four sets of credentials and building your own audit. The controls arrive as a side effect of the easiest thing to do.
Least resistance, by design.
Value
What you stop building
Governance you call, not implement
Point your MCP client or model client at a Gateway URL. Authorization, credential injection and audit happen on the path.
No provider keys in your code
The Anthropic key, the Zendesk OAuth token, the warehouse credential: none of them reach your process. Dome injects them at egress.
Denials you can debug
A refused call comes back with the rule that refused it. Simulate against real traffic before you ship a change.
One integration for every tool
Add a backend once and every agent that has the grant can see it. You stop writing per-tool auth.
Outcomes
What the first week looks like
Nothing here needs a platform team to finish first. A sandbox and a token are enough to get a governed call working.
First governed call in minutes
Register, grab a token, call a tool. The quickstart is four commands.
Local dev that behaves like prod
A disposable sandbox workspace, the same rules, the same audit shape.
Framework stays your choice
LangChain, a bare SDK, or your own loop. Dome sits at the call boundary, not inside your architecture.
Security stops being a gate
The controls they need are already attached to the path you are using.
Next steps