If you want to grow your business and get more attention, there's three ways of marketing that I found that work best and generate the best results. The first one is what I call content marketing. Content marketing simply means that you go hard at producing as much content, sorry for the ambulance, as much content as possible, meaning videos, articles, blog posts, you know, Instagram, anything that you can think of where people can consume that content, even forums. You just do it daily, massively, consistently, and that leads to really, really good growth. That's by the way what I'm doing. If you can, if you look back at my marketing here on this channel, I'm basically doing content marketing and that's my only strategy right now. Now the second way you can market is with what I call leveraged content. Now what leveraged content means is content that gets a lot of shares, a lot of comments. Basically a video, it could be one specific video that's really targeted to get a shitload of attention. For example, like the viral video that I made at the beginning of the year, which all I needed to do, it was a new Facebook page, I just posted it it already right off the bat, you know, got a lot of shares, a lot of views, and then I boosted it for a couple hundred dollars and it ended up reaching 100,000 people and half of it was organic. So essentially you get extremely cheap marketing that reaches a ton of people. Like if you really think about it, all my videos combined here got to about, I think 45, 50,000 people. This one video got 200,000 people. So that's a powerful strategy and you can either hire some sort of a marketer or an agency to help you make a video that will go viral. You don't even need to aim for viral, you just need to aim for something that people will share a lot.  Will this not work? If this is a good video that should get a lot of shares, you will get a lot of shares. It's really that simple. There's no question about it. How many you get, nobody knows. But if it is shareable, if it's really good content, it will get shared. And then when you inject marketing, when you inject ads into it basically by, sorry, boosting into it by promoting it with money on Facebook, then you really, really are going to reach the high levels of success with the video because you're going to get, it's going to feed into itself because the boost makes more people see it and then more people will share it and then more people will see it. So it has a really big effect.  So you might get one video that reaches, one video that reaches 50 people, even a hundred of these are not like one video that gets to 50,000 because when you get to higher levels of attention, then there's more people talking, there's people connected. Oh, you know the guy, I know the guy too, blah, blah, blah. So the more big the marketing, the more big it's going to be exponentially. Now the third level or third type of marketing that you can do, third strategy, is to simply find a marketer. And I learned this both from experience and it's also a combination of what I learned from Dan Pena about giving equity. So if you're confident, if you're believing your project enough and you believe in the revenue that it could create, so you already need to have some revenue, you already need to have something like, for example, what I have, like, hey, I have a business that does this much per sale. This is the conversion rate. That's how many views I get right now. If you help that, like, I'll take you on as a partner, you get 15% of the revenue. So for example, my average sale is about $2,000. So if it's 15%, you know, that means you get about $300 passively, just for being affiliated, for being one of my partners. And what you need to do is make me grow. So as long as you make me grow, I'm going to keep you as a partner. And if it's a really good partner, a really good marketing partner, basically, he knows what you don't know about marketing. So he's really good at that. He just focuses on marketing, you do the rest. So he tells you, okay, let's upload this video, let's put this, he does this, he does that. And his job is simply to give you more views. So while you're focused on maybe delivering the service, maybe hiring sales people, he is focused only on one thing and that's attention. So any good marketer knows to focus on attention. If you get a marketer and he's like, oh, the banner should be like this, should be like that, you know, I talked about the three levels, the root fundamentals and nuance level, basically the root, the big percent and the small percent. It's in the video called the three levels of success. You have to watch it if you didn't. And this guy, you know, is good if he focuses on the attention, getting as many views as possible. That's what a marketer should do. So you can get a good marketer like that. Again, 15% of a proven business will be very easy to find one because again, he just needs to make things happen. It doesn't mean he even, don't even tell him to invest money. You just tell him like, look, you tell me what to do and if we grow, then you get basically the 15% and I'm going to keep you around. So it's a really, really good deal. These are the three levels, three strategies, sorry for always confusing it. These are the three strategies and you really need to see where you are right now. I would use the first strategy as a baseline because that's how you grow an audience and actually grow exponentially with time. I'd use the second strategy to launch something, whether you want to launch a channel, you want to launch a product, basically when you want like a surge of attention for something new. And I use the third strategy if you really want to leverage other people to help you to make big, big progress.  Now, how do you find a marketer like this? It's actually pretty simple.  But beyond that, I have a very simple formula for, you know, leveraging people to help you with anything. And I'm going to explain it in the next video. So if you're interested about leveraging people and using them to help you, then check out the next video to see it. By the way, if you haven't subscribed yet, please do that. You'd love more content from me. And feel free to let me know what you think. And if this video helps you, which one have you tried? Which one are you considering trying? And if you need help implementing it, you know, I'm not teaching it because I learned it, I'm teaching it because I'm doing it. So let me know. I'd love to help you.


