1
00:00:00,111 --> 00:00:07,876
[SPEAKER_01] You know, if you were building a brand new corporate headquarters, you wouldn't let the construction company just, like, keep the master keys to your front door.

2
00:00:08,276 --> 00:00:08,536
[SPEAKER_00] Right.

3
00:00:08,696 --> 00:00:09,837
[SPEAKER_00] No, that would be crazy.

4
00:00:10,037 --> 00:00:10,497
[SPEAKER_01] Exactly.

5
00:00:10,818 --> 00:00:13,819
[SPEAKER_01] You certainly wouldn't say, sure, build my office.

6
00:00:13,959 --> 00:00:21,184
[SPEAKER_01] But, you know, you get to decide who walks into the lobby and, well, feel free to just dig through my filing cabinets whenever the mood strikes.

7
00:00:21,553 --> 00:00:24,574
[SPEAKER_00] Yeah, that would literally be corporate malpractice.

8
00:00:24,614 --> 00:00:31,315
[SPEAKER_00] I mean, you'd never compromise your physical security or your proprietary info like that.

9
00:00:31,375 --> 00:00:33,516
[SPEAKER_00] You absolutely demand ownership of the space.

10
00:00:33,816 --> 00:00:34,036
[SPEAKER_01] Right.

11
00:00:34,496 --> 00:00:45,238
[SPEAKER_01] But when we step into the digital world, and specifically how organizations or associations and businesses communicate with their audiences through newsletters, that is exactly what we do.

12
00:00:45,298 --> 00:00:46,398
[SPEAKER_00] We just hand them the keys.

13
00:00:46,818 --> 00:00:49,179
[SPEAKER_01] We just hand over the master keys to our contact lists.

14
00:00:50,073 --> 00:00:59,742
[SPEAKER_01] And before we dive into a truly fascinating solution to that exact problem today, I really want to start by thanking the supporter of today's deep dive, which is Safe Server.

15
00:01:00,703 --> 00:01:08,290
[SPEAKER_01] Because, you know, think about the incredibly expensive proprietary tools that organizations rely on every single day for their communication.

16
00:01:08,310 --> 00:01:08,830
[SPEAKER_00] Oh yeah.

17
00:01:09,411 --> 00:01:10,832
[SPEAKER_00] The massive walled gardens.

18
00:01:10,972 --> 00:01:11,413
[SPEAKER_01] Exactly.

19
00:01:11,453 --> 00:01:12,053
[SPEAKER_01] The giants.

20
00:01:12,133 --> 00:01:16,217
[SPEAKER_01] We're talking Microsoft, Google, MailChimp, Sendin' Blue.

21
00:01:16,588 --> 00:01:20,251
[SPEAKER_00] It's essentially a landlord-tenant relationship with those companies.

22
00:01:20,771 --> 00:01:26,756
[SPEAKER_00] You are basically renting space for your own audience, and you're paying an absolute premium for the privilege.

23
00:01:26,956 --> 00:01:30,199
[SPEAKER_01] Yeah, and Safe Server offers a completely different path here.

24
00:01:30,259 --> 00:01:33,521
[SPEAKER_01] They basically help organizations transition to open source solutions.

25
00:01:34,062 --> 00:01:37,905
[SPEAKER_01] And I mean, the cost difference of switching away from those giants can be absolutely massive.

26
00:01:37,945 --> 00:01:38,245
[SPEAKER_01] Cute.

27
00:01:38,325 --> 00:01:40,907
[SPEAKER_01] But crucially, this isn't just like a budget conversation.

28
00:01:41,307 --> 00:01:45,871
[SPEAKER_01] If you are dealing with legal, regulatory, or compliance requirements,

29
00:01:45,911 --> 00:01:46,972
[SPEAKER_00] Which so many are.

30
00:01:47,312 --> 00:01:57,016
[SPEAKER_01] Right, things like strict email retention policies, rigorous data protection laws, financial records, secure audit trails, data sovereignty, literally everything.

31
00:01:57,077 --> 00:01:57,677
[SPEAKER_00] It has to be.

32
00:01:57,717 --> 00:02:09,102
[SPEAKER_00] I mean, you simply cannot afford to have highly sensitive contact lists just sitting on some proprietary server halfway across the world governed by an entirely different set of privacy laws.

33
00:02:09,162 --> 00:02:12,624
[SPEAKER_01] Right, where an algorithm update could suddenly lock you out of your own communications.

34
00:02:12,744 --> 00:02:13,204
[SPEAKER_00] Exactly.

35
00:02:13,244 --> 00:02:14,225
[SPEAKER_00] It's a massive risk.

36
00:02:14,463 --> 00:02:28,700
[SPEAKER_01] Which is exactly why SafeServer helps organizations find and implement the right open source tool for their specific needs, taking you from the initial consulting phase right through to secure reliable operation right there on German servers.

37
00:02:29,160 --> 00:02:34,206
[SPEAKER_01] You can find more information about regaining your digital independence at www.safeserver.de.

38
00:02:34,787 --> 00:02:35,767
[SPEAKER_00] It's so important right now.

39
00:02:35,987 --> 00:02:36,488
[SPEAKER_01] It really is.

40
00:02:36,708 --> 00:02:38,128
[SPEAKER_01] So OK, let's unpack this.

41
00:02:38,148 --> 00:02:38,948
[SPEAKER_01] Welcome to the Deep Dive.

42
00:02:39,008 --> 00:02:49,232
[SPEAKER_01] Today we are looking at a stack of sources, specifically a GitHub repository and the official website documentation for an open source software called Keela.

43
00:02:49,392 --> 00:02:49,992
[SPEAKER_00] Yeah, Keela.

44
00:02:50,292 --> 00:03:02,896
[SPEAKER_01] And for any beginner looking to start a newsletter without getting locked into a proprietary ecosystem or without just feeding their subscribers' data to a massive tech conglomerate, this is the perfect entry point.

45
00:03:03,103 --> 00:03:06,104
[SPEAKER_00] It really is a game changer for that specific demographic.

