Choose the task in front of you
Each topic has one canonical guide. Begin with the outcome you need, then follow the links in the navigation rail or search the full documentation.
Start with trusted cost
- Getting started takes you from workspace access to a first verified cost view.
- How PruneFox reads cost explains source authority and normalized evidence.
- Cost basis and financial meaning keeps net, billed, amortized, credits, and tax distinct.
- Data freshness and completeness explains completed, partial, stale, and missing periods.
Connect and maintain data sources
- Connect a data source covers the bounded connection lifecycle.
- Manage data-source connections covers health, recovery, rotation, and revocation.
- Provider guides explain the source-specific boundary.
Explore and explain spend
- Cost overview establishes the financial state and evidence boundary.
- Spend Explorer follows source-backed drivers.
- Provider dimensions explains which breakdowns a source can support.
- Saved Views preserve an authorized recurring analysis.
Plan, detect, and govern
- Budgets, forecasts, anomalies, and alerts help teams set limits and investigate material change.
- Roles and permissions, plans and billing, account security, and offboarding explain workspace control.
Provider guides
Choose a provider to understand its authoritative financial source, safe access boundary, supported cost bases, useful dimensions, and known limits.
- Google CloudDetailed Cloud Billing export
- AWSCost and Usage Report 2.0 manifests and report objects
- Microsoft AzureCost Details or scheduled Cost Management Exports
- Oracle CloudOCI proprietary or FOCUS Cost Reports
- VercelTeam billing charges and validated billing or usage records
- DatadogEstimated current-period and settled historical cost or usage reports
- OpenAIOrganization cost reports with usage attribution when supplied
- AnthropicOrganization cost report with usage attribution when supplied
Developer Productivity
Developer Productivity is a separate governed domain for AI coding-tool adoption, provider-reported usage and cost, and delivery signals. It does not collect prompts or source code, and it does not score employees.
Understand Developer Productivity
Safe use
Customer identity, staff access, provider credentials, and public requests stay separate. Enter connection details only in the signed-in product flow. When you need help, share the provider name, affected date range, visible safe error, and expected outcome—never credentials, raw billing exports, payment data, or customer records.