Earlier this year, Gartner published a report called “How to Manage and Optimize Costs of Public Cloud IaaS and PaaS.” Overall, we agreed with the piece and wrote a blog post about what they get right (and where they miss). However, one thing that stood out to us is how many aspects of optimization Gartner described as very difficult — which CloudZero can help make easier.

Earlier this year, Gartner published “How to Manage and Optimize Costs of Public Cloud IaaS and PaaS,” by analysts Marco Meinardi and Traverse Clayton. As a company that is focused on enabling engineering teams with cloud cost intelligence, we were of course curious what they had to say. Now, if you are familiar with Gartner, you know they have a reputation for serving enterprise clients, so they can sometimes be — well, enterprisey.

Multi-tenancy is one of the key properties of any effective SaaS solution. It gives companies the economies of scale, elasticity, and operational efficiency to offer competitive products with strong margins. However, multi-tenancy has a tradeoff: cost visibility. Because customers share AWS resources in multi-tenant architecture, the billing data shows the resources you’ve utilized, but not by who or to do what. It’s possible to build this kind of visibility in.

Every CEO is looking for an edge. Every change in IT — whether we’re talking about the move away from company owned data centers to VMs, or the latest digital transformation we’re seeing today — has always been about gaining a strategic advantage. Companies want to do more at a lower cost, and they want the freedom to pivot quickly without fixed costs.

In the context of businesses, the ultimate goal of innovation for technology companies is to drive a profit. This means that even though many software engineering problems can be solved with enough time and budget — just because a business can solve a problem doesn’t mean that they should. Sometimes, even once a team has figured out how to solve an engineering problem, it doesn’t make sense to deploy the solution — because it costs so much to operate.

Every year, I look forward to the release of the annual State of DevOps report (that’s the kind of exciting life I lead!). The evolution and adoption of DevOps in the past decade has been incredible — and this report always helps show what’s the next big thing that high-performing teams are adopting. The 2020 State of DevOps report was just released a couple weeks ago and as usual, it was filled with all kinds of insights.

If your business is growing, your AWS bill is probably growing with it. Yet, in conference rooms all over the world (or Zoom calls, these days), CFOs are asking “we’re spending how much?!” — while engineering leaders try to explain that the platform is twice as fast and they’ve added some machine learning that is going to absolutely change the game.

On a day-to-day basis, both engineering and product management in software companies involves constant trade-offs. Everyone has a long backlog of tasks and needs to make decisions about what to prioritize on a daily, weekly, and monthly basis. Figuring out what to tackle first, what to put off for later, and what to say no to is critical both to managing daily workloads as well as to creating product roadmaps that reflect what customers want.

This month, I made the decision to join CloudZero as their new chief revenue officer — a choice I’m incredibly excited about. In the past week, a number of colleagues have asked me to share why I joined the company. After answering the question a few times, I decided to take a minute to collect my thoughts and explain why this incredible company is the next step in my career.

It’s safe to say that cost per tenant (also known as cost per customer) on AWS has been a challenging metric to obtain. Until now, your best bet has usually been to either make a best guess or build some sort of homegrown system. As of November 4, 2020, when you google “cost per tenant,” you get a few things at the top of the page. The first is a couple of blogs by AWS, where they describe an extraordinarily complex system, which you can build yourself.