Sources
Find the source behind the spend.
Compare reporting scope and setup status across the public sources in this catalog. Start with the evidence your team needs, then confirm availability for your workspace.
Cloud
Billing exports and cost reports, with account and resource scope.
Google CloudReporting detailDetailed Cloud Billing exportGuided setup; source and workspace dependent
Billing account, project, service and SKU; resource fields depend on the export and service. Credits and later corrections retain their source context.
Read Google Cloud reporting detailAWSReporting detailCost and Usage Report 2.0Guided setup; source and workspace dependent
Payer and linked accounts, service and operation. Resource visibility depends on CUR 2.0 configuration; revised report partitions retain their context.
Read AWS reporting detailMicrosoft AzureReporting detailCost Details / Cost Management ExportsGuided setup; source and workspace dependent
Billing scope, subscription, resource group and service. Actual and amortized cost are alternative views and are not added together.
Read Microsoft Azure reporting detailOracle CloudReporting detailCost ReportsPlanned; setup not offered
Cost Reports describe tenancy, compartment, service and resource scope. Do not create credentials, policies or report locations for PruneFox. No setup, connection or test action is offered.
Read Oracle Cloud reporting detailPlatforms and services
Reported team charges, current estimates and settled cost reports.
VercelReporting detailTeam billing charges and usage recordsGuided setup; source and workspace dependent
Team, charge type and usage period; project, region and resource identity appear only when supplied.
Read Vercel reporting detailDatadogReporting detailEstimated and settled cost reportsGuided setup; source and workspace dependent
Organization, sub-organization, product and pricing category. Current-period estimates stay provisional; settled historical cost supersedes them.
Read Datadog reporting detailDirect AI
Organization cost reports with their supplied usage attribution.
OpenAIReporting detailOrganization cost reportsGuided setup; source and workspace dependent
Organization, project and line item, with model usage attribution when supplied. Usage does not independently prove billed cost.
Read OpenAI reporting detailAnthropicReporting detailOrganization cost reportsGuided setup; source and workspace dependent
Organization and workspace cost, with model and token attribution when supplied. Null or default workspace attribution stays explicit.
Read Anthropic reporting detailChoose the evidence that matches your question.
A source can report a bill, a reference-price view or native consumption. Those scopes support different reviews; catalog inclusion does not activate a source.
| Reporting scope | Useful for | Keep explicit |
|---|---|---|
| Provider-reported billed or net cost | Reviewing compatible charges and financial movement. | Currency, basis, period, corrections and supplied attribution. |
| Estimated cost | Reading a current reporting estimate in its own scope. | Estimated status; do not blend it with a settled report. |
| List-cost scope | Reviewing usage at supplied reference prices. | List cost is distinct from invoiced or contracted cost. |
Bring the sources you need to an evaluation.
Discuss the billing accounts, reporting periods and review questions that matter to your team. Availability is confirmed during evaluation; inclusion in this catalog does not activate a source.
Discuss source coverage