Overview
Connect Quper to your cloud providers, data warehouses, and data platforms.
Last updated
Was this helpful?
Connect Quper to your cloud providers, data warehouses, and data platforms.
Quper connects directly to your infrastructure using secure, read-only access — with no agents to install and no disruption to your existing setup.
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.
EC2, RDS, Lambda, S3, EKS, and all other AWS services via Cost and Usage Reports
Compute Engine, BigQuery, Cloud Storage, GKE, and all GCP services via Billing Export
Virtual Machines, Azure SQL, Blob Storage, AKS, and all Azure services via Cost Management API
Connect your data platforms to Quper to track query costs, warehouse utilisation, and job-level spend in real time.
Warehouse credits, storage costs, query spend, idle compute, and credit consumption by user and role
Cluster spend, job costs, DBU consumption, idle clusters, and cost by workspace and team
Slot consumption, on-demand query costs, dataset storage, and spend by project and user
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.
Go to Settings → Integrations
Click Add Integration
Select your provider or platform
Follow the step-by-step connection guide
Each integration requires read-only credentials only. Quper never requests or stores write access to your infrastructure.
Go to Settings → Integrations
Find the integration you want to remove
Click the options menu (⋯) and select Disconnect
Confirm the disconnection
After disconnecting, Quper retains your historical cost data but stops ingesting new data from that source.
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.
Last updated
Was this helpful?
Was this helpful?

