1 00:00:00,000 --> 00:00:06,000 Welcome to the Deep Dive. Today we are cutting straight through the complexities of 2 00:00:06,000 --> 00:00:06,720 modern 3 00:00:06,720 --> 00:00:10,230 software infrastructure. And we're tackling a big one. A really big one. We're 4 00:00:10,230 --> 00:00:10,720 talking about 5 00:00:10,720 --> 00:00:15,680 one of the biggest silent time sinks for development teams, managing notifications. 6 00:00:15,680 --> 00:00:17,360 We're diving deep 7 00:00:17,360 --> 00:00:23,920 into Novu, which bills itself as the open source notification inbox infrastructure. 8 00:00:23,920 --> 00:00:24,480 Right. And if 9 00:00:24,480 --> 00:00:29,920 you've ever had to integrate, say, an email provider, an SMS gateway, and an in-app 10 00:00:29,920 --> 00:00:30,480 system 11 00:00:30,480 --> 00:00:34,800 all at once. You know the pain. You know exactly why this is such a critical topic. 12 00:00:34,800 --> 00:00:35,520 Exactly. But 13 00:00:35,520 --> 00:00:38,530 before we jump right in, I just want to say a huge thank you to the supporter of 14 00:00:38,530 --> 00:00:39,520 this Deep Dive, 15 00:00:39,520 --> 00:00:44,160 Safe Server. Yes, absolutely. Safe Server handles the reliable hosting of, well, 16 00:00:44,160 --> 00:00:45,120 percent low is type 17 00:00:45,120 --> 00:00:48,960 of software. Cutting edge, scalable stuff. And they support companies in their 18 00:00:48,960 --> 00:00:49,920 journey of digital 19 00:00:49,920 --> 00:00:54,020 transformation. They really do. They provide that robust backbone that you need for 20 00:00:54,020 --> 00:00:54,800 platforms built 21 00:00:54,800 --> 00:01:03,520 to scale. For more information you can visit www.safeserver.de. That's www.safeserver.de. 22 00:01:03,520 --> 00:01:08,560 Okay, so our mission today is pretty straightforward. We need to unpack how modern 23 00:01:08,560 --> 00:01:09,360 apps can deliver 24 00:01:09,360 --> 00:01:14,380 seamless notifications. Across everything. Email, SMS, push, chat. Without 25 00:01:14,380 --> 00:01:15,520 developers having to 26 00:01:15,520 --> 00:01:20,330 manage, you know, dozens of complex brittle integrations. We want to make this tech 27 00:01:20,330 --> 00:01:21,040 accessible 28 00:01:21,040 --> 00:01:26,480 and show you why centralizing this is a strategic move now, not just a convenience. 29 00:01:26,480 --> 00:01:27,280 And the core 30 00:01:27,280 --> 00:01:32,170 concept is, I think, simple but incredibly powerful. Novu is the platform that 31 00:01:32,170 --> 00:01:32,880 basically 32 00:01:32,880 --> 00:01:37,700 turns complex multi-channel delivery into a single component. A single component. 33 00:01:37,700 --> 00:01:37,920 Think of 34 00:01:37,920 --> 00:01:42,400 the time saved there. All that context switching a developer avoids just by talking 35 00:01:42,400 --> 00:01:43,360 to one unified 36 00:01:43,360 --> 00:01:49,310 system. It's huge. Okay, let's unpack this then. What is the fundamental day-to-day 37 00:01:49,310 --> 00:01:49,920 headache that 38 00:01:49,920 --> 00:01:53,120 Novu is trying to solve for developers? It can't just be about sending an email, 39 00:01:53,120 --> 00:01:53,760 right? That part's 40 00:01:53,760 --> 00:01:57,900 easy. The pain must be in the orchestration. It is, exactly. The initial send is 41 00:01:57,900 --> 00:01:58,960 always easy. 42 00:01:58,960 --> 00:02:03,350 The real difficulty comes from having to integrate and maintain, what, maybe four 43 00:02:03,350 --> 00:02:03,840 different vendors 44 00:02:03,840 --> 00:02:09,260 for delivery? Like who? Give me an example. Okay, so SendGrid for email, Twilio for 45 00:02:09,260 --> 00:02:09,760 SMS, 46 00:02:09,760 --> 00:02:15,040 maybe FCM for Android Push, and then the Slack API for your internal team alerts. 47 00:02:15,040 --> 00:02:16,080 Right. Four 48 00:02:16,080 --> 00:02:20,140 different systems. That's four different APIs, four sets of error codes, four 49 00:02:20,140 --> 00:02:21,680 authentication methods, 50 00:02:21,680 --> 00:02:26,620 and probably four distinct templating languages. All just to tell a user the same 51 00:02:26,620 --> 00:02:27,440 thing. Your 52 00:02:27,440 --> 00:02:32,160 payment process. That sounds incredibly inefficient. It is. So Novu abstracts all 53 00:02:32,160 --> 00:02:32,720 of that away. It 54 00:02:32,720 --> 00:02:36,810 provides this unified API that acts like a single control tower for everything. So 55 00:02:36,810 --> 00:02:37,440 your application 56 00:02:37,440 --> 00:02:41,760 just sends one message to Novu. And Novu handles all the complex routing logic. It 57 00:02:41,760 --> 00:02:42,320 looks at user 58 00:02:42,320 --> 00:02:47,940 preferences, channel availability, workflow rules, all of it. It really does sound 59 00:02:47,940 --> 00:02:48,960 like the system 60 00:02:48,960 --> 00:02:53,020 that stops an app from drowning in its own logistics. I mean, if a developer is 61 00:02:53,020 --> 00:02:53,520 spending, 62 00:02:53,520 --> 00:02:59,200 say, 20% of their time just maintaining this mess of notification logic, what does 63 00:02:59,200 --> 00:02:59,840 freeing up that 64 00:02:59,840 --> 00:03:04,970 time actually let the product team build instead? What's the real strategic benefit? 65 00:03:04,970 --> 00:03:05,360 It lets them 66 00:03:05,360 --> 00:03:09,540 focus on core product features, the things that actually drive revenue or user 67 00:03:09,540 --> 00:03:10,480 engagement instead 68 00:03:10,480 --> 00:03:14,040 of just maintaining plumbing. Right. Notification code is boilerplate. It doesn't 69 00:03:14,040 --> 00:03:14,800 really differentiate 70 00:03:14,800 --> 00:03:18,640 your product. Not at all. Yeah. And by offloading that maintenance debt, your 71 00:03:18,640 --> 00:03:19,600 development velocity 72 00:03:19,600 --> 00:03:25,280 just increases dramatically. Plus, because Novu is open source, the community validations 73 00:03:25,280 --> 00:03:25,440 is, 74 00:03:25,440 --> 00:03:30,080 it's just off the charts. It proves this is a universally shared pain. And the 75 00:03:30,080 --> 00:03:30,640 numbers back 76 00:03:30,640 --> 00:03:37,450 that up, right? Oh, yeah. The momentum is huge. It boasts 38.1 thousand GitHub 77 00:03:37,450 --> 00:03:38,960 stars over 4.2 78 00:03:38,960 --> 00:03:44,400 thousand forks and a contributor base of over 440 people. Wow. That kind of 79 00:03:44,400 --> 00:03:45,440 participation 80 00:03:45,440 --> 00:03:49,600 is a clear signal. It shows their whole approach, built for developers, designed 81 00:03:49,600 --> 00:03:50,240 for growth, 82 00:03:50,240 --> 00:03:55,030 powered by open source, is solving a really crucial industry problem. Okay. So this 83 00:03:55,030 --> 00:03:55,360 moves 84 00:03:55,360 --> 00:03:59,360 the conversation beyond just the backend infrastructure and into the actual user 85 00:03:59,360 --> 00:04:04,320 experience because the most visible primary deliverable here seems to be this embeddable 86 00:04:04,320 --> 00:04:08,720 inbox component. For a lot of listeners, this component is the solution because it's 87 00:04:08,720 --> 00:04:08,880 what 88 00:04:08,880 --> 00:04:13,520 the user sees. It absolutely is. So what does this pre-built component actually 89 00:04:13,520 --> 00:04:14,880 give a product team? 90 00:04:14,880 --> 00:04:19,520 It gives them a ready-made real-time notification center that sits right inside 91 00:04:19,520 --> 00:04:20,560 their web app. 92 00:04:20,560 --> 00:04:25,120 You know, think about the notification bell on GitHub or Slack. Sure. Building that 93 00:04:25,120 --> 00:04:25,360 from 94 00:04:25,360 --> 00:04:31,300 scratch. I mean, handling real-time updates, read-unread states, pagination, user 95 00:04:31,300 --> 00:04:32,320 controls. 96 00:04:32,320 --> 00:04:37,580 It's a huge undertaking. A project in itself. It is. The Novu Inbox component just 97 00:04:37,580 --> 00:04:38,160 eliminates 98 00:04:38,160 --> 00:04:42,640 all of that foundational work. Yeah. It's a ready-to-use UI component that needs 99 00:04:42,640 --> 00:04:43,120 minimal 100 00:04:43,120 --> 00:04:47,180 integration. And the sources highlight just how simple it is. They claim it can be 101 00:04:47,180 --> 00:04:47,840 implemented 102 00:04:47,840 --> 00:04:53,200 with just, what was it? Six lines of code. Six lines. That's almost shocking when 103 00:04:53,200 --> 00:04:53,680 you consider 104 00:04:53,680 --> 00:04:58,000 the complexity it's replacing. It really speaks to the maturity of their SDKs. I 105 00:04:58,000 --> 00:04:59,200 mean, they show an 106 00:04:59,200 --> 00:05:03,110 example using their AdNova Next.js package that simplifies it down to just 107 00:05:03,110 --> 00:05:04,400 importing the component 108 00:05:04,400 --> 00:05:07,750 and giving it a user ID. And what about framework support? They've got full support 109 00:05:07,750 --> 00:05:08,080 for the big 110 00:05:08,080 --> 00:05:12,210 ones, like React and Next.js, and they're actively working on React Native View and 111 00:05:12,210 --> 00:05:13,040 Angular. So, 112 00:05:13,040 --> 00:05:17,360 they're clearly targeting the entire modern front-end landscape. They describe this 113 00:05:17,360 --> 00:05:18,480 component as 114 00:05:18,480 --> 00:05:24,430 batteries included, which I love. It implies it handles all those tedious features 115 00:05:24,430 --> 00:05:24,880 developers 116 00:05:24,880 --> 00:05:29,840 hate building. It does. So, what are the key functionalities that are just baked in 117 00:05:29,840 --> 00:05:30,080 right 118 00:05:30,080 --> 00:05:34,070 out of the box? There are three killer features here that save an immense amount of 119 00:05:34,070 --> 00:05:34,800 engineering 120 00:05:34,800 --> 00:05:40,320 time. First is real-time support. Okay. So, when an event triggers a notification, 121 00:05:40,320 --> 00:05:45,040 the user sees it instantly in their inbox. And there's zero setup for the developer 122 00:05:45,040 --> 00:05:45,120 to 123 00:05:45,120 --> 00:05:48,720 get websockets or polling infrastructure running. That's huge. What's number two? 124 00:05:48,720 --> 00:05:49,040 Second, 125 00:05:49,040 --> 00:05:54,760 and this is crucial for user retention, is user preferences. Oh, letting the user 126 00:05:54,760 --> 00:05:55,440 take control. 127 00:05:55,440 --> 00:05:59,830 Exactly. It's a built-in UI that lets the end user customize what notifications 128 00:05:59,830 --> 00:06:00,720 they get, 129 00:06:00,720 --> 00:06:03,890 and this is the key part on which channel they get them. So, I could say low 130 00:06:03,890 --> 00:06:04,880 priority stuff to 131 00:06:04,880 --> 00:06:09,100 my email, but high priority alerts straight to the app. Precisely. And NoVoo 132 00:06:09,100 --> 00:06:10,000 handles all the 133 00:06:10,000 --> 00:06:15,680 routing logic needed to respect that choice. Giving the user that granular control 134 00:06:15,680 --> 00:06:16,800 is paramount in the 135 00:06:16,800 --> 00:06:20,710 battle against app fatigue. Absolutely. And the third feature. The third is snooze 136 00:06:20,710 --> 00:06:21,680 functionality. 137 00:06:21,680 --> 00:06:27,520 This lets users, and I'm quoting, snooze a message to when they will need it most. 138 00:06:27,520 --> 00:06:28,160 So, instead of 139 00:06:28,160 --> 00:06:32,070 just dismissing an alert because it's inconvenient right now, they can defer it. 140 00:06:32,070 --> 00:06:33,120 Right. It shifts the 141 00:06:33,120 --> 00:06:38,560 notification from being a distracting interruption to a genuinely helpful context-specific 142 00:06:38,560 --> 00:06:39,200 reminder. 143 00:06:39,200 --> 00:06:42,950 That centralization is powerful. But let's hit on the channels themselves. A 144 00:06:42,950 --> 00:06:44,080 crucial part of this 145 00:06:44,080 --> 00:06:48,640 unified system is that it has to handle every delivery method out there. It does. 146 00:06:48,640 --> 00:06:49,040 If I'm a 147 00:06:49,040 --> 00:06:54,340 high-volume sender, I might worry about reliability or vendor lock-in. So, can you 148 00:06:54,340 --> 00:06:55,280 walk us through the 149 00:06:55,280 --> 00:07:00,120 breadth of providers Novu actually manages? It's truly comprehensive. They act as 150 00:07:00,120 --> 00:07:01,120 the intermediary 151 00:07:01,120 --> 00:07:04,270 across basically every modern communication channel you can think of. Okay, let's 152 00:07:04,270 --> 00:07:05,200 start with email. 153 00:07:05,200 --> 00:07:12,320 For email, they integrate with SendGrid, Mailgun, AWS SES, and Postmark. And the 154 00:07:12,320 --> 00:07:13,200 fact they also allow 155 00:07:13,200 --> 00:07:17,840 custom SMTP means if you have some niche or legacy provider, you're not locked out. 156 00:07:17,840 --> 00:07:18,640 So wait, a company 157 00:07:18,640 --> 00:07:23,340 could switch its entire email service provider, say, from Postmark to SES and the 158 00:07:23,340 --> 00:07:24,480 actual application 159 00:07:24,480 --> 00:07:28,640 code? Would not need a single line changed. That's the vendor agnostic dream right 160 00:07:28,640 --> 00:07:30,160 there. It is. And 161 00:07:30,160 --> 00:07:35,290 it's a similar story for SMS. They cover all the meter gateways, Twilio, Plevo, SNS, 162 00:07:35,290 --> 00:07:36,080 and Nexmo, 163 00:07:36,080 --> 00:07:42,240 which is now Vonage. Okay, let me push back a little here. A potential friction 164 00:07:42,240 --> 00:07:42,480 point. 165 00:07:42,480 --> 00:07:48,420 Go for it. Doesn't adding Novu as this middle layer introduce its own complexity or 166 00:07:48,420 --> 00:07:48,960 potentially 167 00:07:48,960 --> 00:07:54,220 increase latency compared to talking directly to, say, Twilio? Why is the 168 00:07:54,220 --> 00:07:56,000 abstraction worth that risk? 169 00:07:56,000 --> 00:08:00,080 That is a really fair point, but you have to look at the total cost of ownership. 170 00:08:00,080 --> 00:08:03,920 Yes, you're adding one later abstraction, one more hop, but you're eliminating 171 00:08:03,920 --> 00:08:05,120 maybe 50 layers of 172 00:08:05,120 --> 00:08:10,250 bespoke brittle complexity. If Twilio's API changes, Novu's team handles that 173 00:08:10,250 --> 00:08:10,960 update, 174 00:08:10,960 --> 00:08:15,970 not your development team. I see. And if a provider fails, Novu has built in failover 175 00:08:15,970 --> 00:08:16,000 to 176 00:08:16,000 --> 00:08:20,140 try another channel or another provider without you writing complex error handling 177 00:08:20,140 --> 00:08:20,720 for every 178 00:08:20,720 --> 00:08:25,360 single vendor combination. The reliability and reduced maintenance burden, it just 179 00:08:25,360 --> 00:08:26,080 far outweighs 180 00:08:26,080 --> 00:08:30,470 any marginal latency concern. That makes sense. And just to finish the list, for 181 00:08:30,470 --> 00:08:31,600 push notifications, 182 00:08:31,600 --> 00:08:37,600 they handle FCM for Android, APNs for Apple, plus platforms like Expo and OneSignal. 183 00:08:37,600 --> 00:08:38,560 And for chat, 184 00:08:38,560 --> 00:08:44,080 which is crucial for teams, they've got Slack, Discord, MS Teams, and Mattermost. 185 00:08:44,080 --> 00:08:44,480 They really 186 00:08:44,480 --> 00:08:49,440 do cover the entire spectrum. They do. So beyond just sending a single notification, 187 00:08:49,440 --> 00:08:50,240 Novu offers 188 00:08:50,240 --> 00:08:55,740 tools to manage how and when things get delivered. This is the workflow orchestration 189 00:08:55,740 --> 00:08:56,720 layer. This is 190 00:08:56,720 --> 00:09:01,150 where the real intelligence is. This is what turns Novu from just a multi-send tool 191 00:09:01,150 --> 00:09:02,000 into a user 192 00:09:02,000 --> 00:09:06,320 experience enhancer. How so? The notification workflow engine. It lets product 193 00:09:06,320 --> 00:09:07,040 managers create 194 00:09:07,040 --> 00:09:11,030 these visual workflows with defined steps, conditions, channel fallbacks. And the 195 00:09:11,030 --> 00:09:11,280 best 196 00:09:11,280 --> 00:09:14,840 example of this seems to be the digest engine. Oh, absolutely. It's the perfect 197 00:09:14,840 --> 00:09:15,680 illustration. 198 00:09:15,680 --> 00:09:20,160 It's designed specifically to combat notification spam. That constant pinging. 199 00:09:20,160 --> 00:09:21,120 Exactly. Yeah. Like 200 00:09:21,120 --> 00:09:24,520 if you use a shared document system, you might get five separate emails in 10 201 00:09:24,520 --> 00:09:25,200 minutes about 202 00:09:25,200 --> 00:09:29,080 tiny little edits. The digest engine collects those five events. Yeah, and bundles 203 00:09:29,080 --> 00:09:29,440 them up. 204 00:09:29,440 --> 00:09:34,700 And combines them into a single email or SMS message. So the developer can just 205 00:09:34,700 --> 00:09:35,840 tell Novu, 206 00:09:35,840 --> 00:09:40,390 hey, just wait 60 minutes. And if you see three or more of these things pile up. 207 00:09:40,390 --> 00:09:41,040 And send one 208 00:09:41,040 --> 00:09:45,760 single summary. Instead of three separate pings, that dramatically reduces noise 209 00:09:45,760 --> 00:09:46,320 and ensures that 210 00:09:46,320 --> 00:09:50,640 when the user does get a notification, it has higher signal value. The user isn't 211 00:09:50,640 --> 00:09:51,120 annoyed. 212 00:09:51,120 --> 00:09:54,960 They're efficiently informed. And what about creating the actual emails? They 213 00:09:54,960 --> 00:09:55,520 integrate a 214 00:09:55,520 --> 00:10:01,120 block-based email editor. They do. Which provides a no-code editor for basic design. 215 00:10:01,120 --> 00:10:01,680 But the real 216 00:10:01,680 --> 00:10:06,280 secret weapon here is that it's all powered by React email. For listeners who haven't 217 00:10:06,280 --> 00:10:06,880 used that, 218 00:10:06,880 --> 00:10:11,200 why is that such a big deal? Because creating responsive, consistent emails with 219 00:10:11,200 --> 00:10:11,840 traditional 220 00:10:11,840 --> 00:10:17,250 HTML is just, notoriously brittle and painful. Using React components to build your 221 00:10:17,250 --> 00:10:18,000 templates 222 00:10:18,000 --> 00:10:22,560 makes them reliable, reusable, and easy to maintain. It brings email templating 223 00:10:22,560 --> 00:10:22,800 into 224 00:10:22,800 --> 00:10:27,200 the modern front-end world. That flexibility really seems to support their whole 225 00:10:27,200 --> 00:10:27,680 mantra, 226 00:10:27,680 --> 00:10:33,050 start simple, scale to code. It's the ultimate growth path. A beginner can start in 227 00:10:33,050 --> 00:10:33,600 the simple 228 00:10:33,600 --> 00:10:38,300 UI, dragging and dropping. But when they level up and need runtime control, or 229 00:10:38,300 --> 00:10:39,360 advanced logic, 230 00:10:39,360 --> 00:10:43,680 or the full power of React email, they can just break into code. They don't have to 231 00:10:43,680 --> 00:10:44,160 abandon the 232 00:10:44,160 --> 00:10:48,070 infrastructure. Not at all. They just gain finer programmatic control over it. So, 233 00:10:48,070 --> 00:10:48,560 since this is 234 00:10:48,560 --> 00:10:51,840 open source, let's quickly touch on their business model. They call it OpenCore. 235 00:10:51,840 --> 00:10:53,280 Right. I see the 236 00:10:53,280 --> 00:10:58,540 transparency, but is there any concern that locking the most critical scaling 237 00:10:58,540 --> 00:10:59,680 features behind a 238 00:10:59,680 --> 00:11:04,380 commercial license might deter some big companies from adopting it? That's the 239 00:11:04,380 --> 00:11:05,200 classic challenge of 240 00:11:05,200 --> 00:11:09,920 the OpenCore model, but I think Novoo is very transparent about the split. The core 241 00:11:09,920 --> 00:11:10,880 technology, 242 00:11:10,880 --> 00:11:15,600 the unified API, the essential delivery logic, the basic workflows, that's all 243 00:11:15,600 --> 00:11:16,560 fully open source 244 00:11:16,560 --> 00:11:21,120 under the MIT license. So, you can use it freely forever? Forever. The enterprise 245 00:11:21,120 --> 00:11:21,600 features, which 246 00:11:21,600 --> 00:11:25,450 you'll see in folders like enterprise and the repo, are usually things like 247 00:11:25,450 --> 00:11:26,800 advanced security, 248 00:11:26,800 --> 00:11:30,640 governance controls, fine-grained access management. The stuff that big 249 00:11:30,640 --> 00:11:31,280 corporations 250 00:11:31,280 --> 00:11:36,530 need for compliance. Exactly. So, the developers get the core value for free and 251 00:11:36,530 --> 00:11:37,280 the enterprises 252 00:11:37,280 --> 00:11:41,250 pay for the tools they need for their specific regulatory environments. That makes 253 00:11:41,250 --> 00:11:41,760 the division 254 00:11:41,760 --> 00:11:46,480 really clear. Okay, to wrap things up, let's distill the core knowledge for you, 255 00:11:46,480 --> 00:11:47,120 the listener. 256 00:11:47,120 --> 00:11:51,930 Go for it. Novoo tackles the notification headache with a unified API, which 257 00:11:51,930 --> 00:11:53,360 dramatically simplifies 258 00:11:53,360 --> 00:11:59,360 multi-channel delivery. It provides that simple embeddable inbox component. And crucially, 259 00:11:59,360 --> 00:11:59,520 it 260 00:11:59,520 --> 00:12:03,980 offers intelligent workflow tools like the digest engine to reduce user fatigue and 261 00:12:03,980 --> 00:12:04,720 spam. And 262 00:12:04,720 --> 00:12:09,600 accessibility is key. It's free to start, ready to scale. They offer a very 263 00:12:09,600 --> 00:12:11,440 generous 10k events month, 264 00:12:11,440 --> 00:12:16,960 free forever. Which lowers the barrier to entry significantly. Any project can get 265 00:12:16,960 --> 00:12:17,600 enterprise grade 266 00:12:17,600 --> 00:12:21,390 notifications right away. Right. And the enthusiasm from the community really 267 00:12:21,390 --> 00:12:22,560 speaks for itself with 268 00:12:22,560 --> 00:12:27,120 people calling it the best solution for notifications. They are clearly hitting a 269 00:12:27,120 --> 00:12:28,400 nerve. Which I think 270 00:12:28,400 --> 00:12:32,280 raises an important question for you to consider as this kind of infrastructure 271 00:12:32,280 --> 00:12:33,200 becomes the norm. 272 00:12:33,200 --> 00:12:37,680 Given the deep control Novo gives users over their preferences, combined with smart 273 00:12:37,680 --> 00:12:38,400 features like the 274 00:12:38,400 --> 00:12:43,530 digest engine, what deeper impact does this kind of centralized notification 275 00:12:43,530 --> 00:12:44,960 management have 276 00:12:44,960 --> 00:12:50,480 on reducing user fatigue globally? So is this a fundamental shift? Is this shift 277 00:12:50,480 --> 00:12:51,280 towards unified 278 00:12:51,280 --> 00:12:56,160 orchestration fundamentally a quality of life improvement for every end user? Is it 279 00:12:56,160 --> 00:12:56,560 a way to 280 00:12:56,560 --> 00:13:00,990 ensure that only the most relevant context specific information is what truly 281 00:13:00,990 --> 00:13:01,920 breaks through all the 282 00:13:01,920 --> 00:13:06,240 noise? That's a powerful way to frame it. It changes the notification from just a 283 00:13:06,240 --> 00:13:07,280 simple ping 284 00:13:07,280 --> 00:13:12,240 to a curated respectful communication. Exactly. Thank you for joining us for this 285 00:13:12,240 --> 00:13:12,960 dupe dive into 286 00:13:12,960 --> 00:13:16,760 Novo. My pleasure. And a reminder that this deep dive was made possible by Safe 287 00:13:16,760 --> 00:13:18,000 Server. Safe Server 288 00:13:18,000 --> 00:13:21,840 assists with software hosting and digital transformation, providing that robust 289 00:13:21,840 --> 00:13:25,040 backbone for modern applications. For more info, check them out. For more 290 00:13:25,040 --> 00:13:26,000 information on securing 291 00:13:26,000 --> 00:13:31,760 your infrastructure, please visit www.safeserver.de. We'll catch you next time.