46
00:03:06,184 --> 00:03:06,364
[SPEAKER_01] Yeah.

47
00:03:06,584 --> 00:03:16,107
[SPEAKER_01] So our mission today is to explore how a 100% open source tool can basically combine beginner friendly design with enterprise level privacy.

48
00:03:16,207 --> 00:03:16,447
[SPEAKER_00] Right.

49
00:03:16,627 --> 00:03:24,869
[SPEAKER_00] And to really understand why Keila is making such waves in the developer and marketing communities, we really first have to look at what it actually is.

50
00:03:25,389 --> 00:03:31,591
[SPEAKER_00] And more importantly, how it dismantles the usual barriers that keep beginners entirely away from open source tools.

51
00:03:31,831 --> 00:03:32,171
[SPEAKER_01] Totally.

52
00:03:32,191 --> 00:03:35,533
[SPEAKER_01] So let's start with the most welcoming part, which, I mean, is the branding.

53
00:03:35,613 --> 00:03:37,634
[SPEAKER_01] Keela is actually the name of the project's mascot.

54
00:03:37,734 --> 00:03:38,855
[SPEAKER_00] Yes, the elephant.

55
00:03:38,995 --> 00:03:44,397
[SPEAKER_01] Yeah, according to the documentation, she is a wise, diligent elephant lady who remembers countless email addresses.

56
00:03:44,537 --> 00:03:44,918
[SPEAKER_00] Yeah.

57
00:03:45,658 --> 00:03:49,180
[SPEAKER_01] And I have to mention my absolute favorite detail from the source material.

58
00:03:49,680 --> 00:03:52,281
[SPEAKER_01] She apparently loves holidaying in the lakes of Finland.

59
00:03:52,361 --> 00:03:53,342
[SPEAKER_00] Which is just so great.

60
00:03:53,602 --> 00:03:54,642
[SPEAKER_00] It's incredibly charming.

61
00:03:54,742 --> 00:03:57,264
[SPEAKER_01] And that charm is a very, very intentional design choice.

62
00:03:58,084 --> 00:04:05,306
[SPEAKER_01] it immediately signals to the user that this isn't some, you know, intimidating hyper corporate sterile software.

63
00:04:05,486 --> 00:04:05,706
[SPEAKER_00] Right.

64
00:04:05,966 --> 00:04:16,008
[SPEAKER_00] But I do have to push back a little on the label open source software, though, because if you're listening to this and you aren't like a full stack developer, that phrase carries some pretty heavy baggage.

65
00:04:16,108 --> 00:04:16,748
[SPEAKER_01] Oh, absolutely.

66
00:04:16,788 --> 00:04:17,548
[SPEAKER_01] It sounds scary.

67
00:04:17,568 --> 00:04:17,788
[SPEAKER_00] Yeah.

68
00:04:18,168 --> 00:04:24,410
[SPEAKER_00] Usually when a beginner hears open source, they picture this, you know, dark terminal screen with the command line interface where

69
00:04:25,230 --> 00:04:28,793
[SPEAKER_00] You basically need a computer science degree just to send a hello world email.

70
00:04:29,033 --> 00:04:29,213
[SPEAKER_01] Yep.

71
00:04:29,373 --> 00:04:31,855
[SPEAKER_01] The green text on a black background stereotype.

72
00:04:31,935 --> 00:04:32,336
[SPEAKER_00] Exactly.

73
00:04:32,436 --> 00:04:36,919
[SPEAKER_00] So if I barely know how to format a Word document, is Keela just going to leave me in the dust?

74
00:04:37,199 --> 00:04:42,544
[SPEAKER_01] Well, that is the classic and honestly often justified open source stereotype.

75
00:04:42,704 --> 00:04:46,487
[SPEAKER_01] But Keela is engineered specifically to solve that exact barrier to entry.

76
00:04:46,867 --> 00:04:53,512
[SPEAKER_01] They've designed the platform to like meet you exactly where your technical skills are today and then essentially grow with you.

77
00:04:53,812 --> 00:04:54,032
[SPEAKER_00] OK.

78
00:04:55,049 --> 00:04:55,489
[SPEAKER_00] How so?

79
00:04:55,830 --> 00:04:58,932
[SPEAKER_00] Well, they offer four distinct ways to create emails.

80
00:04:59,693 --> 00:05:04,677
[SPEAKER_00] So if you have absolutely zero coding experience, you just start with their visual block editor.

81
00:05:04,757 --> 00:05:05,818
[SPEAKER_01] Like a drag and drop thing.

82
00:05:06,038 --> 00:05:06,598
[SPEAKER_00] Exactly.

83
00:05:06,638 --> 00:05:12,543
[SPEAKER_00] It's a super intuitive interface where you literally drag and drop text, images, buttons right onto a canvas.

84
00:05:13,224 --> 00:05:20,770
[SPEAKER_00] In fact, looking at the recent updates from the sources, they just added granular text alignment options right within those visual blocks.

85
00:05:20,910 --> 00:05:21,310
[SPEAKER_01] Oh, nice.

86
00:05:21,410 --> 00:05:24,613
[SPEAKER_00] Yeah, giving you precise control without ever touching a single line of code.

87
00:05:24,928 --> 00:05:27,090
[SPEAKER_01] Okay, but say I'm someone who writes a ton of blogs, right?

88
00:05:28,351 --> 00:05:32,735
[SPEAKER_01] And I find those visual drag-and-drop editors to be a bit, I don't know, clunky or slow.

89
00:05:32,835 --> 00:05:34,657
[SPEAKER_01] I just want to write clean text fast.

90
00:05:34,677 --> 00:05:37,960
[SPEAKER_00] Then you'd step up to their Markdown powered YCWG editor.

91
00:05:38,120 --> 00:05:40,042
[SPEAKER_01] Okay, let's translate that for the non-technical folks.

92
00:05:40,342 --> 00:05:43,445
[SPEAKER_01] YCWG stands for what you see is what you get, right?

