> 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/introduction.md).

# Introduction

Quper is a cloud intelligence platform that helps you understand what's happening across your cost, usage, allocation, and performance — and tells you what to do about it.

## The problem Quper solves

Modern engineering teams run workloads across multiple cloud providers and data platforms simultaneously. Costs accumulate across AWS, GCP, Azure, Snowflake, and Databricks — often without any single team having a clear picture of what is driving spend or how to reduce it.

Existing tools show dashboards and fire alerts. Quper goes further: it explains the root cause of every cost event and surfaces ranked, actionable recommendations so your team can act immediately — not days later.

## How Quper works

Quper connects to your cloud providers and data warehouses using secure, read-only access. Its proprietary ingestion layer maps real-time infrastructure metrics to FinOps outcomes, creating a unified semantic model of your cloud environment.

From there, Quper organises everything into four intelligent steps:

### Observe

Get a complete breakdown of every dollar spent across your cloud — by service, team, workload, and region. Quper provides granular cost attribution with daily and hourly resolution, giving you a unified view you can't get from any single provider's native billing console.

### Detect

Quper detects abnormal cost patterns the moment they emerge using ML-powered anomaly detection. Every alert comes with full context: which workload is responsible, what changed, and what it is costing per hour. You get insight before your bill arrives.

### Decide

Stop staring at charts and start acting. Quper surfaces prioritised recommendations tied directly to impact — rightsizing, idle resource termination, warehouse auto-stop configurations — so your team knows exactly what to fix and in what order.

### Govern

Set the rules. Quper enforces them. Establish team budgets, tag policies, and spend guardrails that prevent ungoverned cloud growth before it compounds into uncontrolled cost. Governance reports are exportable for finance and executive reviews.

## Supported platforms

Quper integrates with all major cloud providers and data platforms:

| Platform           | Type           |
| ------------------ | -------------- |
| AWS                | Cloud Provider |
| Google Cloud (GCP) | Cloud Provider |
| Microsoft Azure    | Cloud Provider |
| Snowflake          | Data Warehouse |
| Databricks         | Data Platform  |
| BigQuery           | Data Warehouse |

## Powered by Vidura AI

Vidura is Quper's built-in AI engine. It monitors hundreds of signals across your infrastructure in real time, performs root cause analysis on anomalies, and generates cost optimisation recommendations ranked by savings potential. Every action Quper surfaces comes from Vidura's analysis.

## Next steps

* [Quickstart](/get-started-with-quper/quickstart.md) — Connect your first cloud provider and see spend data within minutes
* [Onboarding Your Team](/get-started-with-quper/onboarding.md) — Invite users and configure role-based access
* [Integrations](/integrations/integrations.md) — Browse all supported platforms and connection guides


---

# 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/introduction.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.