Integrations
What CloudJaeger reads today — and what it does not, yet.
Every integration carries exactly one status, generated from our evidence rather than from marketing copy: works → Live, works in part → Preview, sample estate only → Demo-only, coming next → Planned.
Showing what you can use today; Planned ones are listed once, below. No logos, no endorsement implied.
Cloud billing
5 available now
- Cloud billingLive
Amazon Web Services
Daily cost by service and region, plus a nightly resource inventory, through a read-only IAM role.
- Needs from you
- A read-only IAM role, deployed from our CloudFormation or Terraform template.
Daily billing works on real bills; the nightly inventory sweep reads the regions on your bill, up to 20 per account. See every action the role allows.
- Cloud billingPreview
Microsoft Azure
Cost Management query by subscription, region-grained.
- Needs from you
- A service principal with Cost Management Reader and Reader on the subscription.
Real cost and inventory sync; not yet checked against a real Azure bill.
- Cloud billingPreview
Google Cloud
Your Cloud Billing export in BigQuery.
- Needs from you
- The billing export switched on, and a service account with BigQuery Data Viewer and Job User.
Real cost and inventory sync; not yet checked against a real Google Cloud bill.
- Cloud billingPreview
AWS Cost and Usage Report (CUR 2.0)
Your detailed AWS bill, line by line, from the CUR 2.0 export in your own S3 bucket, queried through Athena.
- Needs from you
- A CUR 2.0 export to S3. The role's one opt-in write is Athena query results into the bucket you name.
Ran again in production on 27 September 2026. See where its August check stands.
- FilePreview
FOCUS or CUR file upload
A FOCUS or AWS CUR billing file from any cloud, read once.
- Needs from you
- Nothing to install — export a file and upload it.
Single-file totals are exact; use one file per workspace for now, and an upload cannot be deleted yet.
Alerts and workflow
4 available now
- AlertsPreview
Slack
Per-sync spend and anomaly alerts to a channel.
- Needs from you
- An incoming-webhook URL.
Budget alerts and digests do not send yet.
- AlertsPreview
Microsoft Teams
The same per-sync spend and anomaly alerts, to a Teams channel.
- Needs from you
- A Teams Workflows webhook URL.
Same coverage as Slack.
- AlertsPreview
Email
Per-sync spend and anomaly alerts by email.
- Needs from you
- An address per recipient, inside your workspace's allowed email domains.
Scheduled digests do not send yet.
- AlertsPreview
PagerDuty
The same per-sync spend and anomaly alerts, as PagerDuty events.
- Needs from you
- An Events v2 routing key.
Same coverage as Slack.
Data and developer
4 available now
- DeveloperLive
REST API
Costs, recommendations, anomalies and budgets as JSON.
- Needs from you
- An API key, created behind a password re-check.
Documented in full, signed out. Read the API reference.
- AI agentsPreview
MCP server
Key-based MCP answers agree to the cent with the web app.
- Needs from you
- An API key with a read scope. OAuth for third-party clients is still unfinished.
Draft tools can only propose; a signed-in admin confirms. Read the MCP reference.
- ExportPreview
FOCUS export
Your spend from every connected cloud, in FOCUS columns, as a CSV or JSON download.
- Needs from you
- Nothing to set up: download it from the FOCUS export page in the app.
Azure and Google Cloud rows carry no resource id, and euro invoices are exported converted to US dollars.
- KubernetesPreview
Kubernetes agent
Daily per-workload usage from your cluster's own Prometheus, sent by one nightly CronJob.
- Needs from you
- A Helm install in your cluster, with Prometheus in it. No Kubernetes API access, no RBAC.
Proven on a lab cluster; workload costs are priced on EKS only.
AI, SaaS and identity
1 available now
- AI spendPreview
OpenAI and Anthropic usage
Tokens and cost by model, feature and tenant, pushed from your code.
- Needs from you
- The SDK, OpenTelemetry GenAI spans or LiteLLM logs.
The daily pull from the providers' admin APIs is switched off; usage arrives by push.
Planned8 integrations are Planned — not in v1
- Jira Cloud
- ServiceNow
- Outbound webhooks
- GitHub pull-request cost checks
- Warehouse export
- SaaS vendor bills
- Utilisation metrics
- SSO and SCIM
Some exist in the product unfinished; none is part of v1.
Statuses as of 2026-10-15: our 2026-09-25 feature acceptance register, checked again against the code. AWS, Amazon Web Services, Microsoft Azure, Microsoft Teams, Google Cloud, Slack, PagerDuty, Jira, ServiceNow, GitHub, OpenAI, Anthropic and Kubernetes are trademarks of their owners; no affiliation or endorsement is implied.
Need an integration marked Planned? Try the product on the sample estate, then tell us which — design partners help set the order.
Open the live demo — no signupApply for a design partner slot