>> Announcer: From Boston, Massachusetts, it's theCUBE! Covering Cloud Foundry Summit 2018. Brought to you by the Cloud Foundry Foundation. >> Hi I'm Stu Miniman, and this is theCUBE's coverage of Cloud Foundry Summit 2018 in Boston, Massachusetts. Happy to welcome to the program another one the keynote speakers here at the show. Johan Den Haan, who is the CTO of Mendix. A company that handles, is in the low-code space. Had a nice demo they did yesterday. Thanks for joining me. >> Yeah great, great to be here, thanks for having me. >> Johan, first of all, tell us a little bit about your background, the company. We're here in Boston, there's connections to Boston for the company? >> Definitely, our headquarters is here in Boston. So if you look at Mendix as a company, we founded the company a while back, for the sole reason to solve the problem that application development and enterprise is still very hard and error-prone. I mean, if you think about statistics around enterprise software development, most of the projects fail because it's not fast enough, not aligned to do business, things like that. So what we do as a company is help other companies thrive in a software-driven world. To make sure that they can build software from initial idea to a working application with speed. So as quickly as possible in collaboration. Because if you build something, you want to involve business people and IT people, and let them collaborate on creating the right software solution, but also in control, because we're doing it for an enterprise so you want to make sure you can control the entire process and do it in a way that helps enterprises. >> Alright, so Johan, I think back to times in my career when you talk about a softer rollout. It's like oh we're going to do this big initiative, let's bring in the consultants, we're going to spend 12 to 18 months, which turns into 24 months, and we're going to spend a ton of money and we're going to bring this application that's for the enterprise, and going to do things great. Now I talk to some companies and they're like, "Oh hey, I'm doing my ERB rollout. "I thought it was going to take me six months, "I did it in three months because I spun it up in the cloud." That's kind of the infrastructure piece, but from the application side, there's this trend with Mendix, I see low-code in there. I think some people hear it, there's low-code, there's a more controversial term no-code out there. What does this really mean, because at the end of the day, I still have my application, I have my data, what am I building, or am I just taking components? Help us understand this trend and how it fits for Mendix. >> Maybe start with the infrastructure side, as you started there. If you look at infrastructure, what we've done there is basically abstraction and automation. That way, we moved up in the stack, and then automated all the things underneath. Which is valuable, but it's only a small piece of the application life cycle. And if you think about delivering an entire application, it's more than that. And in the development part of the life cycle, you can do the same thing. You can also do abstraction and automation because if you think about applications, then a lot of the elements are the same across applications. You think about an information system, you need to have some data, UI, logic of course, and the basics, and what you can do is abstract away to a higher level, maybe a visual level. That's what Mendix does, having visual models to define your data, your logic, the business processes, as well as the UI, dragging and dropping widgets, creating user interfaces across channels, so mobile web. And then turn these models into a working application automatically. But you don't have to worry about all the technical details like if I hit this button in my UI, will it actually properly call my beckons, and trigger an action and store something in the database. These are all things that can be automated. That's what the difference is across different applications. >> How does this relate to microservices architectures? >> That's a good question, because in a lot of cases if you hear people talk about lockout, or basically came from the whole model driven development movement, then people think that using visual models you extract from detail so you have less control, so you can only build simple toy applications. But that's not where we are nowadays. This is really a next generation of using models to drive software development, where you can have complex applications with the underlying architecture, to your needs. So instead of targeting a simple client server application, we target a microservices architecture. So you can quickly build these microservices, easily re-use data across these services, but all in a visual way. So instead of having to be an architect, and building all the cloud native elements in your microservices, you can just focus on the business functionality. And if you hit the button, it will generate this cloud-native microservice for you that can scale on, as we are on cloud foundation, on Cloud Foundry, for example. >> Great, maybe it might help if you walk us through it's tough to say a typical customer, maybe give me a customer example or two, as to the problem they were having, and how this helped them move faster, I'm assuming, as part of the outcome they're looking for. >> Let's start with a small example, so just to go through all the steps of creating an application. So one of our customers is this airline company, and they had an issue with productivity. Because the main thing for them is if you maintain an airplane, to get it back in the air as soon as possible. Because if it's on the ground, it costs you money, and if it's up in the air, it can bring you money, right? So one of the mechanics in this company came up with an idea for an application that would help him be much more productive. And that's, I think also, a core element of a lockout platform, is that this collaboration that we bring with the Mendix application platform is that you can involve these people in actually being part of the application delivery team. So this mechanic teamed up with somebody who knew Mendix and said whoa, my main problem is, when I lose time, is that I don't know where my equipment is. Because they have these large areas where they maintain these planes, and you have all this specific equipment that you need for different parts of maintenance. So the very simple thing of it is that they tax the equipment with IT beat-ons, and then you build a simple app that listens to all the locations projected on the screen, so what they did was build a simple data model. So, added some entities visually, like I have my equipment, there's a location to it, and I build a UI on top of that, so drag-and-drop some widgets, or google maps widgets, to visualize the location. And then some logic that if you hit a button, you want to look up in equipment, or you want to say you're using it so that somebody else knows that, and things like that. So in just six days, they've gone through this entire process, iterating quickly. And then, they had the app, and it saves them, I think on average, half an hour per day, per mechanic. So if you have a couple hundred mechanics, that's some real money on the table, with just six days of development but the key is that it's not somebody in the head office thought about how to solve the issue of maintainability and efficiency. But it was just somebody on the floor came up with a creative idea and had the tools to quickly experiment and get it into production. >> Great, so, we're here at the Cloud Foundry Summit, can you explain how Mendix fits with Cloud Foundry and then, what other solutions do you have out there because Cloud Native's a rather big environment these days. >> So if you look back, Mendix joined the Cloud Foundry foundation as one of the early movers. And the reason for that is that, when you start to look at this application life cycle and make it (mumbles) speed, calibration, and control do that's fast, then you start with development, but that's also just one piece. So, in the early days we had a customer that was building a work flow application, so automating a certain work flow for publishing magazines. And they were struggling in dot net's for six months already and they didn't have any tangible thing yet. So we came in, we were an early startup, via relations so they were like oh, you can try it. So six weeks later, we had this entire work flow automated, and then they said, we have to take this in production, because this will save us money on a daily basis. And then, okay, go talk with IT and they said well, Mendix we don't know what it is, and by the way, how do we learn this and we need to order hardware. That was the moment that we realized, it's not just about development it's about the delivery of the entire application. So it was called Cloud then, back in 2007 when we had this. We started to host application, made that do the same thing there so one click deployments to solve that issue as well, because you have the same thing that you need expertise to run applications. But instead of that we abstract away from the details and we just run it in the Cloud. And then in 2014, Cloud Foundry came up and we realized we should replace our home-grown past layer that we created with an open-source foundation so that we are completely portable because we want to offer our customers the freedom to deploy anywhere, whether it's on their private cloud running on one of the distributions of Cloud Foundry, on the IBM cloud, the SAP cloud. But I think it's a really happy marriage between Mendix, which is completely complimentary to Cloud Foundry. But both with the same philosophy about automating things, abstracting away from the details, and making it much more productive to develop application one handed but also to deploy and operate them. >> It sounds like a good fit for Cloud Foundry to handle certain things lower-level in the stack, while you're handling the upper-level in the stack. Is it only Cloud Foundry is Mendix supported on other Cloud solutions, or beyond Cloud Foundry? >> Our strategy is to be completely agnostic to underlying infrastructure, so we also run on any dock or base system. So Cubernitas, but also ECS from Amazon, for example. So yeah, whatever we can run a dock content on you can run Mendix and we can scale out because of our Cloud Native architecture. >> Who's the typical person that your company is working with? Is it the developer side that carries the business? Because developers often times do things but don't have the budget for them, and you mentioned some of the developer-operator challenges so I'm curious that Mendix is dynamic with companies. >> That's a great question, because if you look at the developer landscape, it's kind of widening. Because you don't have just the professional developer, that is able to build so far, but with low-card you have more business-oriented people that can join these teams as well. So if you look at the typical team that's building applications using the Mendix platform, I would call them Best Staff Ops teams. You have death ops joining operation development, but this is also joining the business into this same cross-functional team. So a typical team building software using Mendix is like if you have five people on a team, you often have one professional developer, but four people with a business background. They are tech savvy, they maybe have a background as a BI consultant or an SLP consultant or these kind of roles, but they don't have a computer science background, but they are involved in building the software. And a great advantage of course is that they are domain experts in the area they are building the software for. So you can be really enabling the business and being of value to the business. >> Last question, the company itself, how many employees, how many customers, just give us kind of a thumbnail of the company. >> So we have around a thousand enterprise customers. Company size is currently north of 350 people, growing fast. It's crazy hiring all the people that we need to, because the market is really hot. If you look at low-cord, I think it's really the next generation of application development becoming a main-stream option that any enterprise needs to have to deliver the applications they need. And slightly tied to your previous question, it's also solving the talent gap. You've seen all these rallying cries around, everybody needs to learn to code to solve the problem that we need more software than we can build. I don't think that is the solution. We will never have so many people that can develop software. We need a paradigm shift. And that paradigm shift will enable us to build software faster, 10 times faster than you're used to with traditional programming languages, but also with a much broader group of people. More business-oriented people, so a group of people that can use a low-code platform is minimally 10 times bigger than the professional developer group. And that's what we need to solve this problem in the software-driven world that we live in. >> Johan Den Haan, CTO of Mendix, thanks so much for joining me. I'm Stu Miniman, this is theCUBE Cloud Foundry Summit 2018. (upbeat music)

