AInforce
Architecture

Choose the access your review needs.

Browser monitoring, runtime inspection, and connected data sources have different deployment and privacy requirements. Do not assume one setup provides the coverage of another. Agree the scope before connecting production systems.

Browser extension

Managed browser installation

Administrators configure the distributed extension on managed browsers. It reports catalogue domain matches and optional attribution metadata. Local model-setting diagnostics are limited to the supported AInforce configuration-linter page; they do not inspect arbitrary pages or collect prompts.

Review: permissions, employee notice, attribution settings, and browser coverage

API gateway

Application security

Runtime inspection requires routing supported application traffic through a configured control path. Confirm the provider, API format, inspection behavior, latency, and failure handling during evaluation. Traffic outside that path is not covered.

Review: provider support, routing changes, data processing, and enforcement tests

Enterprise integration

Scope before connecting

Agree the identity, event-delivery, and workflow connections needed for your environment. Confirm the connector, permissions, data mapping, and delivery behavior before granting access. A requested integration is not a promise of native support.

Review: availability, permissions, data freshness, and operational ownership

Detailed documentation

Full architecture diagrams, data flow documentation, network requirements, and SDK references are available in the product documentation. Contact your account team for access during evaluation.