• Skip to primary navigation
  • Skip to main content
Last Week in AWS Logo
Master your cloud costs
  • About
    • Community
    • Contact
  • Blog
  • Newsletter
  • Podcasts
    • Last Week in AWS Podcast
    • Screaming in the Cloud
    • Nominate a Guest
  • Merch
  • Resources
    • AWS Network Map
sleazy car salesman
10.04.2019

You Need a Multi-Cloud Dashboard Because I Want To Sell You One

By Corey Quinn
The only vendors selling multi-cloud dashboards are the ones who’d be out of business if you didn’t buy them.
FacebookXLinkedInReddit
Home Blog You Need a Multi-Cloud Dashboard Because I Want To Sell You One
Prev
Next

If I called you and told you that your gasoline budget should be on the same dashboard as your movie ticket budget, you’d look at me like I just laid an egg. 

Why, then, do so many companies insist you need to view your GCP, Azure, and AWS spend in the same dashboard?

Different cloud providers run different workloads for your business (or at least they damn well should!) because multi-cloud for a given workload is invariably the wrong move. 

I go into this in some depth elsewhere. But today’s post is less about the poor strategic decision itself than it is the idea of having a dashboard to centralize all of your public cloud spend in the same context. 

When you’re using multiple providers, the billing dimensions are different, the confusion levels are similar, and there’s no direct comparison that makes sense at a resource level. CPU and RAM options alone vary to a point where it’s very hard to get 1:1 equivalence between instances (or virtual machines) across providers, so you’re rounding. Invariably, you’re rounding badly.

Your CFO doesn’t care what you’re spending on container orchestration. They care how big the checks you’re writing to AWS and Azure are, how much of those checks are for development versus production, and what those numbers are going to look like 18 months from now. 

The comparisons that can be exposed and shown via API aren’t the things that are relevant to a business context—and business context is something that cloud visibility dashboards are completely lacking. 

To wit, everyone’s got a metric for 500 errors. But nobody’s got a metric for how happy their users are.

It turns out there’s no API for business insight. 

My perhaps overly cynical take is that the companies selling these multi-cloud solutions have a vested interest in customers making suboptimal cloud decisions. 

If you go all in on a single cloud provider, the right dashboard answer is either “the one they provide for your use” or “picking up the phone and yelling at them until the dashboard they provide for your use meets your needs.” It’s not cutting large checks (or worse, a percentage of your cloud bill!) to third-party companies that are selling a solution for a problem you almost certainly don’t have. 

What’s worse is that as native dashboards continue to improve, third-party vendors become actively incentivised to encourage and promote multi-cloud strategies that actually  harm their customers. 

I remain steadfast in my opinion that a big driver behind multi-cloud discussions is a sea of vendors who depend on you making a poor decision. Otherwise, they have nothing to sell you. 

Corey Quinn Headshot
by Corey Quinn

Corey is the Chief Cloud Economist at Duckbill, where he specializes in helping companies improve their AWS bills by making them smaller and less horrifying. He also hosts the "Screaming in the Cloud" and "AWS Morning Brief" podcasts; and curates "Last Week in AWS," a weekly newsletter summarizing the latest in AWS news, blogs, and tools, sprinkled with snark and thoughtful analysis in roughly equal measure.

More Posts from Corey

Back to the Blog

Infinidash: AWS’s New Observability Play Has Great Bones and a Terrible Bedside Manner

By Corey Quinn

Infinidash: AWS’s New Observability Play Has Great Bones and a Terrible Bedside Manner AWS has just released something fascinating in the form of CloudWatch Omni. I want to be upfront before I dive further: “CloudWatch Omni” is a wretched name that I will not be using, so for the rest of this article and the […]

Read Moreabout Infinidash: AWS’s New Observability Play Has Great Bones and a Terrible Bedside Manner

Reading Observability Tools? That’s a Robot’s Job

By Corey Quinn

Last Thursday Honeycomb was kind enough to hand me the closing keynote slot at O11yCon, a conference whose entire premise is that observability matters and the people in the room are the ones who would know. I used that slot to argue that the primary reader of your telemetry is no longer a human, and […]

Read Moreabout Reading Observability Tools? That’s a Robot’s Job

S3 Is Not a Filesystem (But Now There’s One In Front of It)

By Corey Quinn

I’ve been saying “S3 is not a filesystem” for over a decade. I’ve said it on stages, in newsletters, on podcasts, and directly to the faces of large company employees who were too polite to tell me to shut up before they went back to their FUSE monstrosities. It was one of those reliable truths […]

Read Moreabout S3 Is Not a Filesystem (But Now There’s One In Front of It)
Billie Holding Mail Email Subscribe Icon

Get the newsletter!

Stay up to date on the latest AWS news, opinions, and tools, all lovingly sprinkled with a bit of snark.

You’re faced with tough questions about cloud costs. You should have confident answers.
Get in touch.
  • Newsletter
  • Podcasts
  • Blog
  • Merch
  • About
  • Contact
  • Disclosures
Billie Footer
footprint-orange
© 2026 L9 Labs, Inc. All Rights Reserved.
Terms of Service Privacy Policy Cookie Policy