Integrations and exports
Where CloudIQ findings go. Jira, GitHub, Slack, email, an MCP endpoint for your own AI tools, CSV and PDF exports, and single sign-on.
A finding is worth most when it reaches the people and systems responsible for acting on it. CloudIQ integrates with the tools your team already uses.
| Integration | What it does |
|---|---|
| Jira | Creates tickets from any finding: per resource, in bulk, or grouped by category. Ticket status syncs back to the task |
| GitHub | Opens Terraform pull requests in weekly bundles. Resources already managed in Terraform are detected, so the generated code aligns with your configuration |
| Slack | Delivers scheduled insight digests, configured in plain language through Fini |
| Sends scheduled reports and platform notifications through standard SMTP | |
| MCP | Lets AI assistants such as Claude, Cursor and ChatGPT query your cost data, using an API key per customer. See Connect an AI assistant |
| Exports | Engineer-ready CSV for every module, PDF and runbook export for task queues, and finance-ready savings reports by ledger stage |
| Identity | Self-service single sign-on with your identity provider (OIDC), multi-factor authentication, five product roles, and a readable audit log |
Scope and cadence#
Each customer's data is isolated in its own tenant, your organization's CloudIQ workspace. Access can be scoped and pinned at the account and project level, so a team sees its own accounts. AWS environments receive daily audit runs and hourly anomaly alerts, and each audit shows what changed since the previous one.
Who configures what#
Integrations and API keys are managed by tenant administrators. The five product roles separate viewing findings, acting on them, and administering the tenant.
Next#
Try this against your own spend
A free savings analysis runs the checks described in these docs against your AWS or Google Cloud account and returns a ranked list of priced findings.