 Good afternoon everyone and welcome back to theCUBE where we're coming to you live from Detroit, Michigan at KubeCon and called NativeCon. We're going to keep the KubePuns coming this afternoon because we have the pleasure of being joined by not one but two guests from Kubea, John Furrier, my wonderful co-host. You're familiar with these guys. You just shadowed with them last week. We broke the story of their launch and featured them on theCUBE in our studio and studio conversation. This is a great segment, real innovative company with lofty goals and they're really good ones. Looking forward to this. If that's not a tease to keep watching, I don't know what is. Without further ado on that note, allow me to introduce Amit and Shaqid who are here to tell us all about Kubea and I'm going to blow the pitch for you a little bit just because this gets me excited. They're essentially the Siri of DevOps but that means you can create using voice or chat or any medium. Am I right? Is this, yeah? You're hired. Excellent. We'll take it. We'll take it. Who knows what I'll tell the chat to do or what I will control with my voice but I love what you're saying. Absolutely. I'll just give the high level conversational AI for the world of DevOps. Kind of redefining how self-service DevOps is supposed to be essentially accessed, right? As opposed to just having siloed information, having different platforms that require the operator or somebody who's using it to know exactly how they're accessing what they're doing and so forth, essentially the ability to express your intent in natural language, English or any language I use. It's quite literally a language barrier sometimes, both from the spoken as well as code language and it sounds like you're eliminating that as an obstacle. We're essentially saying turn simple complex tasks into simple conversations. That's really what we're saying. So let's get into the launch. You just launched a fresh startup. You guys are going to take on the world. Lofty goals, I had the briefing. Where's the origination story come from? How did you guys get here? Was it a problem that you saw, you were experiencing, an itch you were scratching? What was the motivation and what's the origination story? So, essentially everything started with my experience as being an operator. I used to be a DevOps engineer for a few years for a large company. On later stages, I even managed an SRE team. So all of these access requests, Q&A stuff is something that I experienced nonstop on Slack or Teams, all of these communication channels and usually I found out that everything happens from the chat. So essentially back then I created a chatbot. I connect this chatbot to the different organizational tools and instead of the developers approaching to me or the team using the on-call channel or directly they will just approach the bot. But essentially the bot was very naive and they still needed to know what they want to do inside the bot. But it still managed to solve 70% of the complexity and the toil on us as a team so we could focus on innovation. So, QBI is a more advanced version of it. Basically with QBI you can define what we call workflows and we convert all of this complexity of access requests into simple conversations that the end users which could be developers but not only are having with a DevOps team. So that's essentially how it works and we're very excited about it. So you were up all night answering the same question over and over again. Is that the point? I need to say, screw it. I'm going to just create a bot, but it gets at something important. I'm just joking, probably happened, right? That was probably the case. You're up all night, tell us. Yeah, I mean, it was usually stuff that we didn't need to maintain. It was trending requests and questions that just keep on repeating themselves and actually we were in Israel but we served three different time zones of developers. So all of these developers as soon as the day finishes in Israel, the day in the US started. So they would approach us from the US. So we didn't really sleep answering these requests. Because that's 24 hours. Yeah, 24 hours for a single team. The old clock goblets, you can catch it a little sometimes. So you basically take all the things that you know that are common and then make a chatbot answer as if you're you. But this brings up the whole question of chatbot utilization. There's been a lot of debate in the AI circles that chatbots really haven't made it. They haven't been good enough. So because of NLP and other trivial things that haven't really clicked. What's different now? How do you guys see your approach? Cracking the code to go that kind of reasoning level. Bots can reason, now we're in business. Yeah, most of the chatbots are general purpose, right? We're coming with a domain expertise. We know the pain from the inside. We know how the operators want to define such conversations that users might have with a virtual assistant. So we combined all of the technical tools that are needed in order to get it going. So we have a DSL domain specific language where the operators can define these easy conversations and combine all of the different organizational tools which can be done using the SDK. Besides this fact, we have a no code for less technical people to create such workflows even with no code interface. And we have a CLI which you could use to leverage the power of the virtual assistant even right from your terminal. So that's how I see the domain expertise coming in that we have different communication channels for everyone that needs to be inside the loop. That's awesome. And I can add to that. So that's one element which is the domain expertise. The other one is really our huge differentiator. The ability to let the end users influence the system itself. Like how? Give an example. Sure, we call it teach me feature. But essentially, if you have any type of a request and the system hasn't created an automation or doesn't recognize it, you can go ahead and bind that into your intent and next time, and you can define the scope for yourself only, for the team, or even for the entire organization that actually has to have permissions and access to requests and controls and so on. Yeah, I love that as a knowledge base. I mean, a custom toolkit. Absolutely. And I like that you just said for the individual. So let's say I have some crazy workflows that I don't need anybody else to know about. I can customize my experience. Do you see yourself, this is really interesting and it's surprising to me, we haven't seen a lot of players in this space before because what you're doing makes a lot of sense to me, especially as someone who is less technical. Do you view yourselves as a gateway tool for more folks to be involved in more complex technology? So I'll take the, it's not that we haven't seen advanced virtual assistants. They've existed in different worlds. Up until now they've existed more in CRM tools, call centers, right? You go on to Robert Ray, Calvin Klein, you go and chat with, now imagine you can bring that into a world of DevTools that has high domain expertise, high technical amplitude, and now you can go and combine the domain expertise with the accessibility of conversational AI. That's a unique feature here. What's the biggest thing that surprised you with the launch so far? The reaction to the name, which is Cube in Hebrew, apparently. Which by the way, we have a TM and R on our cube. So I mean, top, you know, what, Iceland's rights, okay. The Cube, the Cube. What's up with the trade marshal today, John, here? We're here to share information. Open source, open source, open source, sorry about that. Where are you slide this time? The CubeCon, the Cube, and Kubea. In the Hebrew we have the saying third time, we all have ice cream. So. I think there's some ice cream over there. There is. All kidding aside, all fun. What's been the reaction? Got some press coverage. We had the launch, you guys launched with the Cube in here. Big reception. What's been the common feedback? And really, I think I expected this, but I didn't expect this much. The fact that people really believe in our thesis. Really expect great things from us, right? We've started to work in with. Rolling out dozens of POCs, but even that requires obviously a lot of attention to the detail, which we're rolling out. This is effectively what we're seeing. People love the fact that you have a unique and fresh way to approach in the self-service, which really has been stalled for a while, and we've recognized that. I think our thesis is what we're doing. So as a startup, you have lofty goals, you have investors now. Congratulations. Thank you. They're going to want to keep the traction going. But as the North Star, what are you going to take? What territory are you going to take? Is it new territory? Are you eating someone's lunch? Who are you going to be competing with? What's the target? What's that? What's that? I'm sure you guys have it. What are you taking over? I think the gateway, the entry point to every organization is a bottleneck. You solve the hard problem first, that's where you can go into other directions and you can imagine where other operational workflows and pains that we can help solve once we have essentially the dev off. This is the green field, new opportunity. I believe so. What do you see out there in old Stodgy? Today we're on an internal developer platform, service catalog type of use cases, but that's kind of where we can grow from there and have the ecosystem essentially embrace us. How about the technology platform? What's the vision for the innovation? Essentially you want to be able to integrate with all of the different cloud providers, cloud solutions, SaaS platforms, and take the headless approach that we're using right to the chat from everywhere to anywhere. So essentially we want in the end that users will be able to do anything that they need inside all of these complicated platforms which some of them are truly complicated with plain English. So what's the biggest challenge for you then on that front leading the technology side of the team? So I would say that the conversational AI part is truly complicated because it requires to extract many types of intentions from different types of users and also integrate with so many tools and solutions. So it requires a lot of thinking, a lot of architecture, but we're doing it just fine. Awesome, what do you guys think about KubeCon this week? What's the top story that you see emerging out of this? Just generally as an industry observer, what's the most important story? Maybe it's them. Announcement halo. Yeah. You see, I mean you guys are in the automation and tent-based infrastructure, I get that. So obviously everyone's looking to diversify their engineering, diversify their platforms to make sure they're as decoupled from the main CSPs as possible. So being able to build their own and we're really helping enable a lot of that in there. We're really helping prove the point that open source together with managed platforms can really play a very nice game together, so. Awesome, so are you guys hiring, recruiting? Tell us about the team DNA and your telly if you're in the bay. Check our openings, or LinkedIn. We have a dozen job postings on our website, obviously engineering and sales, then go to market. So when the cube comes to Tel Aviv and we have a location there. Yeah, it's a sort of telly of office happening right now. We would be hosting you. With the C and the cube with the K over there. All one happy family. We'd love that. Get some ice cream. We'd love that. All right, so last question for y'all. You just had a very big exciting announcement. It's a bit of a coming out party for you. What do you hope to be able to say in a year that you can't currently say right now when you join us on the cube next time? No, no, absolutely. I think our thesis that you can turn conversations into operations, it sounds obvious when you think about it, but it's not trivial when you look into the workflows and to the operations. The fact that we can actually go a year from today and say we got hundreds of customers, happy customers, who've proven the thesis or sharing knowledge between themselves, that would be euphoric for us. All right. You really are about helping people. Absolutely. It doesn't seem like it's just lip service from both of you. No. It's going to be levels of bot, like level one bot, level two, level three, and then finally the SRE gets on the phone. Are we going to reach bot singularity? Is that what we're exploring right now? Like some kind of escalation bot. Levels are the right thing to do with bots. We're actually playing a feature we want to call a handoff where a human in the loop is required, which often is needed. Machine cannot do it alone, we'll just... Yeah, I think it makes total sense for GEOs, ops at the same but not exactly the same. Really good solution. I love the direction. Congratulations on the launch. Thank you so much. Thank you very much. It's exciting. You can obviously check out that news on Silicon Angle since we have the pleasure of breaking it. Absolutely. If people would like to say hi, stalk you on the internet, where's the best place for them to do that? Beyond our Twitter and LinkedIn handles, of course. So we have kubi.ai. And we also have a free trial until the end of the year and we also have free forever tier that people can sign up, play and come say hi. I mean, we'd love to chat. I love it. Well, Mitch, Shaked, thank you so much for being with us. Thank you so much. John, thanks for sitting to my left for the entire day. I sincerely appreciate it. I can help out. And thank you all for tuning in to this wonderful edition of theCUBE, live from Detroit at KubeCon. Who knows what my voice will be controlling next? But either way, I hope you're there to find out.