CDN and edge spend is easy to lose track of. Fastly bills on its own, off to the side of your cloud invoice – real money, often significant, sitting where none of your cost tooling reaches. So it stays its own island: a lump sum with no easy way to tie it back to the teams, products, and customers driving the traffic.
What we built
A native Fastly connector. Connect a read-only Fastly token and CloudZero ingests your CDN and edge compute spend the way Fastly actually structures it – by service, region, and usage type (bandwidth, requests, duration), not the single lump sum on the invoice. No custom integration, no pipeline to maintain, and it’s generally available now.
How it works
Create a read-only token in Fastly, add it in your CloudZero connector settings, and the first spend lands in Explorer within about a day. From there it behaves like every other source: allocate it with CostFormation by team, product, and customer, fold it into budgets and anomaly detection, and see it next to your cloud and SaaS spend instead of in a CDN bill of its own.
Read more in the CloudZero documentation →