93
00:05:43,465 --> 00:05:43,625
[SPEAKER_01] Right.

94
00:05:43,965 --> 00:05:45,967
[SPEAKER_01] But how does the Markdown part actually work?

95
00:05:46,207 --> 00:05:52,469
[SPEAKER_00] So Markdown is this beautifully simple way to format text just using standard keyboard symbols.

96
00:05:52,589 --> 00:05:59,232
[SPEAKER_00] For example, if you type an asterisk before and after a word, the editor just automatically knows to make that word bold.

97
00:05:59,692 --> 00:06:01,933
[SPEAKER_00] Yeah, or like a hashtag creates a header.

98
00:06:02,299 --> 00:06:06,881
[SPEAKER_00] It basically translates those simple symbols into clean, perfectly formatted code in the background.

99
00:06:07,161 --> 00:06:11,703
[SPEAKER_00] So it gives you a very fast writing experience without the bloat of a visual block editor.

100
00:06:11,843 --> 00:06:12,703
[SPEAKER_01] That makes total sense.

101
00:06:13,083 --> 00:06:16,505
[SPEAKER_01] But what if I have an actual design team?

102
00:06:16,525 --> 00:06:23,908
[SPEAKER_01] What if I need incredibly complex custom layouts that have to look absolutely perfect on an iPhone, an Android, and a desktop monitor?

103
00:06:24,048 --> 00:06:28,970
[SPEAKER_00] Okay, so that brings us to the third option, which is where Keela really flexes its technical muscles.

104
00:06:29,330 --> 00:06:30,871
[SPEAKER_00] It natively supports MJML.

105
00:06:30,911 --> 00:06:32,451
[SPEAKER_01] Hold on, alphabet soup there.

106
00:06:32,691 --> 00:06:33,212
[SPEAKER_01] MJML.

107
00:06:33,632 --> 00:06:36,093
[SPEAKER_01] Why do we need a specialized language just for emails?

108
00:06:36,453 --> 00:06:39,574
[SPEAKER_01] Why can't we just use regular HTML like we do for every other website?

109
00:06:39,974 --> 00:06:40,534
[SPEAKER_00] Oh, okay.

110
00:06:40,994 --> 00:06:44,035
[SPEAKER_00] What's fascinating here is the chaotic nature of email clients.

111
00:06:44,336 --> 00:06:49,197
[SPEAKER_00] If you build a beautiful webpage, modern web browsers all generally agree on how to display it, right?

112
00:06:49,237 --> 00:06:49,377
[SPEAKER_00] Right.

113
00:06:49,717 --> 00:06:51,318
[SPEAKER_01] Chrome, Safari, they handle it.

114
00:06:51,418 --> 00:06:51,818
[SPEAKER_00] Exactly.

115
00:06:51,898 --> 00:06:58,460
[SPEAKER_00] But email clients like Outlook, Apple Mail, Gmail, they are notoriously terrible at rendering HTML consistently.

116
00:06:58,480 --> 00:07:03,862
[SPEAKER_00] Like, an email that looks absolutely gorgeous in Gmail might look like a broken ransom note when someone opens it in Outlook.

117
00:07:04,062 --> 00:07:05,063
[SPEAKER_01] Well, I hate when that happens.

118
00:07:05,103 --> 00:07:05,603
[SPEAKER_00] We all do.

119
00:07:06,124 --> 00:07:08,826
[SPEAKER_00] So MJML was created specifically to solve this.

120
00:07:09,106 --> 00:07:21,336
[SPEAKER_00] It is a responsive markup language that automatically generates the bulletproof, really messy HTML required to force all those different email clients to display your design correctly.

121
00:07:22,037 --> 00:07:22,597
[SPEAKER_01] Ah, got it.

122
00:07:22,837 --> 00:07:23,077
[SPEAKER_00] Yeah.

123
00:07:23,278 --> 00:07:27,921
[SPEAKER_00] So by supporting MJML, Keela is catering directly to top tier developers and designers.

124
00:07:28,162 --> 00:07:28,802
[SPEAKER_01] So that's three.

125
00:07:29,082 --> 00:07:29,943
[SPEAKER_01] What's the fourth option?

126
00:07:30,323 --> 00:07:31,723
[SPEAKER_00] Good old-fashioned plain text.

127
00:07:32,404 --> 00:07:33,504
[SPEAKER_00] Just words on a screen.

128
00:07:34,064 --> 00:07:37,546
[SPEAKER_00] Which, honestly, often actually have the highest deliverability rates anyway.

129
00:07:37,986 --> 00:07:40,527
[SPEAKER_01] I really appreciate that structural progression, though.

130
00:07:40,747 --> 00:07:40,927
[SPEAKER_00] Yeah.

131
00:07:41,067 --> 00:07:45,688
[SPEAKER_01] I mean, it means a solo creator can start on day one with just simple drag and drop blocks.

132
00:07:45,889 --> 00:07:46,429
[SPEAKER_00] Exactly.

133
00:07:46,449 --> 00:07:58,333
[SPEAKER_01] But then a year later, when their list explodes and they hire a professional designer, they don't have to migrate their entire audience to a new, expensive enterprise platform just to get those advanced MJMLA out.

134
00:07:58,473 --> 00:07:58,713
[SPEAKER_00] Right.

135
00:07:58,853 --> 00:08:09,617
[SPEAKER_00] And if we connect this back to the bigger picture, you've essentially just described the holy grail of software design, eliminating the friction of starting while entirely removing the ceiling on what an advanced user can achieve.

136
00:08:09,837 --> 00:08:10,337
[SPEAKER_01] I love that.

137
00:08:10,377 --> 00:08:12,558
[SPEAKER_01] So OK, we know how to design the email.

138
00:08:12,698 --> 00:08:17,359
[SPEAKER_01] The next logical hurdle is figuring out how to get people to actually sign up for it.

139
00:08:17,459 --> 00:08:17,660
[SPEAKER_00] Yeah.

140
00:08:18,220 --> 00:08:20,961
[SPEAKER_01] And I have to use an analogy here.

