>> Good afternoon everyone, and welcome back to theCUBE where we're coming to you live from Detroit, Michigan at KubeCon and Cloud Native Con. We're going to keep theCUBE puns coming this afternoon because we have the pleasure of being joined by not one but two guests from Kubiya. John Furrier, my wonderful co-host. You're familiar with these guys. You just chatted with them last week. >> We broke the story of their launch and featured them on theCUBE in our studio conversation. This is a great segment. Real innovative company with lofty goals, and they're really good ones. Looking forward to it. >> If that's not a tease to keep watching I don't know what is. (John laughs) Without further ado, on that note, allow me to introduce Amit and Shaked who are here to tell us all about Kubiya. And I'm going to blow the pitch for you a little bit just because this gets me excited. (all laugh) They're essentially the Siri of DevOps, but that means you can, you can create using voice or chat or any medium. Am I right? Is this? Yeah? >> You're hired. >> Excellent. (all laugh) >> Okay. >> We'll take it. >> Who knows what I'll tell the chat to do or what I'll, what I will control with my voice, but I love where you're. >> 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. You know, having different platforms that require an 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 the language barrier sometimes. >> Precisely. >> 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 cast into simple conversations. That's, that's really what we're saying here. >> So let's get into the launch. You just launched a fresh startup. >> Yeah, yeah, yeah. >> Yeah. >> So you guys are going to take on the world. Lofty goals if that. I had the briefing. Where's the origination story come from? What, 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? >> Shaked: So. >> Amit: Okay, go first please. >> Essentially everything started with my experience as being an operator. I used to be a DevOps engineer for a few years for a large (indistinct) company. On later stages I even managed an SRE team. So all of these access requires Q and A staff is something that I experience nonstop on Slack or Teams, all of these communication channels. And usually I find out that everything happens from the chat. So essentially back then I created a chat bot. I connect this chat bot 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, they want to do inside the bot. But it's still managed to solve 70% of the complexity and the toil on us as a team so we could focus on innovation. So Kubiya's a more advanced version of it. Basically with Kubiya you can define what we call workflows, and we convert all of these complexity of access request 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. (all laugh) And you said, Hey, screw it. I'm going to just create a bot, bot myself up. (Shaked laughs) But it gets at something important. I mean, I'm not just joking. It probably happened, right? That was probably the case. You were up all night telling. >> Yeah, I mean it was usually stuff that we didn't need to maintain. It was training requests and questions that just keep on repeating themselves. And actually we were in Israel, but we sell 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 will approach us from the US. So we didn't really sleep. (all laugh) As with these requests non-stop. >> It's that 24 hour. >> Yeah, yeah. 24 hours for a single team. >> So the world clock global (indistinct) catches you a little sometimes. Yeah. >> Yeah, exactly. >> So you basically take all the things that you know that are common and then make a chat bot answering as if you're you. But this brings up the whole question of chat bot utilization. There's been a lot of debate in the AI circles that chat bots really haven't made it. They're not, they haven't been good enough. So 'cause NLP and other trivial, >> Amit: Sure. or 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 chat bots are general purpose, right? We're coming with the domain expertise. We know the pain from the inside. We know how the operators want to define such conversations that users might have with the virtual assistant. So we combined all of the technical tools that are needed in order to get it going. So we have a 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 DSDK. 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 assist 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, 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. So essentially. >> John: Like how? Give me 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 hasn't, 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 permission to access the request and control and so on. >> Savannah: That's something. Yeah, I love that as a knowledge base. I mean a custom tool kit. >> 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. >> 100 percent. >> I can customize my experience. >> Mm hmm. >> Do you see your, this is really interesting, and I'm, 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. >> Yeah. >> Do you view yourselves as a gateway tool for more folks to be involved in more complex technology? >> So, so I'll take that. It's not that we haven't seen advanced virtual assistants. They've existed in different worlds. >> Savannah: Right. >> Up until now they've existed more in CRM tools. >> Savannah: Right. >> Call centers, right? >> Shaked: Yeah. >> You go on to Ralph Lauren, Calvin Klein, you go and chat with. Now imagine you can bring that into a world of dev tools 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, that's a unique feature here. >> What's the biggest thing that's surprised you with the launch so far? The reaction to the name, Kubiya, which is Cube in Hebrew. >> Amit: Yes. >> Apparently. >> Savannah: Which I love. >> Which by the way, you know, we have a TM and R on our Cube. (all laugh) So we can talk, you know, license rights. >> Let's drop the trademark rules today, John, here. We're here to share information. Confuse the audience. Sorry about that, by the way. (all laugh) >> We're an open source, inclusive culture. We'll let it slide this time. >> The KubeCon, theCUBE, and Kubiya. (John laughs) In the Hebrew we have this saying, third time we all have ice cream. So. (all laugh) >> I think there's some ice cream over there actually. >> There is. >> Yeah, yeah. There you go. >> All kidding aside, all fun. What's, what's been the reaction? Got some press coverage. We had the launch. You guys launched with theCUBE in here, big reception. What's been the common feedback? >> And really, I think I expected this, but I didn't expect this much. Really, the fact that people really believe in our thesis, really expect great things from us, right? We've starting to working with. >> Savannah: Now the pressure's on. >> 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 approaching the self-service which really has been stalled for a while. And we've recognized that. I think our thesis is where we. >> Okay, so as a startup you have lofty goals, you have investors now. >> Amit: Yeah. >> Congratulations. >> Amit: Thank you. >> They're going to want to keep the traction going, but as a north star, what's your, what are you going to, 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 the, what's the? >> Sure, sure. >> I'm sure you guys have it. Who are you takin' 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 DevOps. >> John: So you see this as greenfield, new opportunity? >> I believe so. >> Is there any incumbent you see out there? An old stodgy? >> Today we're on internal developer platform service catalog type of, you know, use cases. >> John: Yeah. >> But that's kind of where we can grow from there and have the ecosystem essentially embrace us. >> John: How about the technology platform? >> Amit: Yeah. >> What's the vision for the innovation? >> Essentially want to be able to integrate with all of the different cloud providers, cloud solutions, SaaS platforms, and take the atlas approach that they were using right to the chats 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 totally 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. >> Savannah: Yeah. So it requires a lot of thinking, a lot of architecture, but we are doing it just fine. >> Awesome. What do you guys think about KubeCon this week? What's, what's the top story that you see emerging out of this? Just generally as an industry observer, what's the most important? >> Savannah: Maybe it's them. Announcement halo. >> What's the cover story that you see? (all laugh) I mean you guys are in the innovation intent-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 improve upon 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. Now you're in Tel Aviv. You're in the bay. >> Shaked: Check our openings on LinkedIn. (all laugh) >> We have a dozen job postings on our website. Obviously engineering and sales then go to market. >> So when theCUBE comes to Tel Aviv, and we have a location there. >> Yeah. >> Will you be, share some space? >> Savannah: Is this our Tel Aviv office happening right now? I love this. >> Amit: We will be hosting you. >> John: theCube with a C and Kube with a K over there. >> Yeah. >> All one happy family. >> Would love that. >> Get some ice cream. >> Would love that. >> All right, so last question for you 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 theCUBE next time? >> No, no, it's absolutely. I think our thesis that you can turn conversations into operations. It's, it sounds obvious to you when you think about it, but it's not trivial when you look into the workflows, into 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 a lip service from both of you. >> No. (all laugh) >> Is there going to be levels of bot, like level one bot level two, level three, and then finally the SRE gets on the phone? Is that like some point? >> Is there going to be bot singularity? Is that, is that what we're exploring right now? (overlapping chatter) >> Some kind of escalation bot. >> Enlightenment with bots. >> We actually planning 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. >> Shaked: Yeah. >> But not exactly the same. Really good, good solution. I love the direction. Congratulations on the launch. >> Shaked: Thank you so much. >> Amit: Thank you very much. >> Yeah, that's very exciting. You can obviously look, check out that news on Silicon Angle since we had 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? >> Be on our Twitter and LinkedIn handles of course. So we have kubiya.ai. 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, Amit, Shaked, thank you so much for being with us. >> Shaked: Thank you so much. >> John, thanks for sitting to my left for the entire day. I sincerely appreciate it. >> Just glad 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 are there to find out. >> Amit: Love it.