Organizations are rapidly adopting container technologies to accelerate agile cloud native application development delivery. But with the complexity of managing multiple cloud environments, organizations need partners to help them take the guesswork and risk out of DevOps and platform engineering workflows. Dell and Red Hat have joined forces to introduce the Dell Apex Cloud Platform for Red Hat OpenShift, which is designed to address the challenges and simplify cloud native deployments. Welcome to the future of native infrastructure is now. I'm Dave Vellante and I'll be one of your hosts. Later in this episode, CUBE research analyst Rob Streche will be joined by Caitlin Gordon of Dell Technologies. Caitlin is the VP of ISG Product Management for Multi-Cloud and DevOps and she'll be joined by Chris Morgan, Senior Director, Technical Marketing and Partner Products Executive for Red Hat's hybrid platforms. And they're going to talk about their new joint cloud offering. But first, I had the opportunity to talk with Sudhir Srinivasan, Senior Vice President, Multi-Cloud and Data Solutions and CTO Emeritus at Dell Technologies about some of the challenges of managing multiple clouds. So get ready because the future of native infrastructure is now. The rise of cloud native concepts created a rush to cloud, enabling a more agile development and deployment for applications. The challenge is multiple clouds create complexity in terms of variances in operating environments, tools and processes. And with me is Sudhir Srinivasan, who's the Senior Vice President of Multi-Cloud and Data Solutions at Dell Technologies to talk about some of these issues. In studio, welcome Sudhir. Thanks for coming in. Thank you Dave. Thanks for having me. Yeah, you're welcome. Now about a month ago, we met with Shannon Champion from Dell Technologies to discuss your new family of Apex cloud platforms. And today Sudhir and I are going to discuss what's new and we're going to take a closer look at how this next generation technology is bridging the cloud divide for IT. So Sudhir, let's recap if we could, the Apex portfolio approach, the strategy, the challenges that you're focused on for your customers and then specifically, what should we know about Apex cloud platforms? Awesome, thank you. Thank you Dave. I think it starts with what you said, exactly what you said, which is the complexity. The number one problem that we see our customers facing is more and more operational complexity because it's multi-cloud. Most of our customers are still trying to get hybrid done right and now they're having to deal with multiple clouds. So we talked about in the past our multi-cloud by design strategy and that really has three legs or three pillars, I would say. The first is we're enriching the public clouds by bringing our software defined storage assets into the public cloud so we can offer the same level of capabilities, enterprise-grade storage capabilities in the cloud. That's what we call our ground to cloud piece. The second piece is connecting the cloud operating environments back on-prem and that's what we call cloud to ground and that's what we're going to talk a little bit more about today, the announcement we're going to talk about. And then the third piece is optimizing that experience, multi-cloud experience to be able to give that cloud consumption experience subscription as a service, no matter where you are, whether you're in the cloud or you're on-prem. So it's this, we've taken a holistic approach to multi-cloud that really simplifies operations across cloud, on-prem, edge, wherever. And the trick is how do you deliver that consistency at all layers of the stack, right? All the way from infrastructure, all the way up to the application layer. And that's where this new stuff comes in. Okay, so the new stuff, the Apex cloud platform family, you're saying addresses operational consistency and this includes on-prem, correct? Can you tell me more about what these are? Yeah, so if you think about sort of cloud native, as you said, there's a lot of applications, modern applications are being developed in the cloud or in modern app dev environments like Kubernetes and containers, right? So what we set out to do was to bring those operating environments to the customers on-prem as easy as it is to consume in the cloud. And we've done this in the past with on-prem infrastructure like VMware, right? We've had a lot of success, years of success delivering that level of ease of use and automation in hyper-converged infrastructure on-prem. We're doing that now for multi-cloud as well. So we, just like we did in the past, we're now collaborating very closely with three partners, Microsoft, Red Hat and VMware to co-engineer these turnkey solutions. They're really turnkey solutions that dramatically reduce your operational complexity and ease of use. All right, so you got to giving customers choice, that's important and we've talked before about the need for this. I'm sorry, yeah, we're giving choice, consistency and control. That's what the Apex cloud platforms offer. Okay, you got the three Cs, choice, consistency and control. Okay, so choice is, in other words, any cloud on-prem consistency, we've talked in the past about sort of the need to abstract all that underlying complexity and have a common experience that obviously gives you control. How do you actually do that in these platforms? Yeah, great question. I think the three Cs actually start with consistency. That's the founding, the base capability. And we achieve that through using common building blocks across all of the Apex cloud platform family. And the building blocks are actually three of them, right? The first is the hardware. So we bring to our industry best industry leading power edge servers. The next generation is sort of the latest generation of power edge servers, which are all based on the Intel fourth generation Xeon scalable processors. So you're getting the best compute across all of them and it's common. The second piece is the software defined storage. Now that again, independent of which stack you're using, which cloud stack, you're getting the same software defined storage across all of them. So you get that consistency. And then the last piece is the management and orchestration software that makes this platform be what it is, which is a turnkey solution, right? Extreme levels of automation that give you a sass time to value. And that's also common across all of them. So discussions like this, I like to invoke Einstein, like an adapt an Einstein saying. So my take on this is move as much data as you need to, but no more. Now, but you still have to have data mobility. So how are you addressing data mobility for customers? That's actually, we talked about infrastructure complexity. Data is actually another yet another level of complexity for customers. Data is everywhere. Sometimes you have to move the data to where the application is. Sometimes you move the workload to where the data is. And we set out to solve this using what we call our universal storage layer, right? We talked about the common storage. So it's this storage stack that's available both on-prem and in the clouds. That's how the two pieces come together, the cloud to ground and the cloud, the ground to cloud. So we get, the customer can get the same storage services and operational interfaces everywhere. And not only that, because it's the same storage stack on both sides, we can actually leverage very efficient data mobility techniques or mechanisms between them. So we're moving data in much more efficient ways. And because it's the same operational interface, customers don't have to re-platform their application, whether you're going from in the cloud to on-prem or vice versa or so. Yeah, so obviously moving data can be time consuming and expensive. So you could give us some use cases where data mobility, where you're kind of making that an enabler as opposed to a roadblock for customers. Sure, I mean the most common one we get is again the application delivery one, right? Where customers might want to spin up a development environment in the cloud to enable their developers to actually develop the application, but they may choose to deploy it in production on-premises. You can do that now without having to worry about it being different across the two locations. The one that's even more compelling I would say is the world of data and especially now with AI, right? The speed at which or the rate at which customers need to consume resource infrastructure to do analytics and to do AI is just incredible. And so you may not always be able to have those resources in one location. And with the universal storage layer now, you can actually move data to wherever you need, wherever you might have the GPUs, for example, to be able to do your AI or machine learning over there and then bring the results back. Got it. Okay, so you got this common framework for management and orchestration. Can you add a little bit of color there and tell me more about that? Yes, that's what we call our Apex Cloud Platform Foundation software, you know. This is the software that we have spent years now developing in the world of, excuse me, in the world of hyperconversion infrastructure and software-defined infrastructure. What we've done now is taken that software which delivers all the automation and lifecycle management and make it available to beyond just the hyperconversion into this multi-cloud infrastructure. And because of the experience that we've built into this, you know, customers are seeing as much as 90% reduction in deployment time, for example, or 88% reduction in the number of steps required to deploy a stack, a development environment stack. And this, not only do we do the automation across the Apex Cloud Platforms, we've also integrated this foundation software into the partner's management plane. So what that does is it gives a customer that similarity with their cloud environment. So they can still leverage that, but it also gives consistency across the cloud environments. So it's the best of both worlds. This is good. I mean, it's impressive. You guys taking a holistic approach to the problem.  Any closing thoughts, Sidir? Oh, look, we are very excited to bring the Apex Cloud Platform family. Last month, we announced the one for Azure and today we're announcing the one for Red Hat and OpenShift. And it's going to bring tremendous value to our customers and partners and giving them choice, consistency, and control across their multi-cloud estate. That's good. You guys doing some good work. Thanks for coming into the studio today. Thanks, Dave. You're welcome. All right, about a month ago, Dell introduced the first platform in this new Apex family with the Apex Cloud Platform from Microsoft, Azure. Now it's time for everyone to hear more about the next offer to market the Apex Cloud Platform for Red Hat OpenShift. So stick around as Chris Morgan, who's the Senior Director of Product Management at Red Hat, joins Caitlin Gordon, who is the Vice President of Product Management from Dell, to dig into this exciting new offer and explain its potential to transform OpenShift operations on-prem. We just heard from my colleague Dave Vellante and Sidir Srinivasan from Dell on the overview of Apex Cloud Platform. I'm Rob Streche, Analyst with theCUBE Research, and today we're gonna talk to some people from Dell and Red Hat about a joint cloud offering. I'm so excited to welcome back to theCUBE Caitlin Gordon, Vice President, Product Management from Multi-Cloud and DevOps at Dell, and Chris Morgan, Senior Director of Hybrid Platforms at Red Hat. Welcome. Thanks for having us. Yeah, this is fun because I think, again, when I look at cloud and I look at hybrid and I look at going different places, I really do think Red Hat and Dell, these are two of the major brands that are pretty much everywhere in here. So Chris and Caitlin, today is really exciting because you're here to announce the Apex Cloud Platform for Red Hat OpenShift. And I think, again, this is one of those that is super exciting in the fact that, you know, you can take your applications that you've containerized and such multiple different places. So Caitlin, can you share with us what brought you to this partner together and bringing this to market? Yeah, I mean, it is definitely an exciting day for us and our customers for a long time have continued to struggle with how do they get better agility? How do they get more flexibility in where they build, where they deploy their applications? Now that was for a number of years, virtualization increasingly that's containerized workloads, Gardner predicts that 95% of enterprises are gonna have containers deployed in production by 2028, which is not that far away. And really for customers, that means it's a combination of public cloud and on-prem. And we knew that we really wanted to help simplify that and experience on-prem. And there was clearly only one partner to work with to do that. And that was Red Hat. And that was really why it was a natural combination of Dell to simplify that experience. Red Hat is the leader of container orchestration on-prem to come together to bring this to our customers. Yeah, I'm still trying to figure out who the other 2% is that's not gonna have containers deployed in production because I haven't talked to a customer who isn't building in microservices and containers. So Chris, why don't you share your thoughts? You don't have to share them particularly on Caitlin, but I'm the joint offering here and what are you bringing? For me, the journey started, I guess, 18 plus months ago. And I'll be honest with you, when we were first asked, it's like Dell again. But now it's just what's been really exciting is are the changes. This is about creating an experience, as Caitlin mentioned. Before, we've had a long history with Dell where it's been about putting our operating system on a piece of metal. And this is really about now taking a lot of that and bringing it together. I mean, in many ways, we've been about hybrid for a long time at Red Hat. And so this is really an extension of that where hybrid's becoming more about the experience than just a consistent technology. Yeah, I think that that is the key is doing it together and being very integrated because that's where platform engineering needs to be easier and things of that nature. So let's kind of get into Apex Cloud Platform for Red Hat OpenShift. And I will get it right most of this time.  Yeah, in a lot of ways, our partnership is not new, but the level of this partnership is what is new. This is truly a jointly engineered. Chris and I talk a lot because it is truly jointly engineered. And it's a turnkey appliance that we have built truly to simplify the experience. But there's a lot of really unique things about this platform. You know, a lot of what we talk about now is that this is so unique that we're having to really explain the basics of it to a lot of people because it is so unique with nothing any either of us have ever done before. A couple pieces of that, right? It's optimized for bare metal, which we'll dig into later hopefully. That alone is very different. We've unified the application and the data plan.  And it brings together the compute, the storage, the container orchestration, all in one turnkey experience. I had to double check these numbers from my marketing team. But we have simplified the management and reduced the management tasks by 98%. So there's like another 2% left of something left that you still have to do. I think it's a click that you still have to do. You've really just. I think you calculated it wrong. I mean, you may have to double check it. So I think it's right. I think you calculated it wrong. The simplicity is at the level of simplicity that we're bringing here. And the optimizations on bare metal is just extremely unique. Yeah, and I would add, it is unique, but it's also unexpected. We here, as I'm sure all of you here, oh, we're going to the public cloud. And I kind of, I don't know if I could say, but it's just making bare metal sexy again in some ways. It never went away. But I think as we talked about, there's VMs are considered legacy now. And so this is really a way, if you want to modernize the infrastructure, it's a way you bring your containers and your VMs and gosh, even other clusters together on one control plane. And that, to me, is really what makes it a unique offering for those customers that are looking to upgrade their infrastructure, but keep some things the same. I mean, we all still have mainframes, right? And those were supposed to go away in the mid-90s. And so I think it's the same that we're going to see here too. Yeah, well, it's funny because I also know that you can run OpenShift on a mainframe, which is another funny thing. But I think a lot of it is about the customers and why they should care, right? I mean, customers to our discussion already are really leaning into microservices. And we were talking and I think on average, the customers have in their cloud native applications, they have something like 18 to 20 different containers are part of applications. So again, that manageability and ease of use and that integration from the bare metal has to be there. So Caitlin, why should customers really care about and how are they going to benefit from this collaboration? Well, the first thing is that that bare metal piece is so important. We've talked about it. That's a cost to complexity reduction. It's also a performance increase for your workloads because you really have removed that layer. And it's actually gives you security benefits as well because you've really reduced the attack surface. So that piece of this is really, really unique. And then what we've built together is just something that we call it a turnkey appliance, but it's really a combination of the power of Red Hat software, the power of Dell software and the power of the Dell infrastructure really coming together to provide that unique experience to our customers. Yeah, I think to me it is really about, kind of the build, deploy, run aspect of it for cloud native applications. I think that to me, making platform engineering kind of easier because let's be real, platform engineering is the new IT and you can put whatever name on it, but people have to come up to speed. And we will put a new name on it, which we will. It's already happened. And I'm not surprised it's not an acronym, but how does this really, why don't we start with you, Chris? How does this really meet the flexibility that customers need? Because again, this isn't new, but it's new in how you make it easy for them, right? So, as you mentioned, there's a modernization happen. When we first did all this, it was about modernizing the apps themselves when you go to containers. And to your point, the platform engineering role continued to evolve. It's like, well, they need the infrastructure in order to support that. And when we talk about the simplicity and things that Caitlin was mentioning, to me there's a couple of personas there. There is that platform engineer and admin. They're gonna love this. Like, literally it's their utopia. I can't even begin to tell you it's ridiculous. And then on top of that though, if you're a developer, if you're used to working with OpenShift for your apps and all the different things we have, it's that same experience wherever you've been doing it before. Except now it's nicely integrated to a point where even Dell support is a part of this appliance. So right within the console, within the OpenShift console, there's this phone home capability, which I absolutely love myself because we don't even do that anywhere. This is just absolutely fantastic. And so what's in it for the customers is that simplicity that you've got a best of breed. This to me mimics offerings that Red Hat has with some of the hyperscalers and that level of partnership. And I just think the customers would just benefit directly from all of it. Yeah, what about, what are you seeing? Yeah, I mean, I got geeked out on the infrastructure side like a little bit because I have to. It starts at day one. And the deployment time, when you look at how quickly you get to deploy this, it's actually in a OpenShift and bare metal it can take up to 10 days to deploy that and kind of a standard build it yourself approach. What we've been able to do here is reduce that down to hours. So a 90% reduction to deployment time, which is really powerful because that means you can be up and running, building your applications faster and deploying them faster. That means you get to really invest in your business. I mean, that's very powerful. But of course that happened, deployment happens once, so we're proud of that. But it's really, it's that day two operations benefit that we talk about, that yes, it's fully integrated into the experience, right? All a single line of support, but some of this kind of magic from the Dell side is what we call the Apex Cloud Platform Foundation software. And it really welds that whole experience together. And it does things like a continuously validated state all the way from the BIOS to the firmware all the way up to OpenShift to make sure that that entire stack is validated to work together. We ensure that when you do an upgrade, it's a seamless one click upgrade. And you have the peace of mind that we've worked together to make sure that whole stack works. So it's easy to get up and running. It's easy to manage day to day. So then focus your energy on then using that platform to actually build those applications. Well, I'm so glad you brought that up though because I want to even double click further on that day too. That's really what this is about. So in the Kubernetes community in general, I don't care what distribution it is, OpenShift or otherwise, upgrades are one of the main complaints. And so what's really beautiful about this is you're not upgrading OpenShift, right? You're upgrading the Apex platform. So maybe the next release might have an OpenShift upgrade in it. It might have another component in it. But you don't worry about that as the administrator, right? We're building the magic as it were inside to allow that kind of seamless upgrade experience. Yeah, I love the outsourcing the S-bomb to Dell basically in helping with the OpenShift stuff because to your point, when I talk to people like CloudNativeCon, KubeCon or wherever or just generally at any of these other events, that is one of their big things about, like you said, being close to being hyperscaler. How do you have a true cloud platform that takes away all of that worry for you and really makes it simple? Because that has to be there because people are so used to it. Yeah, well, that is actually was a mission statement that was given to me by the Red Hat CEO 18 months ago. He says, Chris, I want to slide in a pizza box and I want it to boot up and say, are you going to join an existing cluster or a new cluster? And that should be the experience. And we're pretty close right now with this appliance, I have to say. And everybody loves pizza boxes. And pizza for that matter. It's the best pizza box in the industry. Absolutely, they have whites. Yeah, exactly. But so let me kind of shift gears a little bit because I think we'll get kicked off the interwebs if we don't talk about AI. And I'm pretty sure that for many companies, AI and the hype around it, and there's some reality, we even have our own AI and we have our own LLM and stuff like that. I mean, who doesn't? Who doesn't? If you don't, you're not cool. You've got to be one of the cool people now. And I know both companies have been investing heavily in AI. So how is this solution really helping customers meet those business objectives with AI? Colin? Yeah, I'll start with the, again, kind of the bottoms upside a thing. But I talked about the fact that this is a truly appliance and fundamentally there's two core components so that there's the compute and the storage and they both play an important role here. On the compute side, we have fourth generation Intel processors. So you've got the throughput, you've got that processing power to really handle those AI workloads. And at the same time, we all know that AI is pretty useless if you don't have the data. So the storage plays a very, very important role here, which is having that linear scalable software defined storage, something we call the universal storage layer. Not only is it the storage that is in these appliances, the Apex Cloud Platform, but it also runs in the public cloud. So you've got that portability of that as well. So you have the flexibility to use that AI on-prem and also the portability to be able to connect into the public cloud as well. Yeah, and thank you, by the way, because the AI itself would be upset with us if we had to talk about it. It's true. But for us, you know, we've been talking about hybrid cloud for a decade and I'll be honest, sometimes we have to explain what that actually means. AI now is actually validated why you need a hybrid cloud, like you just mentioned. You know, the data is everywhere and you need a consistent compute everywhere. You need to be able to, you know, fine tune your models, run your models in a different space. And so for us, this is really foundational. In fact, there's some other things we're working towards, you know, with our OpenShift AI initiatives to build on the work we're doing here that I think customers are gonna love because I'm seeing a lot of buzzword compliance right now. Everything is chat GPT, especially in the enterprise, you know, they like to understand things like canonical source and provenance of the things that train their models. And so for us at Red Hat, like again, it's very foundational for us to continue that story and get the foundation of a hybrid cloud to create your AI. I'm sure we can do an entire segment on this because I think the stuff that you're doing with Intel and with others underneath the hood, plus what you're doing in the OpenShift platforms and there's multiple on top of there, I think we definitely could, but let's park that for another day and let's kind of take a look at this from and kind of bring it home from perspective of partners. I mean, I'm partners in near and dear to my heart and Dell is really investing in. What is the feedback that you're getting from partners around this, Caitlin? Yeah, it's really exciting, especially when it comes to things like our service provider partners, the level of, you know, keeps using the same terms because it's so true. The level of experience and simplicity that we're building into this platform actually enables them to really focus on the value at services they can bring around that and they can optimize the services that they're bringing to that platform in a very unique way. So Kindrel's a great example of that. They're gonna be taking this new platform and expanding their existing offerings to be able to bring what already is an existing partnership both from Red Hat and Dell and really bringing that together. Yeah, that's powerful. Yeah, that's been the really exciting thing is when the partners are seeing that we're already working together. Because I mean, we're partners and so we're kind of coming to them as one entity and I think that's something that we've gotten a lot of feedback on as well that they're looking forward to is that best of breed. So the same benefit we've talked about for customers, the partners are seeing the same and as Caitlin said, they're excited to be able to put their expertise on top of this and what their additional value is and it's one less thing they have to worry about. I can totally see that with especially in the managed service provider cloud service provider market, that's just huge for them to now have that container reliable container on a reliable platform that makes it easy to use because that's their margin where they get that and that's great for them. I mean, it's fantastic and it's fantastic for their customers who want to get up and running really quick. And keep in mind, right? We're also hearing from, you know, Kindrel and others, it's also about the virtualization. Remember within OpenShift itself, it's native that you can manage VMs, containers and then even other clusters. And so it's about if you also want to modernize your apps and your infrastructure, now you've got one complete solution to do that. So Caitlin, super exciting, you know, this announcement. Where can partners and customers alike find out more information and where are you going to be talking about this? Everywhere. You can start with dell.com slash OpenShift. Of course you could talk to a Dell representative, partner representative. And excitingly, both companies are going to be at Kube.com coming up in Chicago in November. I hear Chicago's beautiful in November. So if you'll be there, come by the booth. It's like after Detroit, didn't people learn their lesson? I was like, come on. Like really? Are we choosing that again? All right. But we'll be there. I think Red Hat, you'll also have a booth. So great time to come by. We can have some hands-on experience with what this is really going to look like. And we'll be there as well. And I'm excited to be there myself. So I think it'll be a lot of fun. I think get to talk all kinds of cloud native back then. So I want to thank you both for joining me. I think, again, getting into this has been super helpful. And I really appreciate it. So thank you for joining. Thanks for having us. Thanks, Rob. And if you need more as well, as Caitlin said, there were some resources. There's also a resource tab down below. And we'll be back with more around this. This solution will be following it very closely here on theCUBE. And we appreciate you for watching. Thank you and take care. Oh, welcome to this analyst brief, where we're discussing Dell's Apex Cloud Platform to Red Hat OpenShift and their announcement around that. I'm Dave Vellante and Rob Streche and I will unpack the market for cloud computing and what the Dell Red Hat announcement means to customers. First, let's take a reminder look again at cloud usage. You know, the movement between public and private clouds, it continues. But looking at the data from ETR, we're seeing that the market is becoming much more balanced. It's not really reached in equilibrium yet, but it's definitely the balances tipping back toward on-prem. And this chart from ETR shows the percent of usage of public clouds relative to private clouds, specifically within the S&P 500, which represents a very large portion of spending well over half of IT spend and is generally considered a bellwether. Now the data shows about 43% usage of public cloud today growing to 55% by January, 2026. Now note that the expected 2026 figure is down from 10 months ago, implying that the market is reaching a more balanced state. As we said, i.e. many workloads are where they belong and the steep momentum to migrate off-prem is stabilized. Rob, what do you make of this data? Yeah, I think it's super interesting in the fact that cloud has become not a place, but it's really an operating model. And I think a lot of what they're looking at is the fact that this equilibrium is because there's better tooling coming to the on-premise. And things like the Apex Cloud Platform are one way that people are looking at how they simplify their life. And AI, of course, is going to be the next battleground here for tooling. Oh, absolutely. Okay, let's look at another set of data. At this time, we're going to look at the overlap of Dell inside 144 Red Hat accounts within the ETR dataset. So the chart shows net score or spending momentum on a platform that's on the Y axis. And presence in the dataset or overlap in these accounts is on the horizontal axis. We see that 46% of those 144 Red Hat customers also have Dell infrastructure installed. So you can see on that X axis, Dell is the dominant player with a greater share inside of these Red Hat accounts, more so than any other competitor. And Rob, I recently talked to Sadeer Srinivasan of Dell and discussed the Apex Cloud Platform family. Then you spoke with Caitlin Gordon of Dell and Chris Morgan, who's Senior Director of Hybrid Platforms at Red Hat. Dell recently announced expansion of the Apex Cloud Platform with the addition of Apex Cloud Platform for Red Hat OpenShift. So Rob, what are the relevant customer requirements that people really need to know about? Yeah, I think what they're really looking for is how do they deal with demand for agility and flexibility? I think that's at the top of the list. And they're trying to understand, hey, it is a cloud operating model. We're going to expand, we're going to keep expanding. How do we really deal with that in an easy way? And it's also a shift towards containerized workloads. I think you and I have been talking for quite a while as people go to microservices and build those next-gen applications. A lot of it is in these containerized workloads where there may be 10 to 20 containers that actually make up an application. And I think there's also a simplified combination of cloud experiences because they're not just going on-premise with their cloud, they're going to other places, like they're going to co-location, they're going to other hyperscalers. And they need a operating model that goes across all of those. And also I think they're looking at it and saying, hey, we're a Red Hat shop and we really like Red Hat's experience and their expertise. So we're trying to leverage that and we have their tooling already. And I think also part of the big thing that they're looking for is a true partnership between the organizations and how do they jointly engineer these things together? Because as they move towards a hybrid experience, it's really important to know that you have that supportability going forward. Yeah, one company can do it alone these days. How do you think in your expert opinion, this announcement addresses customer requirements and or changes them? I think it really is about the unified application in the airplane that the IPEX cloud platform is bringing to bear for customers is a really a big piece of it. It's an operating model that is very unique to what they're bringing out. It is very cohesive. I think it's also they're looking for that all in one solution which compute storage and container orchestration is built in so that when they're getting up and running, it's really quick to get up and running and they know where they're gonna go and it's the same tooling across everything. I think the simplified management, modernized infrastructure to your point, hey, how do I get GPUs and other pieces of infrastructure into the compute layer where I'm building these microservices applications? And I think, again, it's the adoption of those microservices and containers that's really pushing it to be more than just, hey, we go out to the cloud and this is where we're always gonna build. I think bare metal has an appeal from a cost factor perspective as well and the benefits of bare metal are really coming true and starting to ring true, but it has to be turnkey.  So double-click on the announcement. What exactly did Dell and Red Hat announce and why should customers care? Well, I think they really are going after the simplicity and that cloud operating model. It's not just a rehashed, hyper-converged infrastructure, HCI as we've talked about before. It's not just gen two of that. It's really a cloud operating model on top of the hardware and software that's integrated in there. So I think really that makes it cloud-native and cloud-native applications really easy to deploy and run. The Apex Cloud platform for Red Hat OpenShift really takes advantage of the leadership role that OpenShift has in Kubernetes. And I think Red Hat really has a developer ecosystem, a DevOps ecosystem that is super strong and allows people to use the kit in the stack for DevOps that they're using today and apply it to this platform. It's a powerful, I would say relationship, not only for Red Hat, but for Dell, especially in their channel partners where they're leaning into the channel where organizations are going, hey, how do I have a better hybrid experience and looking to that channel partner? And really, ultimately, customers are spending with their money because they want an operating model that not only works on-premise or in colo, but also can scale up to those hyperscalers for when they're using that for production. And it gives optionality to the customers and to the channel. I think both of those constituents have been looking forward to this day for quite some time. So, Rob, thank you, appreciate your time. Yeah, thank you. Okay, and thank you for watching this Analyst Brief. We'll see you next time on theCUBE.


