AWS Cloud Intelligence
Connect a customer-owned AWS account with a read-only cross-account role. AntOps never requests access keys and never changes AWS resources.
Open guideSELF-SERVICE GUIDES
Connect a customer-owned AWS account with a read-only cross-account role. AntOps never requests access keys and never changes AWS resources.
Open guideDelegate a customer-owned Azure subscription or resource group through Azure Lighthouse with the built-in Reader role only.
Open guideRun deterministic analysis for selected static files from a pull request. AntOps does not run Docker builds, start containers or apply Terraform.
Open guideUse Change Risk to inspect selected Dockerfile and compose configuration changes without executing their contents.
Open guideCreate a named workspace key only when a programmatic integration needs it, then store it in the destination’s secret manager.
Open guideConnect selected repositories to deterministic Change Risk checks without granting repository administration, Actions, secrets or organization-member access.
Open guideDeliver AntOps notifications to a Slack incoming webhook you control.
Open guideDeliver real AntOps events to a public HTTPS receiver with a destination-specific signing secret.
Open guideUse the published bounded stdio MCP server from a local MCP client with a workspace API key.
Open guideUse the published AntOps command-line client with a workspace API key kept outside command history and source control.
Open guideCall the production API from Python through the published client and a workspace API key.
Open guideCall the production API from TypeScript through the published client and a workspace API key.
Open guideWorkspace owners can upload an extractable text-layer PDF or UTF-8 text file in AntOps, review deterministic masked findings, and create a sanitized text derivative on eligible plans. A server-side API path remains available for programmatic workflows.
Open guide