> 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/get-started-with-quper/quickstart.md).

# Quickstart

This quickstart gets you connected to Quper as fast as possible. You will have live spend data and your first AI recommendations before you finish your coffee.

{% hint style="success" %}
**Estimated time: 10 minutes.** All you need is a Quper account and admin access to at least one cloud provider or data platform.
{% endhint %}

## Steps

{% stepper %}
{% step %}
**Sign in to Quper**

Log in to your Quper workspace using your credentials or your company's SSO provider. If you don't have an account yet, [book a demo](https://quper.co) to get access.
{% endstep %}

{% step %}
**Connect your first integration**

From the left sidebar, go to **Settings → Integrations** and select your cloud provider or data platform.

{% tabs %}
{% tab title="AWS" %}
Quper connects to AWS via an IAM Role. Click **Connect AWS**, then follow the CloudFormation template link to create a read-only IAM role in your account. Paste the Role ARN back into Quper to complete the connection.
{% endtab %}

{% tab title="GCP" %}
Quper connects to GCP via a Service Account. Click **Connect GCP**, download the provided setup script, and run it in your Google Cloud Shell. The script creates a service account with Billing Viewer permissions and returns a credentials JSON to paste into Quper.
{% endtab %}

{% tab title="Azure" %}
Quper connects to Azure via App Registration. Click **Connect Azure**, follow the guided App Registration steps in the Azure Portal, and paste your Tenant ID, Client ID, and Client Secret into Quper.
{% endtab %}

{% tab title="Snowflake" %}
Quper connects to Snowflake via a dedicated read-only user. Click **Connect Snowflake**, run the provided SQL commands in your Snowflake console to create the user and role, and paste your account identifier and credentials into Quper.
{% endtab %}

{% tab title="Databricks" %}
Quper connects to Databricks via a Personal Access Token. Click **Connect Databricks**, generate a token in your Databricks workspace under **User Settings → Access Tokens**, and paste it into Quper along with your workspace URL.
{% endtab %}

{% tab title="BigQuery" %}
Quper connects to BigQuery via a Service Account. Click **Connect BigQuery**, create a service account in Google Cloud IAM with BigQuery Data Viewer and Job User roles, download the key JSON, and upload it to Quper.
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Quper uses **read-only access only**. No write permissions are ever requested or required.
{% endhint %}
{% endstep %}

{% step %}
**Wait for initial data ingestion**

After connecting, Quper begins pulling your billing and usage data. Initial ingestion takes **15–30 minutes** depending on account size and how much historical data is available.

You will see a progress indicator in the Integrations panel while ingestion is running. Quper automatically pulls the last 90 days of historical data on first connection.
{% endstep %}

{% step %}
**Explore your Spend Overview**

Once data is ready, navigate to **Observe → Spend Overview**. You will see:

* Total spend this week vs. last week
* Spend breakdown by service, account, and region
* Top services by cost
* Any anomalies detected during initial ingestion

{% hint style="info" %}
If Quper detected cost anomalies in your historical data, they will appear in the **Detect → Anomalies** feed immediately.
{% endhint %}
{% endstep %}

{% step %}
**Review Vidura AI recommendations**

Go to **Decide → Action Intelligence** to see your first set of AI-generated optimisation recommendations. Each recommendation shows:

* The resource and the issue
* Estimated monthly savings
* One-click action to apply the fix

Start with the highest-impact items at the top of the list.
{% endstep %}
{% endstepper %}

## What's next?

{% content-ref url="/pages/s9E2om8uuZV2syNKp8x5" %}
[Onboarding Your Team](/get-started-with-quper/onboarding.md)
{% endcontent-ref %}

{% content-ref url="/pages/N4tcuOR4EmJ5TdaBrFli" %}
[Overview](/integrations/integrations.md)
{% endcontent-ref %}

{% content-ref url="/pages/wrP7JAym5GYlfGlga9yd" %}
[Cost Governance](/user-guide/govern/cost-governance.md)
{% endcontent-ref %}


---

# 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/get-started-with-quper/quickstart.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.