>>Welcome to this cube conversation. I'm Dave Nicholson, and this is part of the AWS startup showcase season two. I'm very happy to have with me Webb brown CEO of Qube cost web. Welcome to the program. How are you? I'm doing >>Great. It's great to be here, Dave. Thank you so much for having me really excited for the discussion. >>Good to see you. I guess we saw each other last down in Los Angeles for, for coop con, >>Right? Exactly. Right. Still feeling the energy from that event. Hoping we can be back together in person. Not, not too long from now. >>Yeah. Well I'll second that, well, let, let's get straight to it. Tell us, tell us about Q cost. What do you guys do? And I think just central to that question is what gives you guys the right to exist? What problem are you solving? >>Yeah, I love the question. So first and foremost coupe costs, we provide cost monitoring and cost management solutions for teams running Kubernetes or cloud native workloads. Everything we do is, is built on open source. Our founding team was working on infrastructure monitoring solutions at Google before this. And, and what we saw was as we had several teammates join the Kubernetes effort very early days at Google, we saw teams really struggling even just to, to monitor and understand Kubernetes costs, right? There's lots of complexity with the Kubernetes scheduler and being able to answer the question of what is the cost of an application or what is the cost of, you know, a team department, et cetera. And the workloads that they're deploying was really hard for most teams. If you look at CNCF study from late last year, still today, about two thirds of teams, can't answer where they are spending money. And what we saw when digging in there is that when you can't answer that question, it's really hard to be efficient. And by be efficient, we, we mean get the right balance between cost and performance and reliability. So we help teams in, in these areas and more where, you know, now have thousands of teams using our product. You know, we feel where we're just getting started on our mission as well. >>So when people hear it, when people think of coop costs, they w they naturally associate that with Kubernetes. And they think, well, Kubernetes is open-source wait, isn't that free? So what, so what costs are you tracking? Exactly. >>Yeah. Great question. We would track costs in any environment where you can run Kubernetes. So if that's on-prem, you can bring a custom pricing sheet to monitor, say the cost of your underlying CPU course, you know, GPU's memory, et cetera. If you're running in a cloud environment, we have integrations with Azure, GCP and AWS, where we would be able to reflect all the complexity of, you know, whatever deployment you have, whether you're using a spot and multiple regions where you have complex enterprise discounts are eyes savings plans, you name it, we'd be reflecting it. So it's really about, you know, not just generic prices, it's about getting the right price for your organization. >>So the infrastructure that goes into this calculation can be on premises or off premises in the form of cloud. I heard that, right? >>Yeah, that's exactly right. So all of those environments, we'd give you a visibility into all the resources that your Kubernetes clusters are consuming. Again, that's, you know, nodes, load balancers, every resource that it's directly touching also have the ability for you to pull in external costs, right? So if you have Kubernetes tenants that are using S3 or cloud sequel, or, you know, another external cloud service, we would make that connection for you. And then lastly, if you have shared costs, sometimes even like the cost of a dev ops team, we'd give you the ability to kind of allocate that back to your core infrastructure, which may be used for showback or even charged back across your, your, >>So who are the folks in an organization that are tapping into this, are these, you know, our, our, our, our developers being encouraged to be cognizant of these costs throughout the process, or is this just sort of a CFO on down visibility tool? >>Yeah, it's a great, it's a great question. And what we see is a major transformation here where, you know, kind of shift left from a cost perspective where more and more engineering teams are interested in just being aware or having transparency. So they can build a culture of accountability with costs, right, with the amazing ability to rapidly push to production and iterate, you know, with microservices and Kubernetes, it's hard to have this kind of, you know, just wait for say the finance team to review this at the end of the month or the end of the quarter. We see this increasingly be being viewed in real time by infrastructure teams, by engineering teams. Now finance is still a very important stakeholder and, you know, absolutely has a very important like seat at the table in these conversations. But increasingly these are, again, real time or near real time engineering decisions that are really moving the needle on cost and cost efficiency, overtime and performance as well. >>Now, can you use this to model what costs might be, or is this, or is this, you know, you, you mentioned monitoring in real time, is this only for pulling information as it exists, or could you do, could you use some of the aspects of, of, of your toolset to make a decision, whether something makes more sense to run on your existing infrastructure on premises versus moving into, you know, working in a cloud? Is that something that is designed for or not? >>Great question. So we do have the ability to predict cost cost going forward, based on everything we've learned about your environment, whether you're in multi-cloud hybrid cloud, et cetera. So some really interesting functionality there and a lot more coming later this year, because we do see more and more teams wanting to model the state of the future, right? As you deploy really complex technologies, like say the cluster auto scale or, or HPA in different environments, it can really challenging to do an apples to apples comparison, and we help teams do exactly that. And again, gonna have a lot more interesting announcements here later this year. >>So later that later this year, meaning not in the next few minutes while we're together, >>Nothing new to announce on that front today, but I would say, you know, expect later this quarter for us to have more. >>Okay, that sounds good. Now, now you touched on this a little bit, but I want to hone in on why this is particularly relevant now and moving into the future. You know, we've always tracking costs has always been important, you know, even before the Dawn of cloud, but why is it increasingly important? And, and, you know, there are, there are alternatives for cost tracking legacy alternatives that are out there. So talk about why it's particularly relevant now and tell us what your super power is. You know, what's the, all right. All right. >>Secrets, >>Secret sauce is something you can't share super power. You can talk about >>Absolutely >>NDA. So yes, >>Your superpower. Yeah. Great questions. So for support, just to, to, to touch on, what's fundamentally changing to make a company like ours, you know, impactful or relevant. There's really three things here first and foremost is the new abstractions or complexities that come with Kubernetes, right. Super powerful, but from a cost standpoint, make it considerably harder to accurately track costs. And the big transformation here is, you know, with Kubernetes, you can, at any given moment have 50 applications running on a single node or a single VM, you can fast forward five minutes and there could be 50 entirely new applications, right? So just assigning that VM or, you know, tagging that VM back to an application or team or department really is not relevant in those places. So just the new complexity related to costs makes this problem harder for teams. Second is what we touch on. >>Just again, the power of Cooney. Kubernetes is the ability to allow distributed engineering teams to work on many microservices concurrently. So you're no longer in a lot of ways managing this problem where they centralized kind of single point of decision-making. Oftentimes these decisions are distributed across not only your infrastructure team, but your engineering team. So just the way these decisions and, you know, innovation is happening is changing how you manage these. And lastly, it's just scale, right? The, the cloud and, you know, Kubernetes continue to be incredibly successful. You know, where as goop costs now managing billions of dollars as these numbers get bigger and bigger just becomes more of a business focus and business critical issue. So those are the, you know, the three kind of underlying themes that are changing. When I talk about what we do, that makes us special. It's really this like foundational layer of visibility that we build. >>And what we can do is in real time with a very high degree of accuracy at the largest Kubernetes clusters in the world, give you visibility at any dimension. And so from there, you can do things like have real-time monitoring. You can have real-time insights, you can allow automation to make decisions on these, you know, inputs or data feeds. You can set alerts, you can set recurring reports. All of these things are made possible because of, you know, the, the, I would say really hard work that we've done to, again, give this real-time visibility with a high degree of accuracy at, at crazy scale. >>So if we were to play little make-believe for a moment, pretend like I'm a skeptical sitting on the fence. Not sure if I want to go down this path kind of person. And I say, you know what, web, I think I have a really good handle on all of my costs so far. What would you hit me with as, as, as an example of something that people really didn't expect until they, until they were running coup costs and they had actually had that visibility, what are some of the things that people are surprised by? >>Yeah. Great question. There'd be a number, number one. I'd have, you know, one data point I want to get from you, which is, you know, for your organization or for all of your clusters, what is your cost efficiency? Can you answer that with a high degree of accuracy and by cost efficiency? >>And the answer is now. So tell me, tell me, tell me how to sign up for coupons. >>Yeah. And so the answer, the answer there is you can go get our community version, you know, you can be up and running in minutes, you don't have to share any data, right? Like it is, you know, simply a helmet install, but cost efficiency is this notion of, of every dollar that you are spending on provision resources. What percentage of those dollars are you actually utilizing? And we have, you know, we, we now have, you know, thousands of teams using our product and we've worked with, you know, hundreds of them really closely, you know, this is, you know, that's not the entire market, but in our large sample sizes, we regularly see teams start in the low 20% cost efficiency, meaning that approximately 80% is quote waste time and time. Again, we see teams just be shocked by this number. And again, most of it is not because they were measuring it and accurately or anything like that. Most teams again today still just don't have that visibility until they start working with this. >>So is that, is that sort of the, I in my house household, certain members seem to only believe that there is one position for a light switch, and that would be the on position. Is there, is this a bit of a parallel where, where folks are, are spinning up resources and then just out of sight, out of mind, maybe not spinning them down when not needed. Yeah. >>Yeah. It's, it's, that's definitely one class of the challenges I would say, you know, so today, if you look at our product, we have 14 different insights across like different dimensions of your infrastructure one, or, or I would say several of those relate to exactly what you just described, which is you spin up a VM, you spend a bit load balancer, you spin up an external IP address. You're using it. You're not paying for it. Another class is this notion of, again, I don't have an understanding of what my resources cost. I also don't have a great sense for how much my microservice or application will need. So I'm just going to turn on all the lights, which is, or I'm going to drastically over provision again, I don't know the cost, so I'm just going to kind of set it and forget it. And if my application is performing, you know, then you know, we're doing well here. Again, with this visibility, you can get much more specific, much more accurate, much more actionable with making that trade off, you know, again, down to the individual pod workload, you know, deployment, et cetera. >>So we've, we've touched on this a bit peripherally, but give me an example. You know, you, you run into someone who happens to be a happy user of coop cost. What's the dream story that you love to hear from them about what life was before was before coop costs and what life was like after? >>Yeah, there's a lot, a lot of different dimensions there. You know, one, one is, you know, working with an infrastructure team that, that used to get asked these questions a lot about, you know, why does this cost so much, or why are we spending this and Kubernetes or, or wire expenses growing the rate that they are, you know, like when this, when this works, you know, engineering teams or infrastructure teams, aren't getting asked those questions, right? The tool could cost itself is getting asked that and answering that. So I think one is infrastructure teams, not fielding those types of questions as much. Secondly, is just, you know, more and more teams rolling this out throughout their organization. And ultimately just getting, building a culture of awareness, like ownership, accountability. And then, you know, we just increasingly are seeing teams, you know, find this right balance between cost and performance again. So, you know, in certain cases, improving performance, when are resource bottlenecks in places and other places, you know, reducing costs, you know, by 10 plus million dollars, ultimately at the end of the day, we like to see just teams being more comfortable running their workloads in Kubernetes, right? That is the ultimate sign of success is just an organization, feels comfortable with how they're deploying, how they're managing, how they're spending in Kubernetes. Again, whether that be, you know, on-prem or transitioning from on-prem to a cloud in multiple clouds, et cetera. >>So we're talking to you today as part of the second season of the AWS startup showcase. What's, what's the relationship there with, with AWS? >>So it is the, the largest platform for coop costs being run today. So I believe, you know, at this point, at least a thousand different organizations running our product on AWS hosted clusters, whether they're, you know, ETS or, or self-managed, but you know, a growing number of those on, on EKS. And, you know, we've just, you know, absolutely loved working with the team across, I think at this point, you know, six or seven different groups from marketplace to their containers team, you know, obviously, you know, ETS and others, and just very much see them continuing to push the boundaries on what's possible from a scale and, you know, ease of use and, you know, just breadth of, of offering to this market. >>Well, we really look forward to having you back and hearing about some of these announcements, things that are, that are coming down the line. So we'll definitely have to touch base in the future, but just one, one final, more general question for you, where do you see Kubernetes in general going in 2022? Is it sort of a linear growth? Is there some, is there an inflection point that we see, you know, a good percentage of software that's running enterprises right now is already in that open source category, but what are your thoughts on Kubernetes in 2022? >>Yeah, I think, you know, the one word is everywhere is where I see Kubernetes in 2022, like very deep in the like large and really complex enterprises. Right. So I think you'll see just, you know, major bets there. And I think you'll continue to see more engineers adopted. And I think you'll also continue to see, you know, more and more flavors of it, right? So, you know, some teams find that running Kubernetes anymore serverless fashion is, is right for them. Others find that, you know, having full control, you know, at every part of the stack, including running their own autoscaler for example is really powerful. So I think just, you know, you'll see more and more options. And again, I think teams increasingly adopting the right, you know, abstraction level on top of Kubernetes that works for their workloads and their organizations >>Sounds good. We'll we'll, we'll come back in 2023 and we'll check and see how that, how that all panned out. Well, it's been great talking to you today as part of the startup showcase. Really appreciate it. Great to see you again. It's right about the time where I can still tell you happy new year, because we're still, we're still in January here. Hope you have a great 2022 with that from me, Dave Nicholson, part of the cube part of AWS startup showcase season two, I'd like to thank everyone for joining and stay with us for the best in hybrid tech coverage.