> For the complete documentation index, see [llms.txt](https://docs.quper.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quper.co/integrations/integrations.md).

# Overview

Quper connects directly to your infrastructure using secure, read-only access — with no agents to install and no disruption to your existing setup.

## Supported integrations

### Cloud Providers

Connect your cloud billing to Quper to get a unified view of compute, storage, networking, and managed service spend across all your accounts and regions.

| Provider                                                   | What Quper tracks                                                                              |
| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| [AWS](/integrations/cloud-providers/aws.md)                | EC2, RDS, Lambda, S3, EKS, and all other AWS services via Cost and Usage Reports               |
| [Google Cloud (GCP)](/integrations/cloud-providers/gcp.md) | Compute Engine, BigQuery, Cloud Storage, GKE, and all GCP services via Billing Export          |
| [Microsoft Azure](/integrations/cloud-providers/azure.md)  | Virtual Machines, Azure SQL, Blob Storage, AKS, and all Azure services via Cost Management API |

### Data Warehouses & Platforms

Connect your data platforms to Quper to track query costs, warehouse utilisation, and job-level spend in real time.

| Platform                                                                | What Quper tracks                                                                                    |
| ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| [Snowflake](/integrations/data-warehouses-and-platforms/snowflake.md)   | Warehouse credits, storage costs, query spend, idle compute, and credit consumption by user and role |
| [Databricks](/integrations/data-warehouses-and-platforms/databricks.md) | Cluster spend, job costs, DBU consumption, idle clusters, and cost by workspace and team             |
| [BigQuery](/integrations/data-warehouses-and-platforms/bigquery.md)     | Slot consumption, on-demand query costs, dataset storage, and spend by project and user              |

## How integrations work

Quper pulls data from each connected platform on a regular cadence:

* **Cloud providers** — billing and usage data is refreshed every 24 hours, with real-time usage signals updated every hour
* **Data warehouses** — query-level cost data is updated every hour; storage data is updated every 24 hours

After connecting a new integration, Quper automatically backfills **90 days** of historical cost and usage data.

## Adding a new integration

1. Go to **Settings → Integrations**
2. Click **Add Integration**
3. Select your provider or platform
4. Follow the step-by-step connection guide

Each integration requires read-only credentials only. Quper never requests or stores write access to your infrastructure.

## Removing an integration

1. Go to **Settings → Integrations**
2. Find the integration you want to remove
3. Click the options menu (⋯) and select **Disconnect**
4. Confirm the disconnection

After disconnecting, Quper retains your historical cost data but stops ingesting new data from that source.

{% hint style="info" %}
You can reconnect a previously disconnected integration at any time. Quper will resume data ingestion from the point of reconnection and backfill any gap in data.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.quper.co/integrations/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.