Why it matters
Today every cloud provider's billing export has its own column names, semantics, and edge cases. FOCUS aims to standardize the columns (BilledCost, EffectiveCost, ServiceName, ProviderName, etc.) so tools can be built against one schema instead of N.
Adoption status
AWS, GCP, Azure, and Oracle Cloud all participate in the working group. FOCUS-aligned exports are emerging across providers; tooling is catching up. The spec is still evolving — pin a version when integrating.
Who tovin.io is for
Frequently asked
Is FOCUS a replacement for CUR or BigQuery export?
Long term, yes — FOCUS-aligned exports are intended to replace the provider-specific schemas. Short term, both formats will coexist as adoption ramps.
Should I wait for FOCUS before building?
No. FOCUS is the long-term direction but provider-specific adapters will still be needed for years. Build against today's exports and migrate as FOCUS-aligned outputs become available.