141
00:08:21,881 --> 00:08:24,422
[SPEAKER_01] Having a newsletter sign up form on the open internet

142
00:08:25,162 --> 00:08:29,287
[SPEAKER_01] is a lot like leaving a giant bowl of candy on your porch on Halloween night.

143
00:08:29,687 --> 00:08:30,288
[SPEAKER_00] Oh, completely.

144
00:08:30,308 --> 00:08:31,609
[SPEAKER_01] The bots are going to show up.

145
00:08:32,150 --> 00:08:35,153
[SPEAKER_01] And they aren't just taking one piece, they're going to take the whole bowl.

146
00:08:35,213 --> 00:08:36,134
[SPEAKER_00] They absolutely will.

147
00:08:36,234 --> 00:08:41,379
[SPEAKER_01] Wait, so you're telling me my entire cinder reputation can be ruined just because automated bots fill out my form?

148
00:08:41,539 --> 00:08:42,581
[SPEAKER_00] Oh, absolutely ruined.

149
00:08:43,241 --> 00:08:47,426
[SPEAKER_00] And this is a massive, often invisible problem for beginners.

150
00:08:48,504 --> 00:09:00,091
[SPEAKER_00] See, when spam bots flood your signup form with thousands of fake email addresses, and then you try to send a newsletter to that list, the massive email providers, like Gmail and Yahoo, they take notice.

151
00:09:00,272 --> 00:09:01,252
[SPEAKER_01] Right, they see what's happening.

152
00:09:01,272 --> 00:09:09,698
[SPEAKER_00] Yeah, they see your server attempting to deliver thousands of messages to completely dead inboxes, and their algorithms instantly flag you as a spammer.

153
00:09:09,898 --> 00:09:16,422
[SPEAKER_00] From that moment on, even your legitimate emails to real humans get quietly routed to the junk folder.

154
00:09:16,722 --> 00:09:19,583
[SPEAKER_01] So how does Keela defend the porch, so to speak?

155
00:09:20,063 --> 00:09:23,103
[SPEAKER_00] It addresses it right at the front door with a multi-layered defense.

156
00:09:24,223 --> 00:09:30,965
[SPEAKER_00] So, first, they have a form builder that lets you create custom sign-up forms with checkboxes and drop-downs, all without coding.

157
00:09:31,545 --> 00:09:35,125
[SPEAKER_00] But behind that form, they integrate HCAPTCHA and FRIENDLYCAPTCHA.

158
00:09:35,526 --> 00:09:36,146
[SPEAKER_01] Oh, okay.

159
00:09:36,186 --> 00:09:38,626
[SPEAKER_01] Those are the little widgets that ask you to prove you're human, right?

160
00:09:38,726 --> 00:09:39,566
[SPEAKER_00] Yes, exactly.

161
00:09:39,626 --> 00:09:42,967
[SPEAKER_00] That stops the initial blunt force wave of automated scripts.

162
00:09:43,555 --> 00:09:48,880
[SPEAKER_00] But the ultimate ironclad defense here is confirmed opt-in, which is also known as double opt-in.

163
00:09:49,220 --> 00:09:50,161
[SPEAKER_01] OK, how does that work?

164
00:09:50,562 --> 00:09:55,706
[SPEAKER_00] Even if a really sophisticated bot manages to fill out the form, Keela holds that address in quarantine.

165
00:09:55,926 --> 00:09:57,928
[SPEAKER_00] It sends a verification email to that address.

166
00:09:58,229 --> 00:10:04,855
[SPEAKER_00] And if the link inside that specific email isn't actively clicked by a human, the address is just never added to your active list.

167
00:10:05,327 --> 00:10:05,507
[SPEAKER_01] Right.

168
00:10:05,747 --> 00:10:07,729
[SPEAKER_01] But here's where it gets really interesting, though.

169
00:10:08,209 --> 00:10:16,275
[SPEAKER_01] In the recent update section of the GitHub repository, there's a feature they just added called protected unsubscribe and double opt in links.

170
00:10:17,236 --> 00:10:22,440
[SPEAKER_01] And when you dig into the why behind this feature, it completely blows my mind.

171
00:10:22,520 --> 00:10:23,241
[SPEAKER_00] It's so cool.

172
00:10:23,301 --> 00:10:28,004
[SPEAKER_00] It really highlights the hidden mechanisms of the Internet that are constantly battling each other.

173
00:10:28,224 --> 00:10:29,025
[SPEAKER_01] Break it down for me.

174
00:10:29,568 --> 00:10:33,090
[SPEAKER_00] So corporate mail servers use these automated security scanners, right?

175
00:10:33,470 --> 00:10:44,515
[SPEAKER_00] When an email arrives at a company inbox, the security scanner rapidly clicks every single link in the email in the background to check for malware or phishing attempts before ever letting the employee see it.

176
00:10:44,635 --> 00:10:49,757
[SPEAKER_01] Which, I mean, sounds fantastic for corporate security, but absolutely terrible for a newsletter sender.

177
00:10:49,877 --> 00:10:50,617
[SPEAKER_00] It's a nightmare.

178
00:10:50,977 --> 00:11:01,120
[SPEAKER_01] Because if the scanner automatically clicks the unsubscribe link just to check it for viruses, it accidentally unsubscribes a real loyal reader who actually wanted your emails.

179
00:11:01,140 --> 00:11:01,980
[SPEAKER_00] Oh, precisely.

180
00:11:02,461 --> 00:11:07,782
[SPEAKER_00] Or even worse, the scanner clicks the double opt-in verification link and falsely verifies a bot.

181
00:11:08,342 --> 00:11:08,843
[SPEAKER_01] Oh, man.

182
00:11:09,023 --> 00:11:09,863
[SPEAKER_01] So how did they fix it?

183
00:11:10,245 --> 00:11:17,626
[SPEAKER_00] Keela essentially outsmarted these enterprise scanners by adding a clever additional verification step on those specific links.

