Cloud: 9 read-only integrations
Each page lists the exact tools Triagic exposes and the mechanism that keeps them read-only. Setup steps for every one live on the cloud docs page. 14-day trial, no card.
- AWS CloudWatchRead CloudWatch logs, metrics, and alarms.18 tools
- AWS SQS / SNSInspect queues, topics, and message attributes.20 tools
- Azure MonitorQuery Log Analytics and Application Insights with KQL, and read metrics and the activity log.annotation-vetted tools
- AzureAsk about any Azure service the service principal can read: compute, storage, SQL, Cosmos, AKS, App Service, Monitor and more. Runs the Azure MCP server read-only; Key Vault values are never exposed.35 tools
- Google Cloud LoggingSearch Cloud Logging entries and read Cloud Monitoring metrics, alert policies, and traces.13 tools
- CloudflareQuery Workers Observability logs and analytics at the edge, read-only. Connects to Cloudflare's hosted server.8 tools
- OktaLook up users, their groups and app assignments, and the system log, including recent failed sign-ins. Useful for “can't log in” tickets. Nothing can be changed.12 tools
- AWSAsk about any AWS service the IAM policy allows: EC2, S3, Lambda, RDS, ECS, CloudTrail, IAM and the rest. Runs the AWS API server locked to read-only operations.annotation-vetted tools
- VercelRead deployments, build and runtime logs, projects and Web Analytics. Connects to Vercel's hosted server. Writes are not blocked. Use a token scoped to what you want reachable.20 tools
Connect one and ask it something
Install the desktop app, add a read-only credential for one system, and run a real investigation against it.