Skip to content
Trust Center

Evaluate the boundary before you put it in the path.

AgenticDome can sit in a sensitive execution path. This page states the public operating boundary plainly and separates available controls from items that depend on deployment design or contract.

No certification theatre: readiness material is not a SOC 2 report or an ISO/IEC 27001 certification claim. We will not represent an assessment, certification, latency target, or service commitment that has not been independently completed or contractually agreed.

Identity and tenant boundaries

Use trusted workload and user identities from your existing provider or AgenticDome-issued identities for approved deployments. Runtime keys identify the tenant connection; verified caller tokens establish the acting identity.

Gateway and SDK calls use tenant-scoped policy. Identity management includes deployment review, credential rotation and revocation with retained history.

Explore Agent Identity

Abi conversations and privacy

Abi sessions are scoped to the signed-in customer organisation and user. Provider permissions, retention and processing disclosures follow the organisation's configured settings.

Before starting, customers see the session disclosure and consent choice. Abi prepares deployment advice and blueprints for review; production changes follow the team's own approval process.

Meet Abi

Data path and content

The gateway evaluates requests routed through its configured service boundary. SDKs and plugins contribute context from connected application hooks. That context can include caller identity, task context, tool names, arguments and destinations.

Data handling follows the selected deployment and integration. Review content fields, retention and provider processing for the workflow being protected.

Confirm the exact payload during design review

Failure behavior

Failure behavior is configured for the integration and risk tier. Production-sensitive actions can fail closed; development or lower-risk paths can be configured to fail open. Timeouts, retries, and fallback behavior must be tested before production rollout.

Configurable by deployment

Latency

AgenticDome is optimized to make decisions inline at runtime. Warming, bounded deterministic checks, and region-aligned deployment are intended to keep AgenticDome processing overhead to a few milliseconds on eligible paths. End-to-end latency can be higher because it includes network distance, proxies, and payload size.

Low-overhead design · workload measurement required

Deployment and residency

Managed regional, dedicated, and customer-controlled patterns may be available according to plan and architecture. Data location, retention, deletion, backup, and support-access requirements are confirmed for the selected design rather than implied sitewide.

Plan and contract dependent

Assurance and procurement

  • Security and architecture material is shared at the appropriate review stage.
  • DPA, subprocessors, retention terms, support targets, and service commitments are confirmed in the applicable agreement.
  • Published marketing content is not a substitute for contractual terms.

Vulnerability disclosure

Report a suspected vulnerability to info@agenticdome.io with “Security Vulnerability Report” in the subject. Do not access other customers’ data, disrupt service, or include secrets in ordinary email. We will coordinate an appropriate secure exchange channel.

Machine-readable security.txt

Start an enterprise review

For a deployment diagram, exact data-flow review, retention requirements, DPA or subprocessor questions, and contractual service requirements, book a deployment review. For an active customer issue, use Support.