184
00:11:18,207 --> 00:11:25,948
[SPEAKER_00] A machine scanner that's just clicking rapidly in the background won't pass the second step, but a human actively trying to unsubscribe or opt in will.

185
00:11:26,148 --> 00:11:34,130
[SPEAKER_01] That is an elegant, brilliant way to protect the integrity of your list from both malicious bots and, frankly, overzealous security software.

186
00:11:34,210 --> 00:11:34,770
[SPEAKER_00] Exactly.

187
00:11:35,030 --> 00:11:35,510
[SPEAKER_00] So smart.

188
00:11:36,323 --> 00:11:37,263
[SPEAKER_01] So what does this all mean?

189
00:11:37,583 --> 00:11:44,025
[SPEAKER_01] We have a beautifully designed email, and we have this pristine list full of verified, real human beings.

190
00:11:44,265 --> 00:11:47,966
[SPEAKER_01] Now you have to send them content that actually matters to them, which requires data.

191
00:11:48,206 --> 00:11:48,426
[SPEAKER_00] Right.

192
00:11:48,706 --> 00:11:54,428
[SPEAKER_01] But we want to do this without acting like a creepy surveillance corporation tracking their every single mouse movement.

193
00:11:55,223 --> 00:11:59,985
[SPEAKER_01] And I noticed Keela actually offers a one click option to just turn off tracking entirely.

194
00:12:00,025 --> 00:12:00,445
[SPEAKER_00] They do.

195
00:12:00,626 --> 00:12:05,768
[SPEAKER_00] And honestly, in an era of hyper surveillance capitalism, that is such a breath of fresh air.

196
00:12:06,088 --> 00:12:11,951
[SPEAKER_00] It really comes down to the delicate balance between useful analytics and respecting fundamental privacy.

197
00:12:12,451 --> 00:12:19,694
[SPEAKER_00] Like by default, Keela collects the essential metrics you need to gauge your content's performance, like open rates and click tracking.

198
00:12:20,054 --> 00:12:23,316
[SPEAKER_00] But it's strictly adheres to European privacy standards.

199
00:12:23,623 --> 00:12:30,930
[SPEAKER_01] And if you were running, say, like an internal company newsletter where you absolutely don't need those metrics, you just hit that one button and the tracking is completely gone.

200
00:12:31,011 --> 00:12:31,811
[SPEAKER_00] Yep, vanished.

201
00:12:32,532 --> 00:12:34,714
[SPEAKER_01] But let's assume I do want to personalize things.

202
00:12:35,135 --> 00:12:39,519
[SPEAKER_01] Like, I want to address my subscribers by name or send them highly specific content.

203
00:12:39,940 --> 00:12:42,162
[SPEAKER_01] How does Keela handle subscriber data?

204
00:12:42,807 --> 00:12:45,409
[SPEAKER_00] This is where the architecture of the software really shines.

205
00:12:45,849 --> 00:12:50,894
[SPEAKER_00] So Keela stores custom data for every single contact as a single JSON object.

206
00:12:51,034 --> 00:12:53,476
[SPEAKER_01] OK, let's step away from the developer jargon for just a second.

207
00:12:53,816 --> 00:12:58,179
[SPEAKER_01] How should a non-technical person visualize a JSON object?

208
00:12:58,560 --> 00:12:59,000
[SPEAKER_00] Fair enough.

209
00:12:59,380 --> 00:13:02,923
[SPEAKER_00] Think of a JSON object like a digital name tag for your subscriber.

210
00:13:03,143 --> 00:13:06,846
[SPEAKER_00] But instead of just having their name written on it, you can stick custom labels all over it.

211
00:13:06,986 --> 00:13:07,607
[SPEAKER_01] Like stickers.

212
00:13:07,985 --> 00:13:08,245
[SPEAKER_00] Yeah.

213
00:13:08,665 --> 00:13:22,513
[SPEAKER_00] In a traditional rigid spreadsheet, if you want to track a new piece of information, like, say, someone's favorite color, you have to add a new column for every single person on the list, even if 90% of them don't have a favorite color listed.

214
00:13:22,553 --> 00:13:24,354
[SPEAKER_01] Oh, and that gets incredibly messy fast.

215
00:13:24,394 --> 00:13:25,034
[SPEAKER_00] Very messy.

216
00:13:25,495 --> 00:13:28,876
[SPEAKER_00] But a JSON object uses what's called key value pairs.

217
00:13:29,297 --> 00:13:30,517
[SPEAKER_00] It's totally flexible.

218
00:13:30,557 --> 00:13:37,161
[SPEAKER_00] You can slap a favorite color, blue sticker on John's name tag, and a city Berlin sticker on Sarah's name tag,

219
00:13:37,421 --> 00:13:40,225
[SPEAKER_00] without needing some massive, rigid master template.

220
00:13:40,365 --> 00:13:41,306
[SPEAKER_01] I love that analogy.

221
00:13:41,427 --> 00:13:45,292
[SPEAKER_01] So I have these highly flexible digital name tags for my subscribers.

222
00:13:45,853 --> 00:13:47,455
[SPEAKER_01] How does the email actually read those tags?

223
00:13:47,756 --> 00:13:52,080
[SPEAKER_00] Keela utilizes Shopify's liquid template language to pull that data out.

224
00:13:52,440 --> 00:13:54,502
[SPEAKER_00] Liquid essentially acts as the logic engine.

225
00:13:54,642 --> 00:13:58,926
[SPEAKER_01] Wait, so Shopify liquid is the mechanism that injects the data into the email right at the moment it sends.

226
00:13:59,146 --> 00:13:59,627
[SPEAKER_00] Exactly.

227
00:13:59,707 --> 00:14:01,849
[SPEAKER_00] It allows you to use simple logic statements.

228
00:14:01,969 --> 00:14:09,636
[SPEAKER_00] So it's how the email knows to look at the name tag and say, if the city sticker says Berlin, insert this paragraph about our upcoming Berlin event.

