Observability for the AI Cloud

[Music] Hello everyone. Thanks so much for coming today. I'm Malavika and as you heard I'm a product manager at Verscell. I hope you've had a great day at the conference. I've certainly been blown away by what all of you have been building with our open source tools and infrastructure primitives. It's been so nice to meet many of you in person for the first time um and see some new faces

as well as familiar faces. So today we've learned a lot about the AI cloud. By now you're probably tired of hearing about the AI cloud. You might have be thinking, gosh, can I just get a drink at happy hour already? But just as a reminder in case the message just hasn't quite sunk in yet, Verscell is a unified platform for building, deploying, and running intelligent applications and the agents

behind them. Verscell's mission has always been to abstract away the complexity of managing infrastructure and let you focus on building amazing user experiences. So when we think about how successful we've been in abstracting away complexity across the software development life cycle, we've done a really good job on making buildtime a breeze. Framework defined infrastructure

means that you don't need to think about the underlying infrastructure primitives. There's no need for complex orchestration or infrastructure as code. We handle provisioning compute, networking, caching and more so that you can focus on your application logic. But if we reflect on runtime, there's still a lot of work we have to do to make that as easy and breezy as build time. Sadly, managing an application at

runtime is still quite a time consuming effort for development teams. Like how many in the audience here have dealt with a major incident in the last week? I I don't see that many hands up. I'm surprised. I'm like, are you all using GCP or something? Um maybe maybe you there in the audience uh you're probably feeling really good right now that you're self-hosting Nex.js on a VPS in Hetner. You're like, the cloud's not

going to bring me down. Um, but there's so much manual toil associated with incident response. First, teams need to set up alerts and monitors to identify potential problems. These monitoring tools then in turn cause alert fatigue as teams try to identify high signal issues amongst all the noise. And then once we identify an issue, teams spend hours debugging the issue, trying to identify the root cause and then apply a

fix. So I actually here in the audience we're going to make this a little bit interactive. How much time do you think developers spend on debugging an incident? How many of you think it's under 20% of incident time is spent on debugging? >> More 80 I heard 80%. I So we think it's almost as who thinks it's more like 40%. Uh okay, we've got we've and someone

thinks it's 60 70. Okay, that seems to be maybe consensus. Um 50% actually turns out that 50% of incident time is spent on identifying the root cause and figuring out who should solve it. Like that's crazy. In 2025 with AI, we're spending hours of valuable developer time debugging issues. What if we could reduce that to seconds? Well, with Verscell agent, you can. Our