The governance layer for agentic software.
Every agent is code that reasons with models and acts through tools. Dome governs all three: a Registry for the agents themselves, a Gateway for every tool call, a Broker for every model call. One control plane of access, authorization, and audit, across every runtime and every cloud.
Connect. Govern. Operate.
Docs · Start free · domesystems.ai
brew trust dome-systems/tap
brew install dome-systems/tap/dome
dome auth loginHomebrew 6 requires trusting a third-party tap before it will load its formulae. Direct downloads for macOS and Linux, with checksums and per-archive SBOMs, are on the latest release.
| What Dome actually does | What is Dome? |
| First agent under governance | Govern your first agent — allow employee lookups, redact contact details, deny payroll, from Cursor, Claude, or curl |
| The full path | Get started: four tutorials that build one governed workspace, in order |
| Your role | Choose your role — developer, operator, security, platform admin |
| How agents borrow identity | Learn: standing versus delegated identity, and why one shared agent beats one per person |
Cursor, Claude Code and Codex can sign in with your own Dome account and call governed tools over MCP.
- Set up an AI assistant
- Use Dome as an MCP gateway
- Use Dome as a model broker — any model, your provider key held server-side, every completion audited
Authorization is deterministic. Rules are versioned per scope, simulated against replayed traffic before they ship, and fail closed. Forbid always wins, so the same request decides the same way every time.
- Rules · Guards · Quotas
- Audit events — query by class, result, actor, resource, or payload
CLI · API · MCP · Python SDK · Glossary
- homebrew-tap — the
domeCLI formula - releases — CLI binaries, checksums, SBOMs
- demo-hr-desk — the reference app the Get Started tutorials govern
Questions: help · support@domesystems.ai · status · trust