229
00:14:10,016 --> 00:14:14,100
[SPEAKER_00] Yeah, it transforms a static broadcast into a deeply personalized letter.

230
00:14:14,584 --> 00:14:17,507
[SPEAKER_01] But you don't always want to send an email to everyone on your list, right?

231
00:14:17,527 --> 00:14:19,148
[SPEAKER_01] No matter how personalized the greeting is.

232
00:14:19,388 --> 00:14:21,150
[SPEAKER_01] Keela has a visual segment editor, right?

233
00:14:21,330 --> 00:14:21,610
[SPEAKER_00] Yes.

234
00:14:21,951 --> 00:14:27,296
[SPEAKER_00] Instead of blasting your entire database, you can visually create highly targeted subsets.

235
00:14:27,796 --> 00:14:32,320
[SPEAKER_00] You can filter by specific tags you've applied, or, crucially, by language preferences.

236
00:14:32,520 --> 00:14:37,125
[SPEAKER_01] Which is vital, because looking at the documentation, Keela itself is highly localized.

237
00:14:37,665 --> 00:14:43,391
[SPEAKER_01] It supports, let's see, English, German, French, Spanish, Bulgarian and Hungarian.

238
00:14:43,411 --> 00:14:44,552
[SPEAKER_00] That's a lot of coverage.

239
00:14:44,692 --> 00:14:44,892
[SPEAKER_01] Yeah.

240
00:14:45,313 --> 00:14:52,240
[SPEAKER_01] If you have a global audience, being able to segment your list by language so you aren't accidentally sending a German newsletter to a Spanish speaker.

241
00:14:52,900 --> 00:14:55,523
[SPEAKER_01] I mean, that's table stakes for a professional organization.

242
00:14:55,803 --> 00:14:59,267
[SPEAKER_01] And I saw they recently added an automated welcome emails feature too.

243
00:14:59,447 --> 00:14:59,667
[SPEAKER_00] Right.

244
00:14:59,767 --> 00:15:06,811
[SPEAKER_00] So the moment someone joins a specific segment, they automatically receive a personalized greeting tailored to that exact subset of your audience.

245
00:15:07,272 --> 00:15:13,115
[SPEAKER_00] It just creates a seamless, automated experience for the subscriber, driven entirely by data that you control.

246
00:15:13,335 --> 00:15:16,377
[SPEAKER_01] Which really brings us to the core philosophy of this software.

247
00:15:16,757 --> 00:15:25,923
[SPEAKER_01] I mean, we've talked about what it does, but none of this personalization or bot protection really matters if the software company decides to just double their prices overnight.

248
00:15:26,203 --> 00:15:27,585
[SPEAKER_00] Oh, which happens all the time.

249
00:15:27,745 --> 00:15:28,245
[SPEAKER_01] All the time.

250
00:15:28,506 --> 00:15:31,009
[SPEAKER_01] Or an algorithm suddenly locks you out of your account.

251
00:15:31,689 --> 00:15:33,912
[SPEAKER_01] That's why the underlying architecture is so vital.

252
00:15:35,073 --> 00:15:42,942
[SPEAKER_01] Looking under the hood at the GitHub repository, Keela is primarily built in a programming language called Elixir.

253
00:15:42,962 --> 00:15:44,784
[SPEAKER_01] 68% of the code base, to be exact.

254
00:15:45,530 --> 00:15:46,191
[SPEAKER_01] Why Elixir?

255
00:15:46,431 --> 00:15:49,255
[SPEAKER_00] OK, this is where the engineering gets really impressive.

256
00:15:49,815 --> 00:15:52,238
[SPEAKER_00] Elixir runs on the Erlang virtual machine.

257
00:15:52,339 --> 00:15:54,922
[SPEAKER_00] And to understand why that matters, we actually have to go back to the 1980s.

258
00:15:55,062 --> 00:15:56,544
[SPEAKER_01] The 80s, OK. Yeah.

259
00:15:56,944 --> 00:15:59,928
[SPEAKER_00] Erlang was originally developed by Ericsson for telephone switches.

260
00:15:59,988 --> 00:16:03,613
[SPEAKER_01] Telephone switches, like literally routing physical phone calls.

261
00:16:04,037 --> 00:16:04,738
[SPEAKER_00] Exactly.

262
00:16:04,838 --> 00:16:07,080
[SPEAKER_00] Think about a massive telecom network.

263
00:16:07,520 --> 00:16:12,785
[SPEAKER_00] It has to handle tens of thousands of simultaneous phone calls without dropping a single one, right?

264
00:16:13,366 --> 00:16:15,207
[SPEAKER_00] And the system can never, ever crash.

265
00:16:15,628 --> 00:16:20,692
[SPEAKER_00] That requires incredible concurrency, which is the ability to do many things at the exact same time.

266
00:16:21,533 --> 00:16:27,977
[SPEAKER_00] Fast forward to today, and that same underlying technology is what routes billions of concurrent messages on WhatsApp.

267
00:16:28,077 --> 00:16:30,098
[SPEAKER_01] Wait, my mind is slightly blown here.

268
00:16:30,198 --> 00:16:36,742
[SPEAKER_01] So Keyla is using the same foundational technology that handles WhatsApp's massive global traffic just to send newsletters.

269
00:16:36,982 --> 00:16:44,743
[SPEAKER_00] Yes, because sending out a newsletter to, say, 100,000 people simultaneously is actually a massive concurrency challenge.

270
00:16:45,164 --> 00:16:50,044
[SPEAKER_00] Traditional web frameworks often choke and just crash when trying to blast out that many emails at once.

271
00:16:50,125 --> 00:16:51,085
[SPEAKER_01] Oh, that makes total sense.

272
00:16:51,225 --> 00:16:51,445
[SPEAKER_00] Yeah.

273
00:16:51,585 --> 00:16:54,085
[SPEAKER_00] Elixir handles massive scale effortlessly.

274
00:16:54,585 --> 00:16:59,206
[SPEAKER_00] It ensures Keyleth is lightweight, incredibly fast, and just rock solid reliable.

