Mavvrik allows users to onboard GCP Billing and Usage Accounts.
Why this matters: GCP splits cost visibility and resource visibility across two different entities — a Billing Account gives you the cost data, while a Usage Account (a GCP Project) gives you the resource inventory behind that cost. Onboarding both is what lets Mavvrik show you not just what you spent, but what specifically drove it.
Billing Account
In GCP, a Billing Account is the entity that GCP invoices are generated against. Onboarding it as a Billing Account in Mavvrik gives you access to cost data across every project linked to that billing account, in one interface — instead of checking cost per-project in the GCP console.
Usage Account
A Usage Account in Mavvrik corresponds to a GCP Project. Projects are the resource containers within a GCP organization — an individual project can only belong to one organization at a time. Onboarding a project as a Usage Account gives Mavvrik visibility into the actual resources (compute, storage, etc.) running inside it, which is what powers resource-level cost attribution and optimization recommendations.