One platform, every role.

Platform teams run it, developers build on it, executives answer for it, and integrators deliver on it. Here is what each gets.

Platform teams

Offer governed agentsas a shared service.

Give business units agent templates with identity, rules and audit wired in, and run every agent they ship on one platform.

Teams start from an approved template, with identity, rules, and audit attached.

Every tool and model call goes through your gateways. Your IdP, SIEM and credential store stay in place.

Versioned, simulated against real traffic and rolled back like any deploy.

App developers

Point your client at one gateway URL. Authorization, credentials and audit happen on the call path.

Point your MCP or model client at a gateway, and nothing else in your code changes.

Model keys and tool tokens never reach your process, because Dome adds them on the way out.

A refused call names the rule that refused it.

Executives

Dome answers what is running, who is accountable, and what it costs from one record.

Every agent registers, whoever built it and wherever it runs, and the inventory is one query away.

The agent and the person it acts for travel with every call, and an incident resolves to a name.

Spend caps bind to an agent, a team, or a workspace, and chargeback no longer needs a reconciliation.

Systems integrators

Identity, rules, credentials and audit are the same on every engagement. Build them once on Dome and spend the engagement on the agents.

Every call their agents make lands in one trail, where one query reconstructs any action.

Organizations, tenants and workspaces are in the model, with isolation on every call.

Clients inherit a dashboard, a CLI and a rules repo, not a bespoke integration.