275
00:16:59,386 --> 00:17:01,367
[SPEAKER_01] OK, so the engine is an absolute powerhouse.

276
00:17:01,927 --> 00:17:02,787
[SPEAKER_01] What about the licensing?

277
00:17:03,367 --> 00:17:06,091
[SPEAKER_01] Because it operates under an AGPL v3 license.

278
00:17:06,612 --> 00:17:08,594
[SPEAKER_01] For those of us who aren't, you know, copyright lawyers.

279
00:17:08,875 --> 00:17:12,059
[SPEAKER_01] What does that actually mean for my data and the software's future?

280
00:17:12,440 --> 00:17:16,225
[SPEAKER_00] Okay, AGPL v3 is a very specific type of open source license.

281
00:17:16,966 --> 00:17:18,408
[SPEAKER_00] The A stands for a pharaoh.

282
00:17:18,733 --> 00:17:21,557
[SPEAKER_00] It's essentially designed to close what's known as the cloud loophole.

283
00:17:21,658 --> 00:17:22,659
[SPEAKER_01] Which is what exactly?

284
00:17:22,679 --> 00:17:33,195
[SPEAKER_00] Well, historically, massive tech giants would just take free open source code, run it on their own servers as a paid service, and then never contribute their improvements back to the community.

285
00:17:33,522 --> 00:17:33,922
[SPEAKER_01] Oh, wow.

286
00:17:34,423 --> 00:17:35,904
[SPEAKER_01] Just profiting off the free work.

287
00:17:36,064 --> 00:17:36,564
[SPEAKER_00] Precisely.

288
00:17:36,884 --> 00:17:46,250
[SPEAKER_00] The AGTL v3 license strictly mandates that if you modify the software and offer it as a service over a network, you must release your modified source code.

289
00:17:46,710 --> 00:17:52,834
[SPEAKER_00] It basically legally guarantees that Keeler remains truly open and completely prevents corporate monopolization of the code.

290
00:17:53,074 --> 00:17:54,998
[SPEAKER_01] Now that is true digital sovereignty.

291
00:17:55,719 --> 00:18:03,835
[SPEAKER_01] So practically speaking, if I'm listening to this and I want to deploy Kiela for my organization right now, where does my data actually live?

292
00:18:04,067 --> 00:18:06,069
[SPEAKER_00] You basically have two very distinct paths.

293
00:18:06,289 --> 00:18:07,711
[SPEAKER_00] The first path is Kela Cloud.

294
00:18:07,991 --> 00:18:09,032
[SPEAKER_00] This is their managed service.

295
00:18:09,133 --> 00:18:14,879
[SPEAKER_00] If you choose this, everything is hosted entirely on European infrastructure, specifically in Germany and France.

296
00:18:15,079 --> 00:18:21,306
[SPEAKER_01] OK, so you get the convenience of a hands-off managed service, but with the ironclad guarantee of strict European privacy standards.

297
00:18:21,426 --> 00:18:21,927
[SPEAKER_00] Exactly.

298
00:18:22,147 --> 00:18:25,871
[SPEAKER_00] And then the second path, which Safe Server champions... Is self-hosting, right?

299
00:18:26,250 --> 00:18:27,512
[SPEAKER_00] Yes, self-hosting.

300
00:18:28,293 --> 00:18:34,140
[SPEAKER_00] They provide an official Docker image, which you can find under pentacent slash keela.

301
00:18:34,519 --> 00:18:36,360
[SPEAKER_01] Let's define Docker real quickly for everyone.

302
00:18:36,400 --> 00:18:36,640
[SPEAKER_00] Sure.

303
00:18:37,281 --> 00:18:42,624
[SPEAKER_00] Imagine trying to move a house by taking it apart brick by brick and rebuilding it completely across town.

304
00:18:42,704 --> 00:18:43,485
[SPEAKER_01] Sounds exhausting.

305
00:18:43,525 --> 00:18:45,846
[SPEAKER_00] That's how installing complex software used to feel.

306
00:18:45,866 --> 00:18:46,347
[SPEAKER_01] Yeah.

307
00:18:46,367 --> 00:18:50,629
[SPEAKER_00] Docker is like building that house inside a standardized digital shipping container.

308
00:18:51,010 --> 00:18:55,353
[SPEAKER_00] You can just drop that container onto almost any server in the world, and it runs perfectly.

309
00:18:55,493 --> 00:18:55,813
[SPEAKER_01] Oh, wow.

310
00:18:56,273 --> 00:18:58,835
[SPEAKER_01] So this means absolutely zero vendor lock-in.

311
00:18:59,275 --> 00:19:02,757
[SPEAKER_01] You install Keela on your own servers, and you own the entire stack.

312
00:19:02,897 --> 00:19:03,678
[SPEAKER_00] Exactly.

313
00:19:03,898 --> 00:19:08,246
[SPEAKER_01] But wait, if I hosted on my own server, how do the emails actually leave the building?

314
00:19:08,406 --> 00:19:13,915
[SPEAKER_01] I mean, I can't just hook this up to my standard Gmail account and try to blind carbon copy 50,000 people, right?

315
00:19:14,116 --> 00:19:16,460
[SPEAKER_01] Email would ban my account in about three seconds.

316
00:19:16,909 --> 00:19:18,030
[SPEAKER_00] Oh, they absolutely would.

317
00:19:18,110 --> 00:19:19,972
[SPEAKER_00] And this is where S&TT relays come in.

318
00:19:20,833 --> 00:19:25,638
[SPEAKER_00] Keela actually separates the management of your list from the actual delivery of the emails.

319
00:19:26,219 --> 00:19:29,923
[SPEAKER_00] Think of Keela as like the steering wheel and the dashboard.

320
00:19:30,644 --> 00:19:34,528
[SPEAKER_00] You then connect it to an engine that does the actual heavy lifting of the delivery.

321
00:19:34,628 --> 00:19:38,671
[SPEAKER_01] So it basically seamlessly integrates with major delivery infrastructure.

