Multi-cloud bill translator for engineering teams

The moment this becomes urgent: a startup is running workloads across two or three cloud providers — maybe AWS for most things, Alibaba for APAC, Akamai for edge — and the finance team asks why last month's bill jumped 30%. Nobody on the engineering team can actually answer that clearly because each provider formats billing data differently, uses different unit names, and applies regional pricing in ways that aren't normalized anywhere.

The gap persists for a structural reason: each cloud provider has a strong incentive to make their own billing look favorable but no incentive to help you compare it against a competitor. Their native dashboards are designed around their own SKUs, not your workload categories. So the comparison work always falls to someone manually exporting CSVs from three portals and trying to reconcile them in a spreadsheet — which is exactly what the complaints describe when users ask for 'a graph that compares each month's spending.'

What makes existing approaches fall short isn't that the data is unavailable — it's that the normalization layer doesn't exist. One provider charges per GB-hour, another per instance-minute, another bundles network egress differently by region. The complaint about 'prices are different across regions which makes billing calculations more difficult' is a direct symptom of this: there's no single place where you can see 'here's what this workload costs you in us-east-1 vs ap-southeast-1 vs Alibaba Shanghai, normalized to the same units.'

This is a business because the problem recurs every billing cycle. Engineering managers who approve cloud spend can't currently defend or challenge a bill without doing manual work each month. When a provider silently changes pricing — as several complaints describe ('price changes after you renew, despite the marketing site making it seem like the permanent price') — there's no alert, no audit trail, no diff. That costs real money in missed optimization and in finance team time chasing down explanations.

What to build

Ingest billing exports from AWS, Alibaba Cloud, and Akamai via their respective billing APIs, normalize SKUs and usage units into a common schema, and render a month-over-month diff view that flags line items where unit price changed without a user-initiated upgrade.

Where to start

Start with teams already exporting Alibaba Cloud and AWS bills to S3 or OSS for compliance reasons — they already have the raw data accessible and are most likely to feel the cross-provider confusion acutely, since Alibaba's billing structure is the most foreign to teams whose baseline mental model is AWS.

The hard part

Keeping the normalization schema current is operationally painful — cloud providers update SKU names, introduce new charge types, and change billing export formats without warning, which means the data pipeline breaks silently and erodes user trust fast.

How it makes money

Monthly subscription per workspace, priced at a flat rate up to a cloud spend threshold (e.g., under $50k/month) then a small percentage of tracked spend above that, so it scales naturally with the customer's growth without a per-seat model that penalizes team size.