 I think that how you use AI and how you incorporate it into your workflows is really critical. So we take an approach that really looks at keeping humans in the loop and augmenting them versus replacing them. Hi, this is your host, Saplim Bhartia. And today we have with us, Devani Lamas, CEO of Transposit. Devani, it's great to have you on the show. Thank you. Thanks for joining me today. Since you are here, so I'd love to ask you, what is Transposit all about? What kind of problem are you folks solving? We're building an AI-powered incident management solution. Our goal is to take a lot of the toil and difficulty involved in incidents and make that a lot easier using AI. I want to talk a bit about Genetic AI and how Transposit is using it. But before we go there, let's just talk about the importance of incident management. Incident management is one of those things that if you don't have it implemented today as a process, you need to invest in it. We just came out today with our annual State of DevOps report. It uncovered this really interesting paradox, which is a lot of companies are investing in process automation around incidents, but they're still seeing increasing costs on incidents and increasing pain around incidents. There's been a lot of studies on the cost of incidents for organizations, but you're talking about hundreds of thousands of dollars per hour for some companies that are dealing with it. And the really hard part is that it tends to be the kind of thing that brings everyone in a firefighting mode, and so it takes people away from what they should be doing, which is building your technology, building your product. So organizations are aware of the importance of incident management, but can you talk about how mature their incident management strategies and posture really is? I talk to people about a spectrum of automation. And most companies that I talk to have some level of incident management in place. They might have a paging solution, for example. But the challenge with tools like that is that their real focus is just on waking you up, and then it's like, good luck, you know, you're going to have to deal with figuring out the rest of it from there. So I think there's awareness, there's desire, and there's even sort of acknowledgement that AI is going to play a really big role in that for them. But I think in terms of maturity, we're still in very early stages. Since you mentioned AI, let's talk about the role of AI in incident management space or for Transposit and how you folks are leveraging or using it. We have an engineer at Transposit, and her name is Tanya. And we sometimes joke around how one of our goals is to take the amazingness that is Tanya and make it accessible to anyone that uses our product. And so what makes Tanya really great? So when she gets an alert, she's really good at understanding in her mind. She knows how all the different systems interplay. She's got a lot of historical knowledge of what incidents and issues we've had in the past, and she knows exactly how to get that data quickly. And so she's able to basically, you know, kind of bring all the information that the team needs and the context that they need in a really, really rapid fashion. Most companies I talk to, they might have one or two people like that that are critical members of their senior engineering team that have that context. I think the challenge is how do you take something that can sometimes take people 15 years to get really great at and democratize that? So every person in your organization, even if they've only been there for two weeks, is able to access that same institutional knowledge when an alert fires. So if Iron Man has Jarvis, you have Tanya? Well, internally we call it Iggy after our mascot. But yes, she's absolutely part of the inspiration behind it. As you explained that organizations have been doing incident management in their own way, which means that they have a very well defined workflow. When it comes to them embracing transposite, how does transposite fit into these workflows? Do they have to make a lot of changes or it's a very seamless experience for them? That's a really great question. So I'm a big believer that every organization is going to have their own environment that's going to have tools that they value and enjoy. And our goal is not to come in and make people rebuild, you know, kind of every part of their process. We are very happy to integrate with your existing tooling to leverage the investments you've already made. I think the place where we really shine is in integrating into those tools and then surfacing the right moments to bring those tools into your workflow. So, you know, kind of for us, organizations typically will integrate into their JIRA environment, into their observability tooling, into whatever they're using for CI CD, for code repositories. And that allows us to like leverage the investments that they've made in automation in those systems while bringing them together into an end-to-end flow around their incidents. When it comes to Genitive AI, I see some skepticism. We cannot fully rely on it. Companies feel that human intervention is needed. From transposite and incident management perspective, how reliant can we be on Genitive AI? I think there's a lot of skepticism out there, right? Rightfully so. I think we've all tried ChatGPT and given it a prompt and then gotten gobbledygook back, right? So, people think incidents and they're like, how am I going to trust something like this? So, I think that how you use AI and how you incorporate it into your workflows is really critical. So, we take an approach that really looks at keeping humans in the loop and augmenting them versus replacing them. So, it's very important for us when we have an AI-driven suggestion or insight to present it as that, as an insight or a suggestion that people can respond to and choose to run or choose not to run. So, for example, if we are creating a summary for someone of messages that are happening in the alert, we're going to prompt them and say, hey, we think that it might be a good time to update and here's our draft of that summary, but we always have an edit button that they can come in and modify. Those edits help us make the AI better over time as well as giving people control over what's going on, because it's just too early days for people to fully automate some of these workflows and certainly to trust that. And that's true with any emerging technologies. I mean, if you look at the early days of Docker or Kubernetes, people were skeptical about it, but they matured and kind of they have become the backbone of companies. Same thing might happen with gender, but I want to hear from you. What is your perspective? Do you see this as the future of incident management? I think that they're very complimentary. So, I'll give you an example. If I have a workflow in order to restart a machine, that is a deterministic workflow that I want to happen the exact same way every single time. And I might want to put guardrails into that workflow, but how do you promote that workflow to a human in an incident at the right moment? We call that adaptive automation. It's basically the idea that there might be elements of automation that continue to have the traditional approach of rigid guardrails and kind of lots of controls to make sure that you're not going kind of crazy when you're running some of these things during an incident. But I do think there's a role at the top for dynamically bringing in that automation at the right moment and using more intelligence behind those triggers versus the traditional kind of coding a specific alert to a specific set of workflows because that tends to be really fragile. It breaks when APIs change. It breaks when alerts change. And I think that that's been one of the big things that's prevented a lot of automation adoption. Let's not talk about culture. What role do you see of culture for incident management? Also, let's talk about the impact tools or technologies and company like Transposit can have on culture. And they can kind of become a catalyst to bring the cultural change that is needed within organizations. So what I've found, I've been pleasantly surprised around this, it's very common in incident management circles for people to talk about training and like the challenges of training and a lot of vendors kind of will put together all of this guidance on like, this is how you're going to train people to use your tooling. And what's really powerful about AI is that it's just such an intuitive way to work with the solutions that really brings down that training overhead. Like a really great example. If you think that in order to get your team to do updates regularly, you have to tell them, okay, you have to provide an update every 30 minutes. That's a lot to expect a person to do when they've just been woken up at 3 a.m. with a major issue in their environment. On the other hand, if you have a friendly chatbot that's sitting there and says, I noticed that you haven't made an update in a while or this particular thing that you've done seems like it might be deserving of a communication to the wider team. It becomes much more collaborative and ongoing on the job training, which really helps with that cultural adoption issue. I tell people that our goal is for our AI to feel more like a really valuable teammate versus kind of a system that's just kind of like sitting there telling you what to do. It's about that collaborative approach. It's almost holiday season and this is also the time that engineers don't like because they know the speak season, traffic is high and if something goes wrong, they have to stay awake at night. So talk a bit about how transport make it less stressful for them so that they don't have to worry about staying awake at night if something goes wrong. I'm a big believer in taking the things that can be automated off of people's plate so they can focus on the things that humans are uniquely good at, which is creativity, problem solving and things like that. So again, our focus is people really, really hate writing updates because they know that everyone is going to read them and it's really stressful to think about how am I going to create an update that summarizes all the things that just happened. AI takes a lot of that friction away. It takes a lot of that mental load away and takes that toil away. So for us, let's reduce the number of parallel jobs that a person has to do during an incident and really bring it down to the core of letting them focus on solving the actual problem. I will go back to Genitive AI because there is a lot of fear, uncertainty and doubt that it's going to take away our jobs that it's going to replace people. That may not be entirely true, but I want to hear your perspective. What impact do you see of Genitive AI on people, jobs, hiring? So we're at this conference right now and I've been talking to all sorts of managers and they'll come up to me and they always say, I can't for the life of me hire enough SREs, DevOps engineers, members of my platform engineering team to cover what I need to do. So I really do think that anyone who feels like they are going to be replaced, like absolutely the technology is nowhere near that point. Instead, this is a force multiplier. It lets teams do more with less. It allows them to stay capable of handling all the load that's on them and let's be really honest, people that are in cloud environments are overwhelmed with changes, tooling, number of systems to coordinate between. That's not going to go away. AI can be helpful, it can help reduce stress. We like to sell people, go do your on call from the beach with transposites, but it's still a very, very long ways from being able to take an entire person's job and do it. Of course, you folks continue to work a lot of technologies internally and there are a lot of things that you cannot talk about at this point, we'll talk about them when they're ready, but just give us a glimpse, a teaser, what we should expect next from Transposit. Well, one of the big things that we just unveiled at the conference is our new free tier. So we have introduced a unlimited free tier with unlimited users for our product because we wanted to make sure that everyone could see the magic of AI and incident management and we didn't want cost to stop people from getting started with it. So that's available on our website, anyone can sign on with Slack. It does include our basic AI as part of that package. We do have an enterprise tier that has more sophisticated AI plugins and I think there's some really exciting stuff going on on that AI plugin tier. We're working on some really awesome stuff around change integration and being able to bring in like status messages from other systems and automatically checking those things for you and a lot more that I'm not quite ready to share, but if anyone's interested, they can always get started with our free tier and start experiencing AI in production. And that's a free tier, not a trial. Free, free as in free, free forever, no credit card. Just go sign up and get started. Devani, thank you so much for taking time out today. Talk about Transposit, incident management, GenDVI, great insights there and I would love to chat with you again. Thank you. Thank you.