322
00:19:38,811 --> 00:19:39,412
[SPEAKER_00] Exactly.

323
00:19:39,532 --> 00:19:44,696
[SPEAKER_00] You plug in your credentials for, say, AWS SES, SendGrid, Mailgun, or Postmark.

324
00:19:45,117 --> 00:19:48,099
[SPEAKER_00] You just choose the delivery engine that fits your budget and your scale.

325
00:19:48,599 --> 00:19:52,603
[SPEAKER_00] But Keyla remains the central command center where your data lives securely.

326
00:19:53,303 --> 00:19:55,405
[SPEAKER_01] And this isn't just theoretical architecture.

327
00:19:55,805 --> 00:19:59,008
[SPEAKER_01] The source material provides some pretty compelling real-world proof.

328
00:19:59,492 --> 00:20:03,296
[SPEAKER_01] We have a quote from Anouk Umz, the general secretary of Volt Europa.

329
00:20:03,497 --> 00:20:03,837
[SPEAKER_00] Right.

330
00:20:04,238 --> 00:20:13,668
[SPEAKER_01] They actually used Keela to send millions of emails across Europe, specifically noting that the software allowed them to keep full, uncompromising control of their data.

331
00:20:13,749 --> 00:20:15,871
[SPEAKER_00] Which is massive for a political organization.

332
00:20:16,111 --> 00:20:16,512
[SPEAKER_01] Exactly.

333
00:20:17,288 --> 00:20:29,954
[SPEAKER_01] And then there's Andre Horrell from a company called Brinjel who praised the incredibly simple user interface, the built-in node tracking features, and the fact that it's built on Elixir for that reliable scaling we just talked about.

334
00:20:30,074 --> 00:20:36,257
[SPEAKER_00] Yeah, and when you look at those two use cases side by side, you really see the true spectrum of what this software accomplishes.

335
00:20:36,297 --> 00:20:42,901
[SPEAKER_00] I mean, it is robust enough to handle millions of cross-border emails for a massive political organization, yet

336
00:20:43,641 --> 00:20:49,923
[SPEAKER_00] It maintains an interface that's simple enough that a solo creator can just jump right in and start building visual campaigns immediately.

337
00:20:50,323 --> 00:20:51,984
[SPEAKER_01] It really is a rare breed of software.

338
00:20:52,264 --> 00:21:01,027
[SPEAKER_01] It gives beginners this visual, easy-to-use entry point into newsletter creation complete with, you know, a friendly elephant mascot.

339
00:21:01,147 --> 00:21:01,667
[SPEAKER_00] The best part.

340
00:21:01,867 --> 00:21:10,430
[SPEAKER_01] But beneath that very approachable surface is packing the heavy-hitting privacy tools, the sophisticated bot protection, the dynamic JSON segmentation,

341
00:21:10,775 --> 00:21:14,397
[SPEAKER_01] and that telecom grade elixir architecture that massive enterprises demand.

342
00:21:14,457 --> 00:21:15,237
[SPEAKER_00] Powerful.

343
00:21:15,557 --> 00:21:19,459
[SPEAKER_01] It is all this backed by an absolutely unyielding open source ethos.

344
00:21:19,999 --> 00:21:23,621
[SPEAKER_00] It fundamentally changes the relationship you have with your communication tools, right?

345
00:21:24,101 --> 00:21:26,002
[SPEAKER_00] Just shifting you from a tenant to an owner.

346
00:21:26,267 --> 00:21:34,116
[SPEAKER_01] And that shift is exactly why Safe Server supports this deep dive, and frankly, why they support organizations making this critical transition.

347
00:21:34,797 --> 00:21:46,310
[SPEAKER_01] Because think back to those expensive proprietary tools your company might be using right now, the big tech giants, where you are paying premium prices just to rent access to your own audience.

348
00:21:46,650 --> 00:21:48,793
[SPEAKER_00] Right, the Google and Microsoft ecosystems.

349
00:21:48,813 --> 00:21:52,497
[SPEAKER_01] Yeah, the benefits of switching to an open source solution like Keela are massive.

350
00:21:53,178 --> 00:21:55,280
[SPEAKER_01] You aren't just looking at drastic cost reductions.

351
00:21:55,620 --> 00:22:00,346
[SPEAKER_01] You are regaining absolute uncompromising sovereignty over your subscriber data.

352
00:22:00,655 --> 00:22:03,336
[SPEAKER_00] Which you legally need in so many cases anyway.

353
00:22:03,556 --> 00:22:03,956
[SPEAKER_01] Exactly.

354
00:22:04,636 --> 00:22:17,101
[SPEAKER_01] And whether Keela is the perfect fit for your specific business or whether a comparable open source alternative might suit your unique infrastructure better, Safe Server can be commissioned for the expert consulting you need to just make it happen smoothly.

355
00:22:17,501 --> 00:22:23,703
[SPEAKER_01] They basically guide you from the initial decision process all the way to secure compliant operation on German servers.

356
00:22:24,283 --> 00:22:30,520
[SPEAKER_01] You can explore your options and finally take back control of your communications at www.safeserver.de.

357
00:22:31,553 --> 00:22:37,577
[SPEAKER_00] You know, this raises a really important question, and it brings us right back to that metaphor you opened with about the house and the master keys.

358
00:22:37,717 --> 00:22:37,917
[SPEAKER_01] Yeah.

359
00:22:38,178 --> 00:22:45,262
[SPEAKER_00] When we look at our modern digital ecosystems, we have been deeply, deeply conditioned to just trade our ownership for convenience.

360
00:22:45,803 --> 00:22:49,545
[SPEAKER_00] We simply accept that renting critical software is just how business is done today.

361
00:22:50,006 --> 00:22:58,772
[SPEAKER_00] But you know, if an open source tool like Keela can make professional email marketing this easy, this incredibly secure, and actually give you total control over your audience's data,

362
00:22:59,432 --> 00:23:03,621
[SPEAKER_00] What other proprietary software are you currently renting that you should actually be owning?