My name is Tom. Today I'll be talking to you about servers, why they can't be trusted, and how we mitigate that in EtterSync, which is a project I work on. And this is, you know, you can find the slides over there on the Fossum website. You can scan the QR for it to get the slides. And this is it. Let's jump in. So, first of all, let's look at, like, simple server communications. So, like, the most basic thing, how it looks like. So you have Alice, the user, probably she uses TLS or whatever variation, and connects to the server, so everything is encrypted. And let's, you know, for the purpose of this talk, let's assume that everything between Alice and the server is safe. There's no man in the middle, although this is actually a risk, especially if you use a company laptop and they store a root certificate or anything. It is a risk, but let's assume not. Let's just only talk about the servers today. So, let's start by that communication. What are we leaking when we do that? So, first of all, we have data. Actually, if we use Gmail, for example, we leak the emails, we leak the calendars, we leak any personal notes that we may have, our deeper secrets, secret business information. You know, we're going to do a minute, like, by this company or whatever.  Time of access, so when in the day, I log in, so if I always log in, let's say from 9 to 5 in London time, you can probably assume, you know, this is my business hours, I work in London, I live in London, so that also a lot of information is leaked there. Which data is used and how often? So, for example, you will always call a certain person, you know that person is a person of interest.  And again, when specific data is accessed, so for example, if I have my computer, during work hours, I open this, during after hours, I open this, so you know this is personal information, this is work information. There's a lot actually being leaked there. So let's look at some parts in specific. So let's look at exploiting social graphs. So we have a group of people, we know that we have four, I don't know, rebels or whatever we're trying to catch. We already caught three of them, A, C and E. And now, just looking at the graphs, like by who they know, so let's assume they all use signal. So just by getting access to the signal server, which signal is usually, I mean, it's encrypted, everything like best practices, but still because they leak the social graph, like who knows who, we can already know, we can know that B, just like you see by all the connections, that B is actually part of the group. And we also can see that D, that we actually never knew existed, is also part of that group. So all of this, by using best practices and to an encryption, all of that, this is a leak. And another example actually I really like giving is exploiting access patterns. I don't remember which government agency was that wrote a report about this, but these are two mobile phones. And the graphs are access times to the server. So like when they, essentially when they're on. So one of them is a burner phone used by a spy, and the other one is a normal phone. It's very easy to see. I mean, it's a good idea to turn your phone off because then you can't be triangulated, but you see, you still leak a lot of information. Now all of a sudden you're a target, and if you're A, you're not a target. Your information is no, but you don't stick out. But you know, this is all like a bit theoretical. So let's take it to something more practical, which I care about. A cloud app, sorry. So cloud app, essentially, is how most information, like most address books nowadays are synced. It's used by iCloud, NextCloud, OnCloud, everything with cloud in the name, essentially. And it's a good, you know, it's a standard, so it's great, it's inter-portable, supported in every client. But let's look at roughly how it works. So you have Alice, Bob, Cher, all of those are my contacts. You just have files on the server in clear text with all of the contact information in each one of them. So let's look at how, you know, what's leaked there. So first of all, all the address books information. So yeah, I have, if I hack the server, I have all the, you know, I have all the phone numbers, emails, positioning the company, relationship if you put it, like I'm very pedantic. I have addresses, I have everything in my address book. IP address, obviously, you're connecting to a server. And social graph because you can see which contacts I have and which contacts have me and what groups I group them. So if I had, oh, people that work on enlightenment, which is another project I work on, this already gives you a very good image of groups. And time of access, obviously, when I access the server. And again, which data, like recover, which data, when do I use it and everything. So let's, you know, let's solve some of them. Like it's not a big deal. You can use Tor to hide the origin. You know, Tor is not always perfect because first of all, it's a bit slower nowadays. Sorry, it's a bit slower. But also it doesn't work with all services. So Cloudflare and another, like other services, flag it because a lot of spammers use it. So it's, you'll have issues. You'll have to fill in a lot of captures while using the anything. And another thing, which I don't know actually if this is verified, but I would assume that every government agency flags you as a person of interest the moment you use Tor. Like, it's easy to detect and I'm sure they do it. But it's not verified, so don't take me to it. And we can try to control the access patterns. So I think, I don't remember if it's true, but I think Satoshi Nakamoto, the guy who did them, or guy or guys or girls or, I don't know, what combination of things, that did Bitcoin, used to write posts and emails, like in different times of the day. So you can't know which continent, which country, which everything is from. And another example of access patterns is when, another Bitcoin example, actually, there really, I don't know, it was a lot in the news, is when the guy behind Silk Road, Ross Ulrich was caught, they were monitoring the server and waiting for him to log in. And then by just seeing this access pattern, they were waiting for him to unlock everything that's encrypted. So they waited until logged in. And then this was enough of a cue for them to raise him and, you know, and go after it. And this again, another very easy leak, that it's obvious, but we leak. And another solution, obviously, is trusting the server. So using a trusted provider, I don't know, Google or whatever, we do trust or hosting your own. Obviously, the title of this talk kind of means that I don't believe in many of that. So should we even trust the server? It could get hacked. We get a lot of hacks. Everything is hacked nowadays. And, you know, it's, every server is running a lot of complex software. It's so many, you know, so many places to have issues. And even at the sync, I don't even know how many dependencies I depend on because I want, you know, I want the Java, like for the Android client, I want the Java runtime library and I want probably some, not Google stuff, but I don't know. I have Gson, like passing JSON.  So it's better to protect them and be proactive. And it could get stolen. Like, literally, someone could break into your house if you're self-hosted at home, still the hard drive, and just steal all your data. Again, maybe it's not, it's not interesting for you, but if you're a high-profile lawyer that does a lot of, you know, high-profile cases, you are a target that will get attacked and this is a real threat. And with hosted, you can have rogue employees. So employees are actually selling your data because they're evil or, I don't know why else they would do that. They're compelled by the government or compelled by the mafia or whatever. All of those risks that exist. And also, when it comes to self-hosting, and don't get me wrong, I think everyone should self-host, it's a lot of work. You have to be a techie, at least to an extent to do it. You have to make sure that your finger is on the pulse with really making sure that you're always updated to all of the latest security issues and all of that. So it's a lot of work and it's not that available. So hosted solutions, I think are essential to make a private internet or private world. And this is why, again, I try to make sure to create like an environment where the server can't be trusted and we can use hosted solutions safely. So let's talk about reducing service trust. So first of all, end-to-end encryption. I mean, I'm biased, but don't use a project that does not or a project or a service that does not do end-to-end encryption. It comes with flaws, but for example, if you lose your key, all your data is gone. This is why it's not mainstream and everywhere, but still, you know, there are solutions to that as well, like escrow keys, like just end-to-end is the bare minimum. And you can do mostly offline operation if possible. So let's go back to the COWDAF example. Let's assume I want to write a web client. So normally how I would write it, you have a website, you click on a link, open a certain page, and when that page is open, it's requested from the web server. So I want to see Alice's contacts. I click on Alice. The page is requested from the server, so the server knows I viewed Alice. Another alternative would be to write it all in JavaScript and then on the first time you visit the website, all of your contact list, which is probably, if you're crazy, one megabyte, which is less than my logo, most likely. I mean, in most, or the JavaScript framework, it's really low compared to everything else that you serve. And then always access the data from the local storage, from the local cache, and then you don't leak that information. So there are a lot of solutions to make that possible. And another thing, and I put in a question mark because you can fake access patterns, so you can, for example, when you edit a contact, you can fake edit five others every time randomly, so you don't know which one you edited, but I'm sure I'm not a mathematician, but I'm sure that with enough statistic this, I mean, it will be uncovered. Yes, I don't know if this is actually a sustainable solution. So let's talk about hard and card-off. So we know the problems, we know how to solve them, let's start solving them. And so, first of all, as you can see, we now use IDs instead of the names, so everything is secret. We enter any script, all the data, so nothing is visible to the server. And you can see which one is changed or anything like that, but there are still issues. For example, let's assume I just, you know, I finished this talk, I met, actually just before, I met Caleb, we exchanged contact information, I put it on, now all of you, including whoever's seen it online, knows that the moment, let's see, this file was created, it's Caleb, like you don't need to know the data, but you know by the date of creation, and the fact it was on camera, that it was added, this is enough, this is enough, and now every time, for example, I edit it, I call him, and it updates the last time he called, you can see, oh, Tom called Caleb. It's like all of this information, like it's not obvious, oh, it's encrypted, it's fine, no, it's not fine, because it's still identifiable. So it is a risk, and it's a risk that's not solved by end to end encryption, just like that. Okay, let's go, I mean, this is it, I mean, you know, like we say, this is all we can do, but it's not actually, because we can do much better. And let's go at it. So as I said in the beginning, our data, like our servers cannot be trusted, so our data can also be manipulated by the server. Let's look how. So I don't know if a lot of you do encryption, but like a basic example, like of bad crypto, is encrypting, but not signing, or encrypting, but not doing any sort of message authentication.  So I want to have some access level storage in my app. Let's, I don't know why, like I want to, this is the people that my app automatically support, automatically will expose accept requests to join a group. I don't even know what it does. So it's encrypted, so I know the server can touch it. And the default level is zero zero, so no level. But just by changing one bit, or whatever you want, you can just scramble and write, give another encrypted chunk. All of a sudden, like it changes to 19, like the level. So it's, I can't control it. I don't know how to change it to be one, but 19 is already good enough, especially if you do Boolean comparisons, so you do true or false. So I mean, this is just by being able to touch the data without it's end to end encrypted, I can't see it. This is enough to manipulate me as a user. Like again, this is not a real problem, you just HMAC or like use message authentication codes or signatures to make sure no one does it. But this is a real problem. Let's look at another thing. So we have, we have the hardened card of, and I just added again, a contact, or I just added a to-do item, or I just added a calendar event, because let's say I have a court hearing next week, I just added it, and my adversary, like the people on the other side, obviously, so they saw I added it, they hacked my server and just omitted this file. I have no way of knowing, I mean everything again, end to end encrypted, everything is safe, but the file is omitted. There's no way for me to know the file was omitted because this is normal operation, of course. Files get deleted, get added, I add a contact, I remove a contact. Like so this is another problem, and again a server can't be trusted. So this is easy to solve. You just verify the state, so you do any sort of signature authentication code or whatever, and then like every time this is changed, I will get notified. But again, there's another problem with that, which is data rollback. So let's assume I had, like I just had a state that is valid just now, I added a contact, now people want to remove this contact, all they need to do is serve me, again the old state before I added a contact. This is it, so again a server, no access to my data, I'm signing the whole state, I'm making sure that the state cannot be manipulated, it's still I can get attacked. Which is again, don't trust your server, never. So the solution I came up with, and I mean it's not, obviously it's not me, it's like built on top of like a lot of work by a million of other people, is tamper proof journals. So what it is essentially, is that instead of adding files, instead of adding contacts, what I do every time I add an entry, and so for example here I add Alice, and then I added Bob, and then I realized I had a typo, so I changed Bob, and then I deleted Alice, because we're not friends anymore, and all of this is just like every time, append only, append only, so you can't really know which data is which, because everything looks like, actually let's jump to this, like an encrypted blob, so this is how it actually looks to the server, something happened, something happened, and everything is end to end encrypted, so there's no way for the server to know what happened, and also the server can't manipulate anything, because the UID is every ID of every chunk on the block is a verification of the contact in the previous block, it's essentially like get, just encrypted and signed, and so every time, if I try to remove this, I'll get an integrity error, if I try to just switch them, I'll get an error, again, an error, and all of this protects from that, and because I can't remove anything, I only append, I can verify that nothing is missing, because if I added, I added a contact here, and then I added a contact on another phone, so the server can potentially just not show me the new edition, it can show me, it trimmed the log for me, but then when I try to add again on the other one, it will get a clash, there's no way for the data to be correct, unless again they could diverge it completely, but then the server has to identify each time to know exactly which is which client, which is a difficult task. Okay, so let's go on. So let's see how we protect. So as I said, it's immutable, so data can only be appended, no modifications are allowed, everything is verified by the client every time, like get, so every time you had an error with get, you would get the same error here if a server was trying to manipulate your data, it can't be manipulated or faked, you know it's you. Again, PreviewD is also signed, so there's no emission or reordering, and every, again, like get, as you can see I very much like get, everything is distributed among all clients, so let's assume the server, and this is something I didn't talk about actually in the hardened card, let's assume a server was hacked and everything was deleted, this is it, I'm like actually you know what, I don't care about him finding out, but if, again sorry, but if everything is distributed to the clients and every client does not say oh, it's missing on the server, it means it's deleted, I should delete it here, instead they verify it, so in the case of mass deletion they would just not do anything, there's clients, and we'll be able to recover all of the data from the clients themselves. Let's talk about previously unsolved attacks, they were not solved in the cardoff case, so which data is accessed and modified, everything is done locally, so there's no access, like no one cares about access, and modified, you know there's a modification, but you don't know which one, because that part is also encrypted, so this is actually, it's not entirely true, because for example you can say, you can analyze, do some analysis to know by the size of the message, so for example a contact is probably one kilobyte, but a calendar event is maybe, actually it's probably the same size, but like an image would be much larger, so you could do some analysis to figure out what's what, but again like I said in the previous example, you can fake it, you can fake it, and you can hide it, and you can create fake messages, but it's wasteful. Data omission and rollback, we solved as I said, so that's just like a few words about what Edison is, and how it's used there, like a real world example, so essentially it's secure and encrypted, and you can use it on your own, obviously, use the journal, and personal information, Cloud Sync, so essentially, Syncs you call context and calendar among your Android devices or web, or there's also CalDAV and CalDAV proxy for the desktop, so you can just use Thunderbird or whatever you use. Yeah, I use it everywhere, it's seamless on Android, so like you just use the same apps you always use and it works like a Google account essentially, just encrypts in the background. And the journal format is very simple, you have the UID that I mentioned, and then like in every time, every, like I change, I snapshot, again like it, I snapshot the whole format itself, so all of the calendar event is snapshot every time, so even if I delete, I have a latest snapshot of what happened. Another nice benefit of this is the change journal, so now I know this is like my shared reminder as calendar, so I know I need to feed the cats, go to the supermarket, and then like all of a sudden I can see and someone deleted it, later. So I know that for example my lazy flatmate decided to remove that task that we gave him to do, and you can really see who changed what, when he was changed and also obviously recover lost data, because if the event was deleted now we can find all the content that was there, and also which is super useful is finding entries based on date, so for example I met someone today, added it in the contact list, it's been two weeks, I want to send them, I have no idea, I forgot the name, I have no idea how to find it, I just go back, it's like oh, when was that weekend, yeah, though it's one of those three, I probably will recognize by that, by then, this saved me a handful of times. One more, sorry, one more thing actually and then I finish is signed pages, so as Caleb said in the talk before, one of the biggest problems with serving JavaScript is that you cannot trust the JavaScript is actually really what it is, because the server serves the JavaScript, which is the app every time, so a malicious server, for example, could just serve you a malicious piece of JavaScript that sniffs all your passwords and steals everything, and you'd be none the wiser. Like Caleb, I was looking for solutions and I decided to write a browser extension that essentially verifies the PZP signatures of pages, so it's called sign pages, Devs signs the web pages, users add the expected public key for a page, and the page, like the URL, and then the extension verifies the signatures, as you can see, this is a page with a good signature, a page with a bad signature, and obviously you have external JavaScript and CSS, so you probably want to use sub-resource integrity for all of those, and that's already a mechanism in the browser that's safe and verifies all of that, so essentially by verifying the HTML, the main entry point for your app is that you verify everything, and that's at the same level, almost the same level of security that you get with native apps in the browser, and in the future we're trying, like I'm working with Daniel, the airborne IO, which is like a Google Docs N2N Encryptor, yeah, he's there, and we're trying to do it also for service workers, so you can have it in progressive web apps, so like web apps that you just have an icon on your phone, because they're not verified, because there's no browser there to run it. Yeah, so this is it, just two finishing notes, I mean privacy is a secret right, don't give it up, and once you give it up you give it up for everyone, because then we outliers that care about it are signaled out, and don't forget, oh it's disappointing, no, you're the weakest link, so I mean this is a famous XKCD comic, like in the end doesn't matter how much encryption you use, if in the end like someone hits you with a wrench and tries to steal your password, so make sure if you have really important information, like double redundancy, so encrypted by multi keys, like essentially thanks to cryptocurrencies, there's a lot of information nowadays about advanced crypto, so this is that, and useful links, if you want website, download at the sync, yeah, and my blog, sign pages, a lot of information there, and no time for questions I assume. I have time for questions, okay, so, yes. Question? Over there. By the way, just some good, attribution, like I took a few icons from other places, it's in the slides, if you download them you can see like, and obviously the XKCD comic, so just for good measure, back to this, yeah. Thank you, so your journal appears like a single file? Okay, so the way it's actually implemented, it's implemented in a database, so just like add an entry to the database and all the servers can see is the UID and encrypted content. Okay, so, what about scalability? Did you tackle the issue? Have you thought about it? So, I don't, I haven't, I mean I've never worked on a company like Facebook or Google that deals with a million of users, I have no idea how it will behave in this level, but at the moment it's not even bothering my server, it's not, there's nothing there and it just uses normal SQL, it's just like you add entries, there's nothing there, it's like, and because I rely on existing technologies, it's not too similar from Git, it's not too dissimilar from that, it's not, it's very similar to other things, I don't see any scalability issues in the horizon, essentially. Any more questions? Yeah, over there. Since the data set is always appending, do you, do you take care of trying to make it smaller after using it for a long time? Like if you add contacts, delete contacts, etc. Like after 30 years, I mean I still want to have my contacts encrypted, so would the data set ever increase and download it on my mobile phone, maybe become higher or? Okay, so I mean it's a good concern and you know again like in Bitcoin all of that there are solutions to that, to an extent I think, like I mean you could download only chunks of it and verify those, but to be fair, it's contact information and calendar, like I challenge you to like get to a gig even, and like by the time you go to a gig, like we'll have enough storage, like it's really not a concern, like I don't see how we'll ever reach a point that it's a concern. And I have a lot of users that rewrite and change and add and still we never reached anything that's even scratching the surface, like I think the whole at the base is maybe like 200 megs and not even, actually not even, so yeah it's not a concern at this point. As a fair question to the increasing log and not garbage collecting anything, and the same time for new clients, for instance if you have a new mobile phone and you want to sync all the contacts it has to go through the entire log, right? Yes. Okay, so that could be a problem. You heard the question, I don't need to repeat the question. So essentially again like I challenge you, like right, I don't know how many friends you have, but like I don't think you'll get to more than 2,000, 4,000, 5,000 modifications, 10,000, whatever, it's still not a problem for a computer, and anyhow all of this, the data, all the size just gets to less than a meg, which is again less than an image on a normal website. So it's really not, it's not a concern, but with that being said, I have, it's not really implemented by a plan on doing like helping with general trimming. So essentially let's assume I added a contact and then I realize actually I don't want anyone to know I added this contact. So what I can do, I can help you recreate, you know, recreate a new journal, you can't change them, but create a new one that does not include this data, so you can potentially trim it if you want. I actually have one question. What if you lose your phone and you buy a new one and then you don't have, you cannot verify what's on the server, you cannot even access your data, what's the plan? Okay, so first of all luckily for me, it's because like most of the problems that usually associated with end-to-end encryption are actually solved because end-to-end here means me-to-me, so I don't need to do any secret sharing or verification of who you are identity, so I use symmetric encryption, so as long as you remember your password, it's not a problem. Like you can install it on how many phones if you remember the password, which you should, I mean write down as well, like it's, you can always recover it. That was the first part of the question, what was the first part or that was it? That was it. Okay, yeah, so that's solved and yeah, okay, question there? Well, just a quick question does it still make sense to solve host? I mean, is it secure enough to use a service like a central service for this kind of software? Yeah, so, you know, you should trust me, but like you shouldn't, so like I wouldn't do anything bad with your data but like you never know, so I mean if you think but yeah, but for example I have IP like if you don't use Tor I can have your IP, I don't have access times but I can know for example if you don't do delay addition, I can see when you added a contact so like I don't know it's a contact, maybe you change the calendar of it, but I can see when you touch your phone, when you're awake, if that makes sense. I mean there's still some stuff, but yeah, I mean my, I don't think so, I think you should use like, I don't think you should self host, I think it's too much trouble and you probably better off just using the hosted version. Yeah, question here? So I think we are thank you very much for big round of applause for your presentation and and thank you for making this Dev Room a success, there have been many people, very great presentations you will find everything online. Now it's the end, but it means also that we can stay undiscussed.


