(upbeat music) >> Okay, we're back. We're here in the main stage in Cloud City. I'm John Furrier and Dave Vellante. Normally, we're over there on theCUBE set, but here we've got a special presentation. We'll talk about Totogi and the new CEO of Totogi is Danielle, who is also the CEO of TelcoDR, Digital Revolution. Great to see you. And of course, Robin Langley, we interviewed you in theCUBE, CTO of Totogi. This is a main stage conversation because this is the big news. >> Yeah. >> You guys launched there with a hundred million dollar investment. We covered that news a couple weeks ago and you as the CEO. What's the story. Tell us what is happening with Totogi? Why such a big focus? What's the big push? >> Yeah, I'm really excited about Totogi because I really think this team is working to build public cloud tools for Telco the right way. It's everything I've been talking about. I talked about it yesterday in my keynote and this is really the execution of that vision. So, I'm super excited about that. A couple of days ago, Rob and I were talking about the charging system, but there's another product that Totogi introduced to the world and that's the webscale BSS system. So I think we're going to talk about that today. It's going to be great. >> Let's get into actually the charging system, which was great processing here. What is this focus? What is BSS about with cloud? How does the public cloud innovation change the game with this? >> Well, a little bit like charging. I mean, there are maybe, you know, a hundred plus BSS systems out there, why does the world need yet another BSS? And I think one thing is we're coupling up with public cloud, which gives it that webscale element. Right? We can have a platform. Never do another upgrade again, which I think is really exciting. But I think the really key thing that we're working on is we're building on top of an open API standard. And a lot of vendors talk about their APIs, why is this different? These are standards developed by TM forum, right? It's an independent body in our industry. They've been working on these, sorry, open APIs, and all the different vendors signed a manifesto that say, "I pledge. I pledge to support the open API", but if you look at the leaderboard and everyone is Sub10, Sub5, right? And so it's kind of like, going through the actions and not falling, you know, saying it, but not following it up and we're doing it. >> Wow, so... >> Yeah. >> Dave: Robin, you guys just popped up on the leaderboard. You went from a standing start to, I think more than 10. >> Yeah. >> I don't think that's ever been done before, has it? >> No, so we were out there. We published 12 APIs and we've got a quote from, you know, TM forums saying, essentially I've never seen anyone move so fast and to publish. And it's our intent to publish, you know, 50 plus, all of their APIs by the end of the year. >> So, how were you able to do that? I mean, like, were you holding them back? Just kind of dumping them on one day? This is the nature of the new business, isn't it? >> Yeah, absolutely and then you think about BSS. It's just, you know, been known for years to be a spaghetti of, you know, applications, you know, disparate data, data being duplicated, systems not talking to each other, lots of different interface types. And it was crying out to be just, you know, sold properly in the cloud. And the public cloud is perfect for this. You know, we can build a model and start, rather than looking at the applications first, you know, let's look at the model, the unified model and build on those open APIs and then start to, you know, allow people to come in and create an ecosystem of applications all using that same model. >> If you don't mind me asking you, if you can explain. 'Cause we talked before we weren't on camera, but we talked about the cloud and you were explaining to me how this is perfect for the challenges that you guys are trying to solve. What about the public cloud dynamic or innovation component that you guys are leveraging? Take us through a little bit on that, because I think that's a big story here that's under the covers is... >> Yeah. >> What you're capable of doing here. Do you mind explaining? >> Yeah, no, absolutely. So the cloud gives us this true scalability across everything. You know, we can scale to billions of records. So we can hook in, you know, to suck in data from, you know, our on-premise systems anywhere. We have, you know, a product called Devflow, so we used to do that. And it can really allow us to bring that data in, scale-out, use standard term cloud innovations, like Lambda functions and AWS, you know, DynamoDB, and present that, you know, through that open API. So we can use, you know graphQL, you know, present that with rest on top. And so you can then build on top of that. You can take any low code, no code application building tool you like, put that on top and then start building your own ecosystem. You can build inventory systems, CRM, anything you like. >> Well one thing that's really interesting about these projects is they usually take months, years to deploy, right? And what we're doing is we're providing, almost BSS as a service, right? It's an API layer that anyone can go to. Maybe you need to use it for five minutes, five months, five years, right? With the open standard and your own developers can learn how to use this text stack and code to it doesn't require us. And so we're really trying to get away from being an SI, you know, systems integrator or heavy services revenue, and instead build the product that enables the telcos to use their own people, to build the applications that they, they know what they want, and so, here you go. >> It's a platform. >> Yeah. >> It's a platform. >> So, how do you connect to systems on the ground? Like what's the modern approach to doing that? >> Yeah, go for it. >> Yeah so, telcos have, you know, a huge amount of data on premise. They have difficulties you can get to it. So, as I mentioned before, we had this Devflows product and it has connectors. We have like 30 plus connectors to all the standard sort of, billing systems, CRM systems, you know, we can hook into things like Salesforce. And we can create either, you know, couple of a real-time interface in there, or we can start to suck data into the cloud and then make it available. So, if they want to start with a nice, easy step and just build slowly, we can just hook in and pull that information out. If there may be, you know, an attribute that you want to, you know, use in some of that application, you can easily get to it. And then, you know, over time you start to build your data into the cloud and then you've got the scale, you know, and all the innovations of that brings with it. >> So is Devflow an on-ramp, if you will, for the public cloud, is that the way you were thinking about it? >> Yeah. >> Yeah. Yeah, I mean, I call it the slurper. (group chuckles) Right. I mean, these telcos have, like Robin was saying, spaghetti systems that have been, you know, customized and connected and integrated. I mean, it is a jungle out there of data. They're not going to be able to move this in one step. We just think of like a pile of spaghetti, like the whole bowl. >> Overcooked spaghetti. >> Right overcooked, the whole bowl comes out and it's really hard to just pull out one noodle and the rest is there and what are you going to do? And so the slurper, right, Devflows, allows you to select which data you want to pull out. It could be one time, you could have it sync. You don't have to do the whole thing and it doesn't disrupt the production environment that's on-premise. But now you're starting to move your data into the public cloud and then like Robin was saying, you can throw it up against quick sites. You can throw it up against different Amazon services. You can create new applications. And so it's not this like, you know, big bang kind of approach. You can start to do it in pieces and I think that's what the industry needs. >> I'm talking about this the other day, when we're talk about charging. What a lot of vendors will do is they'll put a wrapper around it, containerize it and then shove it into the public cloud and say, "Okay". >> Check mark. >> Yeah a checkbox. And it affects how they price, if they price the same way. But we talked a lot about pricing the other day, really pricing like cloud, consumption pricing. How are you pricing in this case? >> Same with the charging system. The BSS system is paid by the use, paid by the API call. So, really excited to introduce yet, again, a free tier. We think we're doing 500 million API calls per month for free. We think this is great for a smaller telco where like, you're experimenting and just getting to know the system and before you like, go all in and buy. And I think that API pricing is going to go right at the heart of some of these vendors that love to charge by the subscriber or a perpetual license agreement, right? They're not quite moving as a service. And so, yeah. >> Are you saying, they're going to be disruptive in the pricing in terms of lower cost or more, consumable. >> And I think it's also an easier on ramp, right? It's easier to start paying by the use and experimenting. And it's really easy, just like I was talking about with charging, where you're going to get the same great product that you would sell to a tier one at a price that you can afford. And now those smaller two or three guys aren't having to make a trade off between great technology, but I'm paying through the nose or sacrifice on the tech, but I can afford it. And so, I think you're going to see this ecosystem of people starting to learn how to code and think in this way. Telcos have already decided that they want to adopt the TM forum, open APIs. They're on all the RFPs. Do you support it? Everyone says they support it, but we don't see anyone really doing it. They're not on the leaderboard. >> And there's transparency, because you're pricing by API call, right? Versus the spaghetti, you guys call it, the hairball of what am I paying for? >> Right, you're getting, all of this. It's by the subscriber. It's millions and millions of dollars. Oh, and you know, you're going to need to buy a bunch of consulting revenue to make it all work and talk to each other. Pay up, right? And that's what we're living in today. And I'm taking us to the, you know, public cloud future by the API. >> This is the big cloud revolution. It's unbundling has been a really big part of the consumption of technology paid by the usage, get in, get some value, get some data, understand what it is, double down on it, iterate. >> Put it up with different services that are available that we don't have, but Amazon uses, right? They have call centers up there, they have ML that you may want to use like, start using it, start coding, start learning about the AWS tech stack. >> So is it available now? >> Yeah. >> Yeah. No, it's available now. We've already published the swagger for the BSS APIs. So, you know, they can come on board, they can go to access to all the API straight away and start using it. They can load up their favorite REST clients and then start developing. >> So you got a dozen APIs today. Where are we headed? What can we expect? >> All by the end of the year. There's over 50 APIs. You know, the number one guy on the board is at like 22, 21, 22 APIs covered. We'll be 50 plus by the end of the year. And we're just going to blow doors. >> The API economy has come to telco. >> Yeah, I mean, it's really BSS' Lego pieces, right. Assembling these different components and really opening it up. And I think there's been a lot of power by the vendors to keep it locked down, keep it close. Yes, we have an API, but you got to use our people to do it. Here's the hundreds of thousands or millions of dollars that you're going to pay us and keep us in business, and fat and happy, and I'm coming right in on the low end. Right, dropping that price, opening it up. I think telcos are going to love it. >> Well, Mike, you said too, you'll allow the smaller telcos to have the same, actually, better capabilities than the larger telcos, right? Maybe the stack's not as mature or whatever, but they'll get there and they'll get there with a simpler, easier to understand pricing model and way, way faster. >> Yeah. >> All right and that's where the disruption comes. >> And I Think this is where AWS has really done well as a hyper scaler against their competition, is that they've really gotten to market very quickly with their services. Maybe they're not perfect, but they ship 'em. And they get them out there and they get people using them. They use them internally and they get them out. And I think this is where maybe some of the other hyperscalers, they hold them back and they wait until they're a little bit more mature. And AWS is one because they've been fast. And I want to sort of copy that feat. >> I think your idea of subscriber love in your keynote, and I think applies here because Amazon web services has done such a great job of working backwards from the customer. So they'd ship it fast on used cases that they know have been proven through customer interactions. >> Yep. >> They don't just make up new features. And then they iterate. They go, "Okay". >> Start simple, grow on that, learn from the market. What are people using? What are they not using? Iterate, iterate, iterate. >> Okay, so with that in mind, working backwards from your customer, how do you see the feature set evolving for this functionality? How do you see it evolving as a product? >> Yeah, I mean, I think all of the BSS systems today have been designed with manual people on the other side of the screen, right? And we've seen chat bots take off, we've seen, you know, using chat as support. I think we need to start getting into more automation right? Which is really going to change up telco, right? They have thousands of customer support agents and you're like, "Dude, I just want a SIM, that's all I need". >> Yeah. >> Just like, where do I push a button and send an Uber to my house and drop it off or eSim. And so, speeding up business, empowering the subscriber. We know how to interact, we just went through COVID where we learned about different apps that overnight, you can like order all of your groceries and order all of your food and there it is, and it was contactless and... >> It's funny, you said future of work, which we love that term, "work". Workloads, work force, you got all these kind of new dynamics going on with cloud enablement and the changes is radical. And the value is there. There's value opportunities. >> I mean like, you know, where are the ARVR applications, right? Where your agent pops. I saw the demo. There's a strife in Austin and they're going to kill me 'cause I can't remember their name. But they had a little on your mobile phone, a little holographic customer support. Like, "How can I help you"? Right. And I'm like, "Where's that", like, imagine you're like, ATT, you're not like on the phone for like an hour and a half trying to like, figure out what's wrong. And it's like, you know, it knows what's wrong. It understands my needs and so, no one's working on that. We're still working on, keyboards. >> Right, that and chat bot is a great example because it's all AI, and where's the best AI? It's in the cloud because that's where the data is. That's where the best of modeling has been. (chuckles) >> I think your point, it's the scale of data. >> Absolutely. >> And machine learning and AI needs a lot of data points to get really good. I mean, I'm old, I'm 50. I graduated in 1993. I took an AI class from Niels Nielsen, like the godfather of AI, right? Okay, like that AI, even 10 years ago AI, it's just moving so quickly and it's now super affordable. >> Well, I really want to thank you guys for coming up and sharing that knowledge and insight, congratulations on the product and open APIs. Love open API's open source with some new revolution. Danielle and Robin. Thank you so much. >> Thanks so much. >> Thank you. >> Thank you. >> Congratulations. Thank you everyone for coming. (crowd applauding) (people whooping) Okay, back to you in the studio at Cloud City.