Ecosystem
Integrations
The platform fits into the systems an enterprise already runs. Authentication, secrets, observability, SOAR, and CI/CD — Dome speaks to all of them so bringing agents under management does not require rewiring the stack underneath.
Plays well with
The systems your enterprise already runs
AI-native · MCP
Dome is itself driven by AI
MCP is the protocol agents use to reach tools — and the Dome control plane is itself exposed as an MCP surface. The same platform that governs your agents can be driven by them. Triage denials with an assistant, draft a policy change in Claude, walk through audit events from Cursor, author rules from Copilot. Anything an operator can do at the CLI, an MCP-capable client can do too.
Claude · GitHub Copilot · Cursor · any MCP-capable client
Identity
Identity providers
Authenticate end users through your existing IdP and propagate that identity end-to-end across every agent and tool call.
Okta · Microsoft Entra · Auth0 · OIDC · SCIM
Secrets
Secrets & credentials
Provider keys and backend credentials never live in agent code. They stay in your existing secrets manager and rotate centrally.
HashiCorp Vault · AWS Secrets Manager · GCP Secret Manager
SIEM
Security information & event management
Stream the Dome audit trail into your existing SIEM. Investigations happen where your SOC already lives.
Splunk · Microsoft Sentinel · Elastic Security
APM
Observability & APM
Metrics, traces, and events export to the dashboards your operations teams already watch. Agent health alongside the rest of your platform.
Datadog · Grafana · New Relic
SOAR
Security orchestration & response
Dome events trigger your SOAR playbooks. Denial spikes, lifecycle changes, and policy regressions become automatable.
Splunk SOAR · Tines · Cortex XSOAR
CI/CD
Infrastructure-as-code & CI/CD
Every Dome operation is scriptable. Manage state declaratively, gate deployments on policy simulation, ship rules through the same pipeline as code.
Terraform · GitHub Actions · GitLab CI
Events
Audit is the record. Events are the reflex.
Every governed action lands in the audit trail — complete, immutable, retained, and carrying the full evidence. Events are the other half of that: selected facts, projected to a public contract, and delivered to the systems you already run. The split is deliberate. It keeps the audit schema free to evolve without freezing it into a public API, and it means the payload leaving Dome is public-safe by construction.
Signed, at-least-once delivery
Every event is a signed POST against a delivery ledger, with exponential backoff on failure. Verify the signature at your endpoint and dedupe on the event id.
A public, versioned contract
Events are published against a generated catalog — 55 types, each with a version, a maturity stage, and a JSON Schema. Only registry-approved fields are projected, so a webhook endpoint cannot become a PII sink.
Curated groups, not a type list
The create flow offers bundles — agent lifecycle, governance changes, security signals, incidents — so a destination can be subscribed to what it cares about without assembling event types by hand.
Destinations by preset
Point at an off-the-shelf destination by picking it and pasting a credential, rather than hand-configuring a raw webhook. Each preset carries its own form, endpoint shape, and recommended bundle.
Delivery history and replay
See exactly what was sent to each destination and what came back. Replay a failed delivery, or replay everything that failed since a point in time.
Per-destination circuit breaking
A failing destination is isolated and retried on its own schedule. One broken endpoint cannot slow or stall delivery to the healthy ones.
In practice
Subscribe a destination
Twenty-nine destination presets ship today, across automation, incident response, and observability — Slack, PagerDuty, incident.io, Jira Service Management Ops, ServiceNow, Tines, Torq, Zapier, n8n, Make, Datadog, Splunk HEC, Axiom, Elasticsearch, Sumo Logic, New Relic, Dynatrace, CrowdStrike Falcon LogScale, Google SecOps, Grafana Loki, and more. Anything not in the catalog is a custom webhook.
dome webhooks providers list
dome webhooks subscriptions create sec-ops \
--provider pagerduty \
--credential routing_key=$PD_ROUTING_KEY \
--event-type access.denied \
--event-type agent.suspendeddome webhooks subscriptions create siem \
--url https://siem.example.com/dome \
--event-type access.denied
dome webhooks deliveries list
dome webhooks deliveries replay-failed --since 24h