I'm Ruchira Shuklam, I lead the disruptive tech investing for IFC and this includes direct equity investing in early stage technology startups as well as investing in VC funds. I'm responsible for South Asia. We have a large portfolio across the region, largely in India. We have invested in about 16 companies in India, eight of which have grown to the unicorns and we have investments in about nine VC funds. On average, our tech business in India has returned IRRs of 30% US dollar over the last 10 years. So we look for a double bottom line, which effectively means we're looking for both impact and financial returns and that goes in with the numbers I talked about. The reason we've been able to turn 50% of the companies we backed into unicorns is because we go in relatively early, we're not seed investors. We go in past series A and we back the companies as they grow in subsequent rounds and we do a lot of work with companies to help them grow across various segments. It could be strategy, it could be operations. We help them grow both within the country as well as internationally. We make our networks available to them in order to help them solve various facets of their strategic and operational issues. We invest across sectors. The sectors of focus for us in this fiscal year, which is FY23-24, is health tech, climate tech, SaaS, as well as creator economy companies. Corporate governance is a very complex and a very, very pivotal company. My one advice to founders is no shortcuts work. And when things go wrong, there is not just a depletion of value for investors. There's huge depletion of value for the founders, for management team, for employees. And then they should remember that it's not governance for governance sake. Governance is pivotal to building a sustainable business. And if there are shortcuts in governance sooner or later, the ship will start faltering and the ship will fail. So that's a huge price paid when things go wrong. And therefore it can never hurt to be super cautious. I think they should have the tightest governance control. They should also work with their boards, with their investors in improving those checks and balances, in having that constant dialogue. The phase at which a startup grows means things will go wrong. But it needs to be flagged almost immediately to the board, to the investors, and fixes need to be put in place. So nobody will fault them for things going wrong as long as they have kept their eye on stuff and fixed it as soon as things surface. Things become, they grow out of proportion when they are ignored or when things are brushed under the carpet, when people try to hide things. That's when trust breaks and things. So never be under pressure to hide things. Please be transparent with your investors. Please be transparent with your boards.


