Free — no signup required

Introduction: The Tower of Babel

2 min read

The Multi-Cloud Nightmare

Imagine you are the CTO of a company that uses AWS, Azure, and Google Cloud. You ask a simple question: "How much did we spend on virtual machines yesterday?"

To answer this, your data team has to query three different billing files:
1. AWS: They look for AmazonEC2 in the lineItem/ProductCode column and sum lineItem/UnblendedCost.
2. Azure: They look for Virtual Machines in the MeterCategory column and sum PreTaxCost.
3. Google: They look for Compute Engine in the Service.Description column and sum Cost.

This is the Tower of Babel problem. Every cloud provider speaks a different billing language — different column names, different date formats, different ways of representing discounts. Building a unified cost dashboard requires massive, fragile data engineering pipelines that must be maintained every time a provider changes their export format.

Enter FOCUS

FOCUS (FinOps Open Cost & Usage Specification) is an open-source project governed by the FinOps Foundation (a Linux Foundation project) that solves this problem directly. It defines a standard schema — a shared vocabulary — for cloud billing data.

If all clouds output FOCUS-compliant data, you only need to write one query to answer the virtual machine question across all providers:

SELECT SUM(BilledCost)
FROM focus_billing_data
WHERE ServiceCategory = 'Compute'
  AND ChargePeriodStart >= CURRENT_DATE - INTERVAL '1 day'

That single query replaces three provider-specific queries, three separate pipelines, and three sets of tribal knowledge. FOCUS normalizes the chaos into a single, predictable format that any tool or analyst can consume.

Why a Standard Matters Beyond Convenience

The real value of FOCUS is not just fewer SQL queries. It is the ecosystem effect. When billing data has a standard schema, third-party FinOps tools (Vantage, CloudHealth, Apptio, open-source dashboards) can be built once and work everywhere. Vendors compete on features and insights rather than on who can parse the most billing formats. This is the same reason HTTP and JSON unlocked the web API economy — a shared contract enables an ecosystem.

Interview Tip

Interviewers at companies with multi-cloud environments often ask: "How would you build a unified cost reporting system across AWS and Azure?" The wrong answer is to describe custom ETL pipelines for each provider. The right answer starts with FOCUS: adopt a standard schema so your reporting layer is provider-agnostic. Mention that AWS, Azure, and GCP have all committed to FOCUS-compliant exports, making this a realistic architectural choice today, not a future aspiration.

This is one of 18 chapters

Every chapter is free — Kubernetes, Terraform, SRE, distributed systems, and more — with fast daily review built in.

Sign up free