>>welcome back everyone to the cube con cloud, David Kahn coverage. I'm john for a host of the cube, we're here in person, 2020 20 a real event, it's a hybrid event, we're streaming live to you with all the great coverage and guests coming on next three days. Clayton Coleman's chief Hybrid cloud architect for Red Hat is joining me here to go over viewers talk but also talk about hybrid cloud. Multi cloud where it's all going road red hats doing great to see you thanks coming on. It's a pleasure to be >>back. It's a pleasure to be back in cuba con. >>Uh it's an honor to have you on as a chief architect at Red Hat on hybrid cloud. It is the hottest area in the market right now. The biggest story we were back in person. That's the biggest story here. The second biggest story, that's the most important story is hybrid cloud. And what does it mean for multi cloud, this is a key trend. You just gave a talk here. What's your take on it? You >>know, I, I like to summarize hybrid cloud as the answer to. It's really the summarization of yes please more of everything, which is, we don't have one of anything. Nobody has got any kind of real footprint is single cloud. They're not single framework, they're not single language, they're not single application server, they're not single container platform, they're not single VM technology. And so, um, and then, you know, looking around here in this, uh, partner space where eight years into kubernetes and there is an enormous ecosystem of tools, technologies, capabilities, add ons, plug ins components that make our applications better. Um the modern application landscape is so huge that I think that's what hybrid really is is it's we've got all these places to run stuff more than ever and we've got all this stuff to run more than ever and it doesn't slow down. So how do we bring sanity to that? How do we understand it? Bring it together and companies has been a big part of that, like it unlocked some of that. What's the next step? >>Yeah, that's a great, great commentary. I want to take into the kubernetes piece but you know, as we've been reporting the digital transformation at all time, high speed is the number one request. People want to go faster, not just speeds and feeds, but like ship code fast to build apps faster. Make it all run faster and secure. Okay, check, get that. Look what we were 15, 15 years ago, 10 years ago, five years ago, 2016. The first coupe con in Seattle we were there for small events kubernetes, we gotta sell it, figure it out. Right convince people >>that it's a it's worth >>it. Yeah. So what's your take on that? Well, I mean, it's mature, it's kind of de facto standard at this point. What's missing. Where is it? >>So I think Kubernetes has succeeded at the core mission which is helping us stop worrying about all the problems that we spent endless amounts of time arguing about, how do I deploy software, How do I roll it out? But in the meantime we've added more types of software. You know, the rise of ai ml um you know, the whole the whole ecosystem around training software models like what is a what is an Ai model? Is it look like an application, does it look like a job? It's part batch, part service. Um It's spread out to the edge. We've added mobile devices. The explosion in mobile computing over the last 10 years has co evolved. And so kubernetes succeeded at that kind of set a floor for what everybody thought was an application. And in the meantime we've added all these other parts of the application. >>It's funny, you know, David Anthony, we're talking about what's to minimum and networks at red hat will be on later. Back in the first two cubicles were like, you know, this is like a TCP I P moment, the Os I model that was a killer part of the stack. Now it was all standardized below TCP I. P. Company feels like a similar kind of construct where it's unifying, is creating some enablement, It's enabling some innovation and it kind of brought everyone together at the same time everyone realized that that's real, >>the whole >>cloud native is real. And now we're in an era now where people are talking about doing things that are completely different. You mentioned as a batch job house ai new software paradigm development paradigms, not to suffer during the lifecycle, but just like software development in general is impacted. >>Absolutely. And you know, the components like, you know, we spent a lot of time talking about how to test and build application, but those are things that we all kind of internalized now we we have seen the processes is critical because it's going to be in lots of places, people are looking to standardize. But sometimes the new technology comes up alongside the side, the thing we're trying to standardize, we're like, well let's just use the new technology instead function as a service is kind of uh it came up, you know, kubernetes group K Native. And then you see, you know, the proliferation of functions as a service choices, what do people use? So there's a lot of choice and we're all building on those common layers, but everybody kind of has their own opinions, everybody's doing something subtly different. >>Let me ask you your opinion on on more under the Hood kind of complexity challenge. There's general consensus in the industry that does a lot of complexity. Okay, you don't mean debate that, but that's in a way, a good thing in the sense if you solve that, that's where innovation comes in. So the goal is to solve complexity, abstract out of the heavy lifting under heavy living in Sandy Jackson. And I would say, or abstract away complexity make things easier to use >>Well and an open source and this ecosystem is an amazing um it's one of the most effective methods we've ever found for trying every possible solution and keeping the five or six most successful and that's a little bit like developers, developers flow downhill, developers are going to do, it's easy if it's easier to put a credit card in and go to the public cloud, you're gonna do it if you can take control away from the teams at your organization that are there to protect you, but maybe aren't as responsive as you like. People will, people will go around those. And so I think a little bit of what we're trying to do is what are the commonalities that we could pick out of this ecosystem that everybody agrees on and make those the downhill path that people follow, not putting a credit card into a cloud, but offering a way for you not to think about what clouds are on until you need to write, because you want to go to the fridge is a developer, you wanna go the fridge, pull out your favorite brand of soda, that favorite band Isoda might have an AWS label also >>talk about the open shift and the Kubernetes relationship, you guys push the boundaries. Um Den is being controlled playing and nodes, these are things that you talked about in your talk, talk about because you guys made some good bets on open shift, we've been covering that, how's that playing out now? It's a relationship now >>is interesting coming into kubernetes, we came in from the platform as a service angle, right, Platform as a service was the first iteration of trying to make the lowest cost path for developers to flow to business value um and so we added things on top of kubernetes, we knew that we were going to complex, so we built in a little bit um in our structure and our way of thinking about cube that it was never going to be just that basic bare bones package that you're gonna have to make choices for people that made sense. Ah obviously as the ecosystems grown, we've tried to grow with it, we've tried to be a layer above kubernetes, we've tried to be a layer in between kubernetes, we've tried to be a layer underneath kubernetes and all of these are valid places to be. Um I think that next step is we're all kind of asking, you know, we've got all this stuff, are there any ways that we can be more efficient? So I like to think about practical benefits, what is a practical benefit That a little bit of opinion nation could bring to this ecosystem and I think it's around applications, it's being application centric, it's what is a team, 90% of the time need to be successful, they need a way to get their code out, they need to get it to the places that they wanted to be, and that place is everywhere. It's not one cloud or on premises or a data center, it's the edge, it's running as a lambda. It's running inside devices that might be being designed in this very room today. >>It's interesting. You know, you're an architect, but also the computer science industry is the people who were trained in the area are learning. It's pretty fascinating and almost intoxicating right now in this this market because you have an operating system, dynamic systems kind of programming model with distributed cloud, edge on fire, that's only gonna get more complicated with 5G and high density data applications. Um and then you've got this changing modal mode of operations were programming with bots and Ai and machine learning to new things, but it's kind of the same distributed computing paradigm. Yeah. What's your reaction to that? >>Well, and it's it's interesting. I was kind of described like layers. We've gone from Lenox replaced proprietary UNIX or mainframe to virtualization, which, and then we had a lot of Lennox, we had some windows too. And then we moved to public cloud and private cloud. We brought config management and moved to kubernetes, um we still got that. Os at the heart of what we do. We've got, uh application libraries and we've shared services and common services. I think it's interesting like to learn from Lennox's lesson, which is we want to build an open expansive ecosystem, You're kind of like kind of like what's going on. We want to pick enough opinion nation that it just works because I think just works is what, let's be honest, like we could come up with all the great theories of what the right way computers should be done, but it's gonna be what's easy, what gets people help them get their jobs done, trying to time to take that from where people are today on cube in cloud, on multiple clouds, give them just a little bit more consolidation. And I think it's a trick people or convince people by showing them how much easier it could be. >>You know, what's interesting around um, what you guys have done a red hat is that you guys have real customers are demanding, you have enterprise customers. So you have your eye on the front edge of the, of the bleeding edge, making things easier. And I think that's good enough is a good angle, but let's, let's face it, people are just lifting and shifting to the cloud now. They haven't yet re factored and re factoring is a concept of taking what you're doing in the cloud of taking advantage of new services to change the operating dynamic and value proposition of say the application. So the smart money is all going there, seeing the funding come into applications that are leveraging the new platform? Re platform and then re factoring what's your take on that because you got the edge, you have other things happening. >>There are so many more types of applications today. And it's interesting because almost all of them start with real practical problems that enterprises or growing tech companies or companies that aren't tech companies but have a very strong tech component. Right? That's the biggest transformation the last 15 years is that you can be a tech company without ever calling yourself a tech company because you have a website and you have an upset and your entire business model flows like that. So there is, I think pragmatically people are, they're okay with their footprint where it is. They're looking to consolidate their very interested in taking advantage of the scale that modern cloud offers them and they're trying to figure out how to bring all the advantages that they have in these modern technologies to these new footprints and these new form factors that they're trying to fit into, whether that's an application running on the edge next to their load bouncer in a gateway, in telco five Gs happening right now. Red hat's been really heavily involved in a telco ecosystem and it's kubernetes through and through its building on those kinds of principles. What are the concepts that help make a hybrid application, an application that spans the data flowing from a device back to the cloud, out to a Gateway processed by a big data system in a private region, someplace where computers cheap can't >>be asylum? No, absolutely not has to be distributed non siloed based >>and how do we do that and keep security? How do we help you track where your data is and who's talking to whom? Um there's a lot of, there's a lot of people here today who are helping people connect. I think that next step that contact connectivity, the knowing who's talking and how they're connecting, that'll be a fundamental part of what emerges as >>that's why I think the observe ability to me is the data is really about a data funding a new data sector of the market that's going to be addressable. I think data address ability is critical. Clayton really appreciate you coming on. And giving a perspective an expert in the field. I gotta ask you, you know, I gotta say from a personal standpoint how open source has truly been a real enabler. You look at how fast new things could come in and be adopted and vetted and things get kicked around people try stuff that fails, but it's they they build on each other. Right? So a I for example, it's just a great example of look at what machine learning and AI is going on, how fast that's been adopted. Absolutely. I don't think that would be done in open source. I have to ask you guys at red hat as you continue your mission and with IBM with that partnership, how do you see people participating with you guys? You're here, you're part of the ecosystem, big player, how you guys continue to work with the community? Take a minute to share what you're working on. >>So uh first off, it's impossible to get anything done I think in this ecosystem without being open first. Um and that's something the red at and IBM are both committed to. A lot of what I try to do is I try to map from the very complex problems that people bring to us because every problem in applications is complex at some later and you've got to have the expertise but there's so much expertise. So you got to be able to blend the experts in a particular technology, the experts in a particular problem domain like the folks who consult or contract or helped design some of these architectures or have that experience at large companies and then move on to advise others and how to proceed. And then you have to be able to take those lessons put them in technology and the technology has to go back and take that feedback. I would say my primary goal is to come to these sorts of events and to share what everyone is facing because if we as a group aren't all working at some level, there won't be the ability of those organizations to react because none of us know the whole stack, none of us know the whole set of details >>And this text changing too. I mean you got to get a reference to a side while it's more than 80s metaphor. But you know, but that changed the game on proprietary and that was like >>getting it allows us to think and to separate. You know, you want to have nice thin layers that the world on top doesn't worry about below except when you need to and below program you can make things more efficient and public cloud, open source kubernetes and the proliferation of applications on top That's happening today. I >>mean Palmer gets used to talk about the hardened top when he was the VM ware Ceo Back in 2010. Remember him saying that he says she predicted >>the whole, we >>call it the mainframe in the cloud at the time because it was a funny thing to say, but it was really a computer. I mean essentially distributed nature of the cloud. It happened. Absolutely. Clayton, thanks for coming on the Cuban sharing your insights appreciate. It was a pleasure. Thank you. Right click here on the Cuban john furry. You're here live in L A for coupon cloud native in person. It's a hybrid event was streaming Also going to the cube platform as well. Check us out there all the interviews. Three days of coverage, we'll be right back Yeah. Mm mm mm I have

