Usage and billing
Review resource consumption, allocation, estimates, and budget notifications.
Usage views attribute infrastructure consumption to organizations, projects, regions, and labels. Billing separates the Infra subscription from hosted resource charges and externally operated hardware costs.
Usage categories
Hosted compute uses the allocated size and applicable running interval. Persistent storage uses provisioned capacity, while recovery data follows its storage class and retention. Address reservations and network services have their own usage categories.
The subscription covers the organization plan, seats, and support agreement. Owned fleet resources can use configured internal rates for allocation reports without becoming hosted compute charges. Keep subscription and internal cost allocation separate when reconciling a provider invoice.
The applicable agreement defines billable units and rates. Console estimates use the rate information available for the selected resources and are not a replacement for the invoice.
Project allocation
Open Organization → Usage and group by project, region, resource type, or allocation label. Resource IDs remain available when names change. Internal rates can assign a cost model to owned capacity without creating a hosted charge.
A resource without an allocation label remains in an unassigned category. Adding a label affects subsequent allocation views; it does not rewrite an issued invoice. Review label policy before relying on it for internal cost distribution.
Stopped and retained resources
A stopped droplet can retain persistent disks, reserved public addresses, and backup copies. Those resources continue consuming capacity and can continue incurring charges. Deleting the droplet does not automatically remove every independent resource.
Use the project inventory to find unattached volumes, unused addresses, retained images, and expired recovery data. Follow their deletion and retention workflows before assuming cleanup is complete.
Budgets
Open Organization → Usage → Budgets → Create budget and choose an organization, project, or allocation label. Set the currency, period, amount, and notification thresholds. A threshold event sends a notification when measured or forecast usage crosses the configured value.
A budget is an alerting rule. It does not stop droplets or reject new resources. Use quotas and an explicitly configured admission policy when an organization requires resource limits.
Usage can arrive after the resource action occurred. A budget threshold can be crossed before the notification is delivered. Monitor resource reservations alongside monetary estimates for fast-changing deployments.
Export and reconciliation
Export a bounded period with resource IDs, allocation labels, quantities, and available rate information. Compare the period and units with the invoice or internal accounting system. Corrections appear as adjustments rather than silent edits to a previously issued billing record.
Billing Viewer access is sufficient for usage and invoice inspection. It does not grant permission to stop workloads or change project quotas. See Roles and teams.
Reserved capacity distinguishes pricing commitments from physical headroom. Spend caps add explicit admission controls; ordinary budget alerts remain notifications and do not enforce those caps.
Rate references
Use Organization → Billing → Pricing for the applicable price card. Pricing separates subscription from resource usage; compute prices list hardware configurations, and service prices cover retained data, traffic, and networking. Worked examples include persistent resources and discounts.