> ## Documentation Index
> Fetch the complete documentation index at: https://docs.costgraph.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Integrations
> Connect the providers you pay and see all of your spend in one place
Your bill is spread across vendors, each with its own console, its own export, and its
own idea of what a "resource" is. CostGraph connects to the ones below, takes
your own data for anything else, and gives you one view of what you spend, what it is
spent on, and what to do about it.
Clouds, databases, AI, and developer tools, side by side.
A read-only credential per provider. Nothing to deploy, nothing to schedule.
Every view, insight, and tool covers every connected provider.
## What connecting changes
```mermaid theme={null}
flowchart LR
P1(["Clouds"])
P2(["SaaS"])
P3(["AI"])
P4(["Databases"])
P5(["Your own data"])
CG(("CostGraph"))
O1["One spend view
provider, service, team"]
O2["Insights
what moved, and why"]
O3["Savings
you can act on"]
O4["MCP
ask in your own tools"]
M1(["Your editor"])
M2(["Chat"])
M3(["Your agents"])
P1 --> CG
P2 --> CG
P3 --> CG
P4 --> CG
P5 --> CG
CG --> O1
CG --> O2
CG --> O3
CG --> O4
O4 --> M1
O4 --> M2
O4 --> M3
classDef hub fill:#0F6DFF,stroke:#0E46A0,stroke-width:2px,color:#FFFFFF,font-weight:bold
classDef source fill:#EEF4FF,stroke:#5394FD,stroke-width:1px,color:#0E46A0
classDef outcome fill:#FFFFFF,stroke:#0F6DFF,stroke-width:1.5px,color:#0E46A0
class CG hub
class P1,P2,P3,P4,P5,M1,M2,M3 source
class O1,O2,O3,O4 outcome
linkStyle default stroke:#5394FD,stroke-width:1.5px
```
Every provider you connect feeds the same place, so "what did we spend last month, and
why is it up?" stops being four consoles and a spreadsheet. It is one question, and the
answer covers everything you connected.
## Two ways to connect
Give us a read-only credential and your spend keeps itself current. This is how most
providers work, and it is the fastest way to start.
Send your billing data to us instead. Your credentials stay in your infrastructure,
and it covers anything we cannot reach: an internal chargeback system, a warehouse
job, a private cloud.
Not sure which you want? Start with a pull connection. You can add a pushed source later
without changing anything that already works.
## Providers
### Compute
Your AWS bill, down to the resource.
Your Google Cloud bill, down to the resource.
Droplets, volumes, load balancers, databases, spaces.
Every product on the bill, with Public Cloud usage per project.
Managed services, attributed per project.
Per project and per resource.
Every line item on the invoice.
Bare metal, priced per server.
Team spend, split by project.
Serverless GPU and compute, per function.
GPU pods and serverless, per GPU type.
Container build and runner minutes, with cache savings.
Dev sandboxes, priced per resource, with idle signals.
### AI and Machine Learning
Model spend sits next to infrastructure spend, so the AI line stops being a separate
argument at the end of the month.
Spend per model.
Spend per model.
One connection covers every model you route through it.
Gateway spend across every upstream provider.
Request spend across every routed model.
Team usage, per model and per member.
Grok spend per model.
Gateway spend per key, model, and team.
Enterprise LLM gateway spend, per model, with cache savings.
Self-hosted LLM gateway spend, per model and key.
Token usage from Envoy AI Gateway, agentgateway, APISIX, and vLLM, priced by us.
Character and credit usage, with unused-quota signals.
### Databases
Database spend, plus rightsizing for the databases behind it.
Per subscription and per database.
Usage cost per service, with idle/scale-to-zero signals.
### Analytics
Kafka spend per cluster and environment.
### Developer Tools
Actions minutes, Packages storage, Copilot seats.
GitHub Actions runner minutes, per runner size.
CI seats, with idle-seat signals.
Task-run cost per tenant, with failed-run waste.
### Networking
Usage across every Cloudflare product.
### Management and Governance
What Datadog itself costs you, by product.
Metrics, logs, traces, and profiles per stack.
Your CostGraph invoice, in the same view as everything else.
### Anything else
A provider we do not list, an internal chargeback system, a private cloud. Send it
yourself and it behaves like any other connected source.
## Connecting one
Open **Settings -> Integrations** and choose it from the catalogue.
The tenant decides which team or environment the charges belong to.
The form asks for exactly what that provider needs and explains the permission each
value requires. We check the credential before saving, so a wrong value fails while
you are still on the form rather than silently at 3am.
Credentials are encrypted at rest and used only to read billing data. Revoke the key at
the provider and that connection stops. Nothing else is affected.
## What you get back
A connection is not a dashboard tile. Once a provider is connected it is part of every
answer CostGraph gives:
Month-to-date and historical spend, sliced by provider, service, and team.
Spikes, waste, and drift, caught inside a provider and across providers.
Rightsizing and cheaper placements, priced before you commit to them.
Ask about any connected provider from your editor or from chat.