Observational hospital stays allow physicians to evaluate and treat patients while determining the need for further intervention. These stays typically last less than 24 hours. Inpatient stays, on the other hand, may be much longer as they are often directed towards patients with more serious medical conditions. Sometimes, however, unnecessary inpatient admissions can result in short stays that could have been managed under observation status. But why does this matter? Though it may sound insignificant, this distinction comes at a price. Veterans subjected to full copayment and admitted to observation status pay approximately 4% the amount paid by those admitted with inpatient status for the same amount of time spent in the hospital. To identify patient characteristics associated with these types of hospital stays, a team of researchers analyzed nearly a decade's worth of admission records from veterans' hospitals throughout the U.S. Sifting through millions of records, they identified patients who had been diagnosed with chest pain and focused on those who were admitted to either observation stays or inpatient stays lasting less than 24 hours. Using statistical analyses and considering attributes such as age, gender, and race, the research team compared the two admission categories. The researchers found high variation between hospitals but low variation within hospitals regarding observation stay usage. While they found that female patients have a 10% greater chance of being placed in observation, the team identified very few patient characteristics associated with the different types of hospital admissions. What they did find, however, was that for veterans presenting with chest pain, the proportion of observation stays has increased in recent years. This may be the result of patient preference or due to ever diminishing space availability in VA health facilities. When it comes to billing, the categorization of patients is important as observation stays are considered an outpatient service and thus incur substantially lower costs than inpatient stays, even if the length of stays are identical. This study highlights the need to develop clinical protocols to accurately identify which patients are appropriate to simply keep for observation and which should be admitted for inpatient care.