Maybe I'm late to this, but I finally spent time comparing CUR and FOCUS (CUR 2.0 exposes ~115-131 fields, while FOCUS exposes ~60 ... but theres more)
Maybe I'm late to this, but I finally spent some time looking through the CUR 2.0 and FOCUS exports side by side.
One thing that stood out:
CUR 2.0 exposes roughly 115-131 available fields depending on export options and enabled billing features.
FOCUS exposes roughly 60.
At first that sounded like:
"CUR has more detail."
But the more I looked at it, the more it felt like they're solving different problems.
CUR preserves a lot of AWS-specific concepts:
- Resource IDs
- Split Cost Allocation
- Savings Plans
- Reserved Instances
- Capacity Reservations
- IAM Principal allocation
FOCUS seems more interested in creating a common language for cloud costs.
The mental model that clicked for me was:
CUR is for fidelity.
FOCUS is for consistency.
I'm curious what people are actually doing in production.
Are you:
- Running both?
- Moving toward FOCUS?
- Still primarily living in CUR?
Genuinely interested. I feel like FOCUS adoption is one of those things that sounds very different in conference talks than it does in real environments.