>>from >>around the >>globe. It's the Cube with digital coverage of pager duty. Summit 2020. Brought to you by pager duty. Hey, welcome back to Brady. Jeffrey here with the Cube in Palo Alto studios today. And we're talking about an upcoming event. It's one of our favorites. This will be the fourth year that we've been doing it. And it's pager duty summit. And we're excited to have from the pager duty team. She's Caroline Gus, the VP of corporate marketing from pager duty. Caroline, Great to see you. >>Hi, Jeff. Great to see you again. >>Absolutely. So, you know, I was thinking before we turn on the cameras we've been doing pager duty for I think this will be like, say, our fourth year that first year was in the cool, um, cruise ship terminal pier. I gotta written appear 27 which was which was nice. And then the last two years, you've been in the, you know, historic Westin ST Francis in downtown San Francisco, which is a cool old venue, but oh, my goodness. You guys were busting at the seams last year. So this year, year to go virtual. There's a whole bunch of new things that that you could do in virtual that you couldn't do in physical space. At least when you're busting out of the seems so First off, Welcome and >>talk a little >>bit about planning for virtual versus planning for a physical event from, you know, head of marketing perspective. >>Absolutely. I mean, the first thing that's changed for us is the number of people that can come. It's five x the number of people that were able to join us, the Western last year. So we have, uh, we we expect to have 10,000 people registered on attending age duty summit. The second thing is thea share number of sessions that we can put on. Last year, I think we had around 25 sessions. This year we have between 40 and 50 on again. That's because we're not constrained by space and physical meeting rooms, so it's being a really exciting process for us. We've built a fantastic agenda on. It's very much personalized, you know, developers come to our event. They love our event for the opportunity to learn mixed with their peers, get best practices and hands on experience. So we have many more of those types of sessions when we have done previously, and that things like labs and Bird of Feather Sessions and Emma's. But we've also built a whole new track of content this year for executives. Page Julie has, um, many of the Fortune 500 on 4100 customers. We work very closely with CEO CTO, so we have built sessions that are really designed specifically for that audience on I think for us it's really opened up. The potential of this event made it so much broader and more appealing than we were able to do when we were, As you say, you know, somewhat confined by the location in downtown San Francisco. >>I think it's such an interesting point. Um, because before you were constrained, right, If you have X number of rooms over a couple of days, you know you've got to make hard decisions on breakouts and what could go in and what can't go in. And, you know, will there be enough demand for these for this session versus another session? Or from the perspective of an attendee, you know, do they have to make hard tradeoffs? I could only attend one session at one oclock on Tuesday and I got to make hard decisions. But this is, you said really opens up the opportunities. I think you said you doubled. You doubled your sessions on and you got five X a number of registrations. So I think, you know, way too many people think about what doesn't happen in digital vs talking about the things that you can do that are impossible in physical. >>Yeah, I think at the very beginning. Well, first of all, we held our Amir summit events in London in July. So that was great because we got Thio go through this experience once already. And what we learned was the rial removal of hurdles in this process. So, to your point about missing the session because you're attending another session, we were calling this sort of the Pelton version of events where you have live sessions. It's great to be there, live participate in the live Q and A, but equally you have an entire on demand library. So if you weren't able to go because there was something else at the same time, this is available on demand for you. So we are actually repeating live sessions on two consecutive day. So on the Monday we're on everything on the Tuesday I ask because show up again for life Q and A at the end of their sessions. But after that it's available forever on an on demand library. So for us, it was really removing hurdles in terms of the amount of content, the scheduling of the content on also the number of people that content in attend, no geographical boundaries anymore. It used to be that a customer of ours would think, Well, I'll send one or two people to the page duty summit. They could learn all the great innovation from page duty, and they'll bring it back to the team that's completely changed. You know, we have tens of 20 signing up on. All of them are able to get that experience firsthand. >>That's really interesting. I didn't didn't even think about, you know, kind of whole teams being able to attend down instead of just certain individuals because of budget constraints, or you can't send your whole team, you know, a way for a conference in a particular area. But the piece to that you're supporting that were over and over is that the net new registrants goes up so dramatically in terms of the names and and and who those individuals are because a lot of people just couldn't attend for for various reasons, whether it's cost, whether it's, uh, geography, whether it's they just can't take time off from from from leaving their primary job. So it's a really interesting opportunity to open up, um, the participation to such a much bigger like you said five x five X, and increase in the registration. That's pretty good number. >>That's right. Yeah. I mean, that crossed boundaries gone away. This event is free on DWhite. That's actually meant is, as I say, you know, larger teams from the same company are attending. Uh, In addition, we have a number of attendees who are not actually paid to duty customers right now to previously. This was very much a community event for, you know, our page duty users on now we actually have a large number of I asked, interested future customers that will be coming to the event. So that's really important for us. And also, I think, for our sponsor partners as well, because it's bordering out the audience for both of us. So let's >>talk about sponsors for a minute, because, um, one of the big things in virtual events that people are talking about quite often is. Okay, I can do the keynotes, and I could do the sessions. And now I have all these breakout sessions for, um, you know, training and certification and customer stories, etcetera. But when it comes to sponsors, right sponsors used, you know, go to events to set up a booth and hand out swag and wander badge. Right? And it really was feeding kind of a top level down funnel. That was really important. Well, now those have gone away. Physical events. So from the sponsor perspective, you know, what can they expect? What? What do you know the sponsor experience at pager duty Summit. Since I don't have a little tiny booth at the Westin ST Francis given out swag this year. >>Yeah. So one important thing is the agenda and how we're involving our sponsors in our agenda this time, something that we learned is we used to have very long keynotes. You know, the keynote could be an hour long on involved multiple components and people would stay in that room for a now er on did really stay and watch sessions all day. So we learned in the virtual format that we need to be shorter and more precise in our sessions on that opened up the opportunity to bring in more of our partners, our sponsorship partners. So zendesk Salesforce, Microsoft some examples. So they actually get to have their piece of both of our keynote sessions and of our technical product sessions. I'm really explain both the partnership with pager duty, but also they're called technology and the value that they provide customers. So I think that the presence of sponsors in content is much higher than it was before on we are still repeating the Expo format, so we actually do have on Expo Hall that any time there's breaking between sessions, you could go over to the Expo ball, and it actually runs throughout as well, and you can go in and you can talk to the teams. You can see product demos, so it's very much a virtual version of the Expo Hall where you went and you want around and you picked up a bit of swag, >>so you mentioned keynotes and and Jennifer and and the team has always had a fantastic keynotes. I mean, I just saw Jennifer being interviewed with Frank's Luqman and and Eric Juan from Zoom By by Curry, which was pretty amazing. I felt kind of jealous that I didn't get to do that. But, um, talk tell us a little bit about some of the speakers I know there'll be some some, you know, kind of big rally moment speakers as well as some that are more down to technical track or another track. Give us some highlights on on some of the people. I will be sharing the stage with Jennifer. >>Absolutely, I said. I think what's really unique about Page duty Summit is that we designed types of content for different types of attendees. So if you're a developer, your practitioner, we have something like this from Jones of Honeycombs, who's talking about who builds the tools that we all rely on today, and how do they collaborate to build them together in this virtual world? Or we have J. Paul Reed from Netflix talking about how to handle the stress of being involved in incidents, So that's really sessions for our core audience of developers who are part of our community and pager duty really helps them day to day with with that job. And then we have the more aspirational senior level speakers who could really learn from a ZA leader. So Bret Taylor, president and CEO of Salesforce, will be joining us on the main stage. You'll be talking about innovation and trust in today's world on. Then we have Derrick Johnson. He is president of N A A. C P, and he'll be talking about community engagement and particularly voter engagement, which is such an important topic for us right now. Aan den. We have leaders from within our customers who are really talking about the way they use pager duty thio drive change in their organization. So an example would be porches, bro. He runs digital for Fox on, and he's gonna be talking about digital acceleration. How large organization like Fox can really accelerate for this digital first world that we find ourselves living in right now, >>right? Well, you guys have such a developer focus because pager duty, the product of solution, has to integrate with so many other, um, infrastructure, you know, monitoring and, uh, and all of all those different systems because you guys were basically at the front line, you know, sending them the signals that go into those systems. So you have such a broad, you know, kind of ecosystem of technology partners. I don't know if people are familiar with all the integrations that you guys have built over the years, which is such a key piece of your go to market. >>That's right. I mean, we we like to say we're at the center of the digital ecosystem. We have 203 170 integrations on. That's important because we want anyone to be able to use page duty no matter what is in their technology stack technology stacks today are more complex than they've ever been before, particularly with businesses having to shift to this digital first model since we all began shelter in place, you know, we all are living through digital on working and learning through digital on DSO. The technology stacks that power that are more complicated than ever before. So by having 370 integrations, we really know that we conserve pretty much any set of services that your business. It's using. >>Yeah, we've all seen all the means right about who's who's pushing your digital transformation. You know, the CEO, the CEO or or covert. And we all know the answer to toe what's accelerated that whole process. So okay, but so before I let you go, I don't even think we've mentioned the date. So it's coming up Monday, September, September 21st through Thursday, September 24th not at the West End Online and again. What air? What are you hoping? You're kind of the key takeaways for the attendees after they come to the summit? >>Yeah, a couple of things. I mean, first of all, I think will be a sense of belonging. Three attendees, the uses, a pager duty. They are really the teams that are at the forefront of keeping our digital services working on. But what that means is responding to incidents we've actually seen. Ah, 38% increase in the volume of incidents on our platform since covert and shelter in place began. Wait 30 >>38% increase in incidents since mid March. >>That's correct. Since the beginning of on bear in mind incidents. Prior to that in the six months prior, they were pretty flat. There wasn't instant growth. But what we've also seen is a 20% improvement in the time that it takes to resolve an incident from five minutes down to four minutes. So what that really means is that the pager duty community is working really hard. They're improving their practices. Hopefully our platform, our platform is a key part of how, but these are some people under pressure, so I hope that people can come and they can experience a sense of belonging. They can learn from each other about experiences. How do you manage the stress of that situation on what are some of the great innovations that make your job easier in the year ahead? The second thing that we don't for that community is that we are offering certification for P. D. You page due to university for free this year. It's of course, with a value of $7500. Last year, you would attend page duty summit on you would sit through your sessions and you would learn and you would get certified. So this year it's offered for free. You take the course during summit. But you can also carry on if you miss anything for 30 days after. So we're really feeling that, you know, we're giving back there, offering a great program for certification and improved skills completely free to help our community in this in this time of pressure, >>right? Right. Well, it is a very passionate community, and, you know, we go to so many events and you can you can really tell it's palatable, you know, kind of what the where the tight communities are and where people are excited to see each other and where they help each other, not necessarily only at the event, but you know, throughout the year. And I think you know a huge shout out to Jennifer on the culture that she's built there because it is very warm. It's very inclusive, is very positive. And and that energy, you know, kind of goes throughout the whole company and ice the teaser. You know this in something that's built around a device that most of the kids today don't even know what a pager is, and just the whole concept of carrying a pager and being on call right and being responsible. It's a very different way to kind of look at the world when you're the one that has that thing on your hip and it's buzzing and someone's expecting, Ah, return call and you gotta fix something So you know, a huge shout out to keep a positive and you're smiling nice and big culture in a job where you're basically fixing broken things most of the time. >>Yeah, absolutely. I mean, there's, I think, a joke that we make you know these things only break on Friday night or your wedding anniversary or Thanksgiving. But one of the announcements we're most excited about this year is the level of automation on artificial intelligence that we're building into our platform that is really going to reduce the number of interruptions that developers get when they are uncle. >>Yeah, I look forward to more conversations because we're gonna be doing a bunch of Cube interviews like Normal and, uh, you know, applied artificial intelligence, I think, is where all the excitement is. It's not a generic thing. It's where you applied in a specific application to get great business outcomes. So I look forward to that conversation and hopefully we'll be able to talk again and good luck to you and the team in the last few weeks of preparation. >>Thanks so much, Jeff. I've enjoyed talking to you. Thanks for having me. >>Alright. You too. And we'll see you later. Alright. She is Caroline. I'm Jeff. You're watching the Cube. Thanks